Comments on: In Defense of Development Practices http://www.brandonsavage.net/in-defense-of-development-practices/ The personal blog of Brandon Savage. Contains entries of a personal and professional nature focusing on PHP, Apple, LAMP, MySQL and Washington, DC. Fri, 03 Feb 2012 19:36:33 -0500 hourly 1 http://wordpress.org/?v=3.3.1 By: Mikael http://www.brandonsavage.net/in-defense-of-development-practices/#comment-3010 Mikael Mon, 15 Mar 2010 16:52:07 +0000 http://www.brandonsavage.net/?p=1187#comment-3010 @Stephen Cox "Perfecting" code is a way to ensure new features will be easy to add. If you don't overdo it, it's also a way to save money. And keep clients. @Stephen Cox
“Perfecting” code is a way to ensure new features will be easy to add. If you don’t overdo it, it’s also a way to save money. And keep clients.

]]> By: Stephen Cox http://www.brandonsavage.net/in-defense-of-development-practices/#comment-3009 Stephen Cox Mon, 15 Mar 2010 15:07:34 +0000 http://www.brandonsavage.net/?p=1187#comment-3009 First question i ask; "Does it work?". That's all I need to know. Look, the end users don't care about code. They want the app to work. If YOU want to spend all YOUR time "perfecting" YOUR code, have at it. As long as I'm not paying your salary. ;) Shawn, is right. it's a balancing act. A balance of time, people and resources. All done to make sure the app works. And that's the important thing. ;) First question i ask; “Does it work?”. That’s all I need to know.

Look, the end users don’t care about code. They want the app to work. If YOU want to spend all YOUR time “perfecting” YOUR code, have at it. As long as I’m not paying your salary. ;)

Shawn, is right. it’s a balancing act. A balance of time, people and resources. All done to make sure the app works. And that’s the important thing. ;)

]]> By: Chris D http://www.brandonsavage.net/in-defense-of-development-practices/#comment-3001 Chris D Fri, 12 Mar 2010 20:51:37 +0000 http://www.brandonsavage.net/?p=1187#comment-3001 Martin Fowler (mentioned in Marco's post) made up all that crap just to get free drinks and woo women at computer and business conferences. I bet he never though that people would actual believe it when they sobered up. Martin Fowler (mentioned in Marco’s post) made up all that crap just to get free drinks and woo women at computer and business conferences.

I bet he never though that people would actual believe it when they sobered up.

]]> By: Shawn Stratton http://www.brandonsavage.net/in-defense-of-development-practices/#comment-3000 Shawn Stratton Fri, 12 Mar 2010 06:12:19 +0000 http://www.brandonsavage.net/?p=1187#comment-3000 While I agree with you and Marco on process, let me say something of my own; I've worked on enough projects where there were no practices or standards that I've realized they are a necessity but at the same time best practices of the community don't work on every team equally. Best practices are awesome in a perfect world where every team member is well versed, the project and methodology is well documented, and the deadline allows enough time to implement them. Sadly almost no project I've seen in the wild meets any of these 3 qualifications, so you literally have to pick and chose what practices to follow and which to cast aside in order to do what programing is really intended for, produce a working product. Yes I agree uptake time is important, maintainability is important, and I even agree the larger messes of code (Wordpress as an example) work, but really the single best practice that most developers and managers need to learn is how to compromise and balance between good/best practices and doing our jobs. While I agree with you and Marco on process, let me say something of my own; I’ve worked on enough projects where there were no practices or standards that I’ve realized they are a necessity but at the same time best practices of the community don’t work on every team equally. Best practices are awesome in a perfect world where every team member is well versed, the project and methodology is well documented, and the deadline allows enough time to implement them. Sadly almost no project I’ve seen in the wild meets any of these 3 qualifications, so you literally have to pick and chose what practices to follow and which to cast aside in order to do what programing is really intended for, produce a working product. Yes I agree uptake time is important, maintainability is important, and I even agree the larger messes of code (WordPress as an example) work, but really the single best practice that most developers and managers need to learn is how to compromise and balance between good/best practices and doing our jobs.

]]>