"Coding is easy. All you need is an idea, and the rest is just typing!"

All I want for Christmas is... 😍😍😍

Slow Internet connection and people who don't follow the Headphones Rules

My friend just started RUBY.
He read somewhere " Ruby is used commonly in rails ".

He now thinks RUBY is for programming trains and station related stuff.

Interviewer: where do you see yourself in near future.
Me: to get a 175+ on my Rant.

Myself 1 week into programming
"I can build a website!!"

Myself 2 years later and multiple web and mobile apps launched
"I know nothing"

Customer at a first meeting:
- "Didn't realize you're a developer, you're almost good looking!"
Never got a more bittersweet compliment.

Code runs, time to remove all the System.out.println("AAAAAAAAA"); from it.

Today I learned: typing "man ascii" into the terminal on Linux will print out the ascii table.
Guess I don't need to go online to find it anymore

When you are a Dev but you don't want to be single

Girl: what's your profession?
Me: I am a writer
Girl: Cool! What do you write?
Me: I write code😎

Client: "My Internet isn't working!"

Me: "You've got your own one?"

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook

That would be 🙄

When it's time to go into evil mode

Apple rejected my app, because they throught there was a frickin Windows phone on my loading screen.

How insecure can you be?

Damn Dijkstra!

EDIT: devRant April Fools joke (2017)
-------------------------
@trogus and I have had an absolute blast working on devRant over the last year. However, we're strong believers in only working on a project if you're passionate about it, and over the last few months, we've sadly lost some of that passion so we've to announce, with heavy hearts, that we will both be moving on. We've decided to focus 100% of our energies on our next product, one which we are confident has billion dollar potential: Semicolon JS (http://semicolonjs.com).

We identified this sizable market opportunity as we were building out the new devRant website. Every JavaScript framework we tried left us wanting more. More efficiency. More elegance. More extensibility. That's what Semicolon JS is: more. More than a framework, it's a guiding philosophy. We believe that Semicolon JS will do for front end development what Material Design has done for user interface design. We're calling it Semicolon JS because even though you can still develop JavaScript without it, like a semicolon, we think it will soon become a standard and synonymous with quality JS development.

So comes the obvious question. What will happen to devRant? We wanted to make the announcement today because we will be officially shutting down the product in 30 days. So that gives everyone a full month to take in the last memories, look at those rants they really loved, and hopefully take some time to chat with @trogus and I about Semicolon JS and what we have planned.

With so many thanks and looking towards the future,
- @dfox and @trogus

Best DHCP server ever.

If Doctors Were Like Coders
(cross-posted from https://medium.com/@c09b6133a238/...)

Problem: The patient has a broken leg.

Solution:

1. Ask the patient to reproduce the exact scenario that resulted in the broken leg. Watch closely to see if the leg breaks again. Check for consistency by repeating the scenario a few more times.

2. Explain that this isn’t an intended use case for the leg, and besides, it only affects one person. Ask the patient if, all things considered, he really wants to prioritize his broken leg over your other work.

3. Point out that the patient’s other leg performs just fine under the same circumstances. Ask if he can use his other leg instead, at least as a workaround.

4. Attach several accelerometers to the broken leg and break it again. Stare at the data received from the accelerometers, then shrug and declare it useless.

5. Decide that the patient’s problem must be in his spleen. After all, that’s the only part of his body you don’t really understand.

6. Track down the people who created the patient. Ask them if he’s ever had spleen problems before. When they seem confused, explain that he has a broken leg. Ignore them when they tell you that the spleen they created could not possibly cause a broken leg.

7. Ask Google where a person’s spleen is. Spend half an hour reading the Wikipedia article on Splenomegaly.

8. Open the patient and grumble about how tightly-coupled his spleen and circulatory system are. Examine the spleen’s outer surface to see if there are any obvious problems. Inform him that several of his organs are very old and he should consider replacing them with something more modern.

9. Compare the spleen to some pictures of spleens online. If anything looks different, try to make it look the same.

10. Remove the spleen completely. See if the patient’s leg is still broken. If so, put the spleen back in.

11. Tell the patient that you’ve noticed his body is made almost entirely out of cellular tissue, whereas most bodies these days are made out of cardboard. Explain that cardboard is a lot easier for beginners to understand, it’s more forgiving of newbie mistakes, and it’s the tissue franca of the Internet. Ask if he’d like you to rebuild his body with cardboard. It will take you longer, but then his body would be future-proof and dead simple. He could probably even fix it himself the next time it breaks.

12. Spend some time exploring the lymph nodes in the patient’s abdominal cavity. Accidentally discover that if the patient’s leg is held immobile for six weeks, it gets better.

13. Charge the patient for six weeks of work.

This one time, a client wanted a complete overhaul of her website.

I asked her for the credentials to the VPS, She gave me some random crap to try, cause clearly the site hadn't been touched since 2003 (and boy was it fugly).

Me: Maam, these aren't the correct details.

She sends in more crap to try...2 days pass with this back and forth.

Client: "contact steve, he should have the login details"

Me: ****Calls Steve *****
Me: "Maam, he says the login details are in your mail"

Client: "well, I don't remember this fact. Steve handled everything.
Hack into the website and then reset it.

The Russians did not need login details to hack into America's system. So please, do what you have to do to get us moving."

No jokes...that was the exact crap that came out of her fingers