Comments on: The Duct Tape Programmer – Joel on Software http://stereointeractive.com/blog/2009/09/25/the-duct-tape-programmer-joel-on-software/ Development Blog Tue, 07 Sep 2010 10:31:10 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Lawrence Krubner http://stereointeractive.com/blog/2009/09/25/the-duct-tape-programmer-joel-on-software/comment-page-1/#comment-491 Lawrence Krubner Sun, 04 Oct 2009 22:05:06 +0000 http://stereointeractive.com/blog/?p=317#comment-491 This offered a bit of balance: http://blog.objectmentor.com/articles/2009/09/24/the-duct-tape-programmer This offered a bit of balance:

http://blog.objectmentor.com/articles/2009/09/24/the-duct-tape-programmer

]]> By: Andrew Noyes http://stereointeractive.com/blog/2009/09/25/the-duct-tape-programmer-joel-on-software/comment-page-1/#comment-482 Andrew Noyes Sun, 27 Sep 2009 20:46:47 +0000 http://stereointeractive.com/blog/?p=317#comment-482 Brilliant post! These days people seem very bent up over development patterns and modular programming--agreed, these are incredibly important things that are helping brilliant minds architect massive, world changing appliances--but for most of us, they're a big waste of time. I've met plenty of programmers who wanted to do things from their academic programming high horse, to the letter, who only ended up obfuscating the code and making it impossible to maintain. WHAT IS THAT?! A HARD CODED BUSINESS RULE?! We need to re-engineer this into a more ductile framework just in case the rules change! The end result is that for every programming project, they create a theoretically sound system designed to be able to handle curveballs without breaking a sweat, turning every single programming project into a framework. Abstraction on top of abstraction on top of abstraction. Ironically, they're building said framework on top of a system that is designed to easily implement any business logic and allow a developer to change the rules when needed--A PROGRAMMING LANGUAGE! Brilliant post! These days people seem very bent up over development patterns and modular programming–agreed, these are incredibly important things that are helping brilliant minds architect massive, world changing appliances–but for most of us, they’re a big waste of time. I’ve met plenty of programmers who wanted to do things from their academic programming high horse, to the letter, who only ended up obfuscating the code and making it impossible to maintain. WHAT IS THAT?! A HARD CODED BUSINESS RULE?! We need to re-engineer this into a more ductile framework just in case the rules change!

The end result is that for every programming project, they create a theoretically sound system designed to be able to handle curveballs without breaking a sweat, turning every single programming project into a framework. Abstraction on top of abstraction on top of abstraction. Ironically, they’re building said framework on top of a system that is designed to easily implement any business logic and allow a developer to change the rules when needed–A PROGRAMMING LANGUAGE!

]]>