Me rereading code I wrote a month ago

Content Related What personality trait makes a bad developer? Thinks like a normal person, not a programmer. Normal people get things done; programmers get computers to do it. I am extremely lazy; I will spend 12 hours programming something that would take me 2 hours to do, because: 1. It takes me 2 hours to do it the first time, and 2 hours to do it the second. But it takes my program 0 hours to it the first time and the second time and every futire time, 2. you NEVER do stuff only once. 3. I make mistakes. When I do it the first time, I will get something wrong, but I wont want to spend another 2 hours to do it again. But I can test the program and run it until it gets it right.

Content BUILD A WEB APP IN 14 LINES 1572 DEPENDENCIES, 116 MB TO DOWNLOAD

Ah, the classic programmer joke about array indexing! The medal shows "1 Place" but someone cuts out the "1" to make it "0 Place" - because in most programming languages, arrays start at index 0, not 1. The programmer's smug face in the final panel says it all. He's not celebrating second place, he's celebrating the technically correct place. This is peak programmer pedantry that only true code jockeys would appreciate. The kind of person who'd correct you mid-conversation about proper variable naming conventions.

GASP! The AUDACITY of developers thinking they can hide behind AI! 💅 When you run git blame to find out which MONSTER broke the code, it reveals the actual HUMAN criminal - not GitHub Copilot! Your AI assistant isn't taking the fall for your disaster of a commit, sweetie! That's right, your name is PERMANENTLY etched in the git history hall of shame! There's no escaping accountability in this dystopian developer hellscape!

Content Going to pass a new job interview Junior Senior

Content The number of tabs open on chrome when I'm working on a project Number of stars in the galaxy Number of grains of sand on Earth