So true 😂😂😂

i'm getting headaches right now...

Every job interview question ever

It's a merge conflict

Conversation today...

Guy: "Hey I need a real quick script to pull some values out of an XML document...is that possible?"

Me: "Uh...yeah that's pretty simple if that's all it has to do."

Guy: "Ok excellent I'll send you some files and documentation."

Me: "Ok so is this like a one time use thing or do you need to parse multiple of these?"

Guy: "Actually it needs to run all the time, on this specific PC, watch directories for any files that are added, then generate a XLSX files of the values, and also log information to a database. Etc"

Me: "Oh that adds quite a bit of complexity from what you originally said. It's going to take more time."

Guy: "But you said it was easy."

Well fuck you...

Ran into a girl who I had a crush on in high school at a bar last week. Hanged out for a bit, but then I had to run catch the last train home.

Today I get a message from her that reads: "Hey, it was nice to meet you last week. Can I call you some time, there's something I want to tell you. 😉"

I think to myself -- sweet and say that I have no meetings today, call me whenever you can.

A couple of minutes later she calls me, and the first thing she says: "I have this app idea..."

fuck, shouldn't have hyped myself up.

When somebody started bragging about his superior coding skill then I said that talk is cheap and that I wanted to see code (for some reason, this pissed her off) and then she started to DDoS me :^)

spoiler alert: she got a huge fine for it AND got fired from her job (whose servers she used to perform the DDoS)

Too much work kills your brain cells.

Well here's how I see things going:

Intel and AMD ditch their assembly architectures for Scratch, because drag and drop is very popular lately.

The Boolean is renamed to the biggot by SJW leaders for only supporting binary views.

You must first ask consent to add an item to a linked list, because forcing two items together promotes rape culture.

Apple removes the "h" and "7" keys on all laptop models and gives no reason for their actions.

Linus Torvalds grows an extra middle finger, and it still isn't enough.

Nintendo makes Mario gay and Luigi black to be more inclusive.

LG makes a curved monitor that curves away from you rather than towards you. People buy it in confusion.

Everyone makes the same ad revenue on YouTube, and it is rebranded to OurTube. Luckily, they were able to keep the color scheme.

People finally realize that machine learning is just math, and stop using it everywhere. (Just kidding lol)

AMD and Gucci merge. Nobody understands why.

assignment: use winAPI to create a "virus" that put itself in autorun and does nothing.

me, a curious student: does the assignment and adds a heap corruption code just as a joke.

after sending the assignment to the teacher I realized that I have sent the real virus.

result: teacher comes next lesson without a computer and stares at me silently and viciously.

we'll see what happens next
any idea on what's going on in his head?

day 1 - colleague buys a mini need pistol

day 2 - other colleague buys a big nerf pistol

day 4 - other colleague buys a f#&$ nerf shotgun

day 7 - I buy a automatic nerf gun

day 8 - huge nerf war with other co-workers

day 9 - nerf weapons banned on the office

yesterday - wait colleague leave the office and shoot him on the face every time

today - everyone walking crouched leaving the office

Please, if you are the someone else's boss, don't ban nerf guns, it's worse..

D: “Did the attackers exfiltrate any data?”

M: “I can’t say for sure, but most likely based on—”

D: “—but did you find any undeniable evidence of it?”

M: “Keep in mind that the absence of evidence isn’t necessarily evidence of absence. There was very limited logging to begin with and the attacker erased artifacts and logs.”

D: “If there’s no evidence, then there was no exfiltration.”

M: “If a business doesn’t have cameras on its front door and then gets robbed, it can’t claim there was no robbery just because they didn’t video-record it.”

D: “That’s a poor analogy. Nothing’s missing here. I couldn’t care less if a robber made a *copy* of my money. That isn’t robbery.”

M: “... If the Titanic really hit an iceberg, then how come no pieces of an iceberg were ever found in the wreckage?”

Well, that’s one way to stop someone from harassing you online. But damn....

Simple flowchart XD

Epic self-troll... Btw, YT deserved it.

Found this 2 years old beauty today:

public boolean hasPermission(User user, Permission permission){
// TODO
return true;
}

