The problem being a dev at a big company (around 1000 devs) with huge codebase (I mean huge, tens of thousands of modules, if not millions) is that, as many hands touch the code of a project and deadlines are always short, not everyone care about changing the documentation afterwards.

This translates to double the work everytime you need to fix a bug or something as you have to quickly reverse engineer the modules to understand it - the documentation often reflects an old version and it messes things up much more than it helps you out.

One of the many joys in a programmers life

Web devs get me

Russian-roulette in Bash

I love it when I spend 20+ minutes answering someone's question on the Stack and they don't even bother accepting my answer, or upvoting. I'm gonna give up on that website soon.

Happy birthday Linux. Here's your cake.

Windows, no matter where.

!rant

NASA using Node.js to build a mission control framework. I just hope they don't get discouraged by the haters 😃

https://nasa.github.io/openmct/

THE MOTHER FUCKING INTEGRATION TEST ALWAYS BREAKS IN CI ONLY, NOT ON MY MACHINE. SEEMS LIKE HE HAS SOME PERSONAL ISSUES WITH ME. THE FUKING HAUNTING GHOST

Everyone always says the previous developer was crap, sometimes you're right