Comments on: What would you like your software developers to learn? http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/ Effective software development Mon, 13 Oct 2008 08:54:20 +0000 http://wordpress.org/?v=2.0.6 by: Ben http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-45818 Tue, 19 Aug 2008 03:12:50 +0000 http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-45818 I want the people I manage to get from what the customer thinks they want to what they need and can use. I do this by getting them to put something into the customers hands as fast as possible, no matter how simple, and iterating from there. I get them to focus on workflow improvements rather then adding shiny things! I want the people I manage to get from what the customer thinks they want to what they need and can use.

I do this by getting them to put something into the customers hands as fast as possible, no matter how simple, and iterating from there. I get them to focus on workflow improvements rather then adding shiny things!

]]> by: George Dinwiddie http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28194 Sat, 05 Apr 2008 03:00:11 +0000 http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28194 Zeb, Tim, What about the followup questions? Zeb, Tim,

What about the followup questions?

]]> by: Tim Walker http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28184 Fri, 04 Apr 2008 23:52:29 +0000 http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28184 Executable requirements and other agile best practices. Executable requirements and other agile best practices.

]]> by: ZebZiggle http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28040 Thu, 03 Apr 2008 22:18:19 +0000 http://blog.gdinwiddie.com/2008/04/03/what-would-you-like-your-software-developers-to-learn/#comment-28040 1. Learn the business. How do we make money? How do our customers make money by using our products? Why are these features important? 2. Sort of a variation of Don't Repeat Yourself (DRY) in code but Don't Do It Manually (DDIM) with business processes. Are you collecting metrics manually? Are you doing builds manually? Are you setting up/tearing down manually? Automate it and never do it again. 3. Don't get attracted to shiny objects. It's easy to go down a technical rabbit hole because something is cool & new. Keep focused, stay on the task at hand. When the core work is done ... go play in the woodshed. 4. Don't make broken windows. There is a business process for a reason. If you aren't contributing to making it better or maintaining it, you are making broken windows. Before long the process fails and it's chaos. 1. Learn the business. How do we make money? How do our customers make money by using our products? Why are these features important?

2. Sort of a variation of Don’t Repeat Yourself (DRY) in code but Don’t Do It Manually (DDIM) with business processes. Are you collecting metrics manually? Are you doing builds manually? Are you setting up/tearing down manually?

Automate it and never do it again.

3. Don’t get attracted to shiny objects. It’s easy to go down a technical rabbit hole because something is cool & new. Keep focused, stay on the task at hand. When the core work is done … go play in the woodshed.

4. Don’t make broken windows. There is a business process for a reason. If you aren’t contributing to making it better or maintaining it, you are making broken windows. Before long the process fails and it’s chaos.

]]>