The Copy-Paste Betrayal

Expectation: Writing elegant code with perfect structure and original logic. Reality: WHEEEZE *frantically searching through 2000 lines of code at 3am* "I FORGOR SEMICOLON" And then there's that one missing semicolon that keeps you awake for 4 days straight while your non-programmer friends think you're being dramatic. No, Chad, this isn't like when you "missed her" - this is psychological warfare between me and a punctuation mark that Satan himself invented.

The eternal tech support paradox in its natural habitat! You're desperately trying to explain how to use the software while the user is completely disinterested, yet somehow the program itself is just sitting there, sipping coffee and watching the chaos unfold. It's like trying to teach quantum physics to a goldfish while the quantum computer is just chilling in the corner. The best part? Tomorrow they'll ask you the exact same questions again, as if today's explanation evaporated into the void of their RAM.

The classic tale of software development! You've got this beautiful, sleeping lion of efficient code that's been purring along just fine in production for months. Then some product manager comes along with a stick and the brilliant idea to "just add one small feature" that's about to wake the beast and unleash chaos across your entire codebase. That baboon with a stick is the perfect embodiment of management poking at stable systems without understanding the delicate balance that keeps everything from exploding. Ten bucks says the lion wakes up and someone's going to be debugging until 4 AM on a Saturday.

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

Content I Am Devloper iamdevloper Remember, a few hours of trial and error can save you several minutes of looking at the README. 2:11 AM 07 Nov 18