The author quit last year.

😂😂😂

Fuck you GoDaddy thats all I have to say, transcript attached.

http://imgur.com/a/PixiAUf

Gotta love testing in production. Nice work Niantic 🤣

Informative.

Intel x86

Unicode on a cup of joe

- Think first, write later;
- Do not rush into purchasing servers. You might not need them for another 10 months;
- It takes away a lot of family time to do side projects;
- NOT playing any games saves tremendous amounts of time. Also applies to watching TV;
- If you get stuck - get some sleep. Morning brings you better ideas;
- Write proper abstractions or you'll end up refactoring everything way more often that you'd like;
- Side projects need a loo-ooooot of your will and determination

This shit is real.

Guy comes to my desk.
Guy: Do you know Python?
Me: Yes
Guy: I want a program that reads a CSV containing IP addresses and tells which of them are valid.
Me: Sure thing. Show me the CSV file.
Guy: (Shows the file)
Me: (Writes a small function for checking whether the IP is valid)
Me: Done Here you go.
Guy: You should be using regex.
Me: Why? This is perfect. No need for regex.
Guy: My manager wants a solution using regex only.
Me: Why so?
Guy: I don't know. Can you do it using regex?
Me: Only if you say so. (Stackoverflow. Writes a humongous regex). Done!
Me: Just for curiosity, what is your application?
Guy: I will port it in Java. You see, regex is easy to debug.
Me: Ohhh Yes. I forgot that. Good luck with your regex.

START FUCKING USING GIT.

😅

new rule in company

No headphones while coding

job hunting start......

This is how one of our junior devs solved a merge conflict

Currently acing an interview, had to do a typing test, got 67wpm and 98% accuracy.

"If you want faster I'd have to bring my own keyboard, this one's a little small"

"You can go faster?"

--- HTTP/3 is coming! And it won't use TCP! ---

A recent announcement reveals that HTTP - the protocol used by browsers to communicate with web servers - will get a major change in version 3!

Before, the HTTP protocols (version 1.0, 1.1 and 2.2) were all layered on top of TCP (Transmission Control Protocol).
TCP provides reliable, ordered, and error-checked delivery of data over an IP network.
It can handle hardware failures, timeouts, etc. and makes sure the data is received in the order it was transmitted in.
Also you can easily detect if any corruption during transmission has occurred.
All these features are necessary for a protocol such as HTTP, but TCP wasn't originally designed for HTTP!
It's a "one-size-fits-all" solution, suitable for *any* application that needs this kind of reliability.
TCP does a lot of round trips between the client and the server to make sure everybody receives their data. Especially if you're using SSL. This results in a high network latency.
So if we had a protocol which is basically designed for HTTP, it could help a lot at fixing all these problems.
This is the idea behind "QUIC", an experimental network protocol, originally created by Google, using UDP.

Now we all know how unreliable UDP is: You don't know if the data you sent was received nor does the receiver know if there is anything missing. Also, data is unordered, so if anything takes longer to send, it will most likely mix up with the other pieces of data. The only good part of UDP is its simplicity.
So why use this crappy thing for such an important protocol as HTTP?
Well, QUIC fixes all these problems UDP has, and provides the reliability of TCP but without introducing lots of round trips and a high latency! (How cool is that?)

The Internet Engineering Task Force (IETF) has been working (or is still working) on a standardized version of QUIC, although it's very different from Google's original proposal.
The IETF also wants to create a version of HTTP that uses QUIC, previously referred to as HTTP-over-QUIC. HTTP-over-QUIC isn't, however, HTTP/2 over QUIC.
It's a new, updated version of HTTP built for QUIC.

Now, the chairman of both the HTTP working group and the QUIC working group for IETF, Mark Nottingham, wanted to rename HTTP-over-QUIC to HTTP/3, and it seems like his proposal got accepted!
So version 3 of HTTP will have QUIC as an essential, integral feature, and we can expect that it no longer uses TCP as its network protocol.

We will see how it turns out in the end, but I'm sure we will have to wait a couple more years for HTTP/3, when it has been thoroughly tested and integrated.

Thank you for reading!

Lol, prob repost but funny anyway.