Who has not stolen a cookie from the jar when Mother was not searching?
Or stayed out with close friends extensive immediately after bedtime?
Or — God forbid — taken the shortcut by means of the park in which shady men and women lurk, rather of heading the extensive way about the main road?
Or, indeed oh sure, which programmer has not violated a single of all those etched-in-stone greatest tactics, you know, a person of the types that you should really adhere to at all expenditures?
It is risk-free to say that a lot of, if not most, of us have accomplished this right before. But possibly your rule-breaking is specifically why your code was much better than normal. At minimum it didn’t make you drop your job. Or make your pc explode at runtime.
Sure, breaking principles is never ever devoid of possibility. If you’re a mind surgeon, you really need to abide by the rule of “never lower this piece off.” (Forgive me for my bluntness, I’m no health-related professional.)
But if you’re setting up software package, what’s the worst circumstance? Certain, if you are developing killer drones or software program for electrical grids or assistance programs for spaceships you may well want to go slow and comply with the regulations.
But those programmers who don’t have significant stakes like that — and that is most of us — you might want to dilemma your rulebook from time to time.
Duplicate-pasting code isn’t the root of all evil
Initially of all, if you have a problem that can take 5 seconds to google, you would not go annoy your coworker for ten minutes to make them resolve it. And if the remedy is on Stack, then, nicely, the solution is there.
The purists would argue that you shouldn’t copy anything since you could possibly not fully grasp what’s going on in the copied code. And they have a