Trying To Patch A Bug In Production Be Like

Content bhav Oxbaface Being a dev is like being a woodpecker - just methodically bang your head against a wall until you find all the bugs 6:36 PM Nov 9, 2021

Ah yes, the tea bag floating on top instead of steeping properly—exactly how features work without documentation. Developer thinks it's "common sense" that you're supposed to remove the staple and dunk the bag. User just plops the whole thing in and wonders why their experience tastes like disappointment and metal. Six months later, the same developer will stare at their own code wondering what dark magic they were attempting.

The eternal battlefield of code reviews captured in one perfect image. Code reviewers (the kids) are desperately trying to protect themselves from the tiger (that obvious bug that will definitely crash production), while completely ignoring the rabbit (a harmless typo in a comment). Classic case of missing the forest for the trees—or in this case, missing the tiger for the bunny. The same reviewers who'll write a 12-paragraph essay about your variable naming conventions will somehow miss the null pointer exception that's about to nuke your entire AWS instance.

Content DON'T BE A DICK PUBLIC LICENSE Version 1, December 2009 Copyright (C) 2009 Philip Sturgeon emailphilsturgeon.co.uk Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed. DON'T BE A DICK PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 1. Do whatever you like with the original work, just don't be a dick. Being a dick includes - but is not limited to - the following instances: 1a. Outright copyright infringement - Don't just copy this and change the name. 1b. Selling the unmodified original with no work done what-so-ever, that's REALLY being a dick. 1c. Modifying the original work to contain hidden harmful content. That would make you a PROPER dick. 2. If you become rich through modifications, related worksservices, or supporting the original work, share the love. Only a dick would make loads off this work and not buy the original works creators) a pint. 3. Code is provided with no warranty. Using somebody else's code and bitching when it goes wrong makes you a DONKEY dick. Fix the problem yourself. A non-dick would submit the fix back.

Content shard files

Content Nick Craver O Nick Craver uh huh. temporary try 3:57 AM - Jul 27, 2022 TweetDeck 15 Retweets 2 Quote Tweets 275 Likes Nick Craver Nick Craver 19h Replying to Nick Craver I don't want y'all to worry, I fixed it. temporary Permanent try