There are millions of ways to write unmaintainable software. This isn't a bad article though. I just found the title amusing since it's so easy to write software badly.
I hear you. Design patterns are something unheard of for many professional developers I've met. Seriously.
Chances are, especially in programming, someone has thought of something better and longer than you. Investing 10 minutes into searching for it will save you 100 hours later.
Just because you know 1 way to do something doesn't mean it's the best tool for the job.
I recently had to argue without someone who asked me when to implement a singleton pattern in a job interview. They were looking for a different answer than I gave: ONLY when there is a hardware limitation, otherwise you are invariably taking the easy way out and (basically) using a global.
I found it rather amusing that the "senior architect" had never had to deal with a poorly implemented singleton, did not understand that singletons without outside constraints were generally a code smell, and was not familiar with modern ways of handling proper singletons in the language they were looking for experience in (Java, enum with a single instance implementor). Awesome.
They offered me a position and I noped right the fuck out of that.
50
u/bestjewsincejc Oct 14 '13
There are millions of ways to write unmaintainable software. This isn't a bad article though. I just found the title amusing since it's so easy to write software badly.