Can't Argue With That

bugs Developers Library Unexplained Paranormal

Programming Debugging Testing

4 months ago 124,746 views 0 shares

Can't Argue With That

programming-memes, debugging-memes, library-memes, unexplained-memes, software-memes | ProgrammerHumor.io

In the hallowed halls of knowledge, software programming sits right next to "unexplained phenomena" in the Dewey Decimal System. Coincidence? I think not! The library just confirmed what we've all suspected—code that works on the first try, disappearing bugs that reappear in production, and that one function nobody wrote but somehow runs perfectly... all supernatural events that defy scientific explanation. Next time your code works and you don't know why, just remember: you're not a programmer, you're a digital paranormal investigator.

More Like This

We do Agile

Programming

3 years ago 32.4K views 0 shares

We do Agile | ProgrammerHumor.io

Content CEREAL It's just a matter So, when will that ofume ant The one new feature be ready month, couit de no months Three months? could he Four months? I contrece that happening, yes Eight months? That's a realistic timeline Eleven months? Perhaps Ok. now really think hard about this one. One year? I could see that as a very real possibility

Avoid potential problems

Programming Linux

4 years ago 44.3K views 0 shares

Avoid potential problems | developer-memes, design-memes, cli-memes, IT-memes | ProgrammerHumor.io

Content ARE YOU THE DEVELOPER? JUST FINISHED THE DESIGN, AND I WOULD LIKE TO DISCUSS IT WITH YOU BEFORE SHOWING IT TO THE CLIENT. JUST TO AVOID POTENTIAL PROBLEMS IS THIS A DREAM? PLEASE.FOLLOW ME. DON'T HAVE FRIENDS garabatokid.tumblr.com ' garabatokid

Shorten Your Function Name

Programming Csharp C++ Javascript Python

1 month ago 157.8K views 0 shares

Shorten Your Function Name

The classic programmer journey from self-righteousness to self-sabotage in three easy steps: First, you write a verbose, descriptive function name that perfectly documents what it does. You feel virtuous. Clean code! Self-documenting! Then, you realize typing that monstrosity repeatedly is killing your productivity. So you create a wrapper function with a shorter name. Problem solved! Finally, you're faced with your creation in production code: if (cumming()) - and suddenly you remember why code reviews exist. Your future maintainers will either die laughing or hunt you down with pitchforks. And this, friends, is why naming things remains one of the two hardest problems in computer science.

..and make code more readable?

Programming

2 years ago 31.2K views 0 shares

..and make code more readable? | code-memes, indentation-memes | ProgrammerHumor.io

Content if (condition) ... Why don't you invert the condition and return to avoid one level of indentation?

Well, technically

Programming Cloud

3 years ago 40.9K views 0 shares

Well, technically | tech-memes, cloud-memes | ProgrammerHumor.io

Content So technically Moses is the first man to download files from the cloud using a tablet. ProgrammerHumor.to

When You Must Explain Your Own Code

Programming Javascript Debugging Frontend

4 months ago 131.3K views 0 shares

When You Must Explain Your Own Code

When the senior dev asks you to explain your code to a non-technical stakeholder, and suddenly you realize you don't actually understand what you built either. That moment when your elaborate JavaScript framework is just a glorified rubber duck – it looks impressive floating in the bath of your codebase, but you have no idea what it's actually supposed to do. The perfect representation of every technical interview where you confidently wrote something that worked by accident.