Who's Gonna Tell Him

Content The Proud Parent The Linker REPENT TOMER - Half your manager, half your senior - Designed the codebase - Will always answer your question, but only after a 5 minute on the motivations of a now rebuilt module from years ago - "I remember when we had to do that process in the AWS console with just a trackpad, uphill both ways" - Tough during code review, but genuinely happy to see you ship new features to the system The Job Security Maximizer - Always sends you a link when you ask a question, sometimes without any other words - "Look at this" - Thinks you don't know standard documentation exists - Posts medium articles in the main channel, doesn't read them - Never reviews code - First stack overflow result The Big Chiller - "Ohh, that? Sorry I totally forgot all - Been around for years, knows the entire about the code I wrote a month ago" codebase - Tells you to ask someone else for the - Friends with the CTO simplest question - Shows you the exact line of code that - Has dozens of pages of private notes, causes your bug within 5 minutes READMEs all read "initial commit" - They last shipped a commit a couple - "Have you thought about adding an months ago, you think abstracter to this abstraction? With that - Always approves your PRs we can decouple the coupler from the universe" 10 i0

Content Senior Developer: junior developer: Sir Error On Line 42 Error: 41 42 43 ); if (includ MemesByUneeb

The universal developer solution to compiler warnings: just put a decorative plant in front of the screen! Who needs to fix those 43 warnings when strategic foliage placement solves the problem instantly? This is basically the software equivalent of putting tape over your check engine light. Sure, your code might explode in production, but at least your desk looks nicer!

Sleeping peacefully until your brain jolts you awake at 3:27 AM because you realized you used = instead of == in that authentication code. That single equals sign just gave admin access to literally everyone. Sweet dreams! Nothing quite like the cold sweat of realizing you've accidentally created the world's most generous authorization system. The fix takes 2 seconds but the existential dread lasts forever.

Documentation: *exists* Developers in 2023 still trying to absorb technical knowledge like it's The Matrix. Those jumper cables aren't going to help you understand that 500-page API reference any faster. Just another day of hoping the knowledge will somehow bypass the reading part and directly upload to your brain. Spoiler alert: the only thing getting fried here is your dignity.

The eternal struggle of being the "tech person" in the family. First you're desperately trying to explain that programming skills don't magically transfer to printer repair, then five seconds later you're elbow-deep in printer parts because—let's face it—you actually can fix it. Not because of any programming knowledge, but because you've developed the sacred debugging mindset after years of staring at error messages that might as well say "something's wrong lol good luck." The real programming skill is knowing how to Google the right question while maintaining the illusion that you're doing something complicated.