When You Debug For Two Hours

Content Why I quit my programming job to become a diamond miner. I used to be a programmer. I worked in an office, staring at a computer screen all day. I was good at my job, but I wasn't happy. Then I found out about diamond mining. The thing about diamonds is that several armed groups are fighting over control of the mines. But my C skills transfer pretty well to my AK-47. Sure, the work is hard. I have to be constantly on the lookout for land mines, and the pay is terrible. But I'm my own boss, and I get to work outdoors. And the best part is, I don't have to deal with people asking me to fix their printer anymore.

Content ZeroEcks ZeroEckscuties.cloud 0 2tim a fun trick I once learnt. If you are worried at some point that you will ever run out of hard drive space on a server (which would cause everything to come to a sudden grinding halt) Add ballast! I add a 20gb file on the root of the hard drive, I can then delete this in an emergency to buy myself enough time to sit down properly and fix it. sysadmin name: Create ballast community. general. filesi; path: ballast size: 20GB 17 34

Oh. My. God. Barbie is literally ALL OF US facing the unholy trinity of web development! She's over here coding HTML with one hand, CSS with the other, and when asked about JavaScript? The only reasonable response: SMASH FACE INTO KEYBOARD! 💀 The sheer audacity of Steven and Brian offering "help" while Barbie's already juggling the impossible. Like, excuse me?! I don't have a third hand for your callback hell nightmare, thankyouverymuch! Honestly, head-banging is the most elegant solution to JavaScript bugs I've seen in years. Pure genius. No debugging required!

Content developers I just wanna ship my product I know my nodejs backend isn't good enough, but. infrastructure engineers you guys are idiots I hate all of you whoops, junior dev just deployed to production without testing. guess who's not getting help fixing their outage project manager, I will not join your hour long standup. Fill out a ticket like everyone else and GTFO

The ultimate developer escape hatch has arrived! Some genius created a GitHub repo called "git-blame-someone-else" with 11k stars and counting. It's basically the digital equivalent of writing "not my fault" in your commit messages, but automated. The repo description says it all: "Blame someone else for your bad code." Finally, a way to attribute those questionable 3 AM coding decisions to your coworkers! The MIT license is just chef's kiss—legally allowing you to distribute your blame. Who needs accountability when you have this repo? Your tech debt just became somebody else's problem!

Content Sarah Barr Sarah Barr Explaining the peer review process to my brother, a carpenter academia phdlife AcademicTwitter Imagine spending 2 years making a table and then showing someone and they tell you every tiny detail wrong with it 2:40 PM A So you fix everything they say and then show some more people and they tell you everything STILL wrong with it 2.40 PM One of them asks why you made it with 4 legs when it would have been much more stable with 8 legs 2:40 PM Another says this table is too heavy, it should have shorter legs 240 PM The third one says the table is fine but did you consider making a chair instead? 2.40 PM 7:31 AM 2022-09-08 Twitter Web App