About Me

Training

Nothin But .Net Developer Bootcamp

Navigation

Search

Categories

On this page

The fallacy of the standardized developer machine/image

Archive

Blogroll

 Agile Developer Venkat's Blog
 Ayende @ Blog
 B#
 Barry Gervin's Software Architecture Perspectives
 Boy Meets World
 Brad Abrams
 Canadian Developers
 Christopher Steen
 Claritude Software News
 Clemens Vasters: Enterprise Development and Alien Abductions
 Coding Horror
 Coding in an Igloo
 Dare Obasanjo aka Carnage4Life
 Darrell Norton's Blog [MVP]
 David Hayden [MVP C#]
 Don Box's Spoutlet
 Eric Gunnerson's C# Compendium
 EZWeb guy: Jeffrey Palermo [C# MVP]
 Fear and Loathing
 Generalities & Details: Adventures in the High-tech Underbelly
 Greg Young [MVP]
 Greg's Cool [Insert Clever Name] of the Day
 IanG on Tap
 Ingo Rammer's Weblog
 ISerializable - Roy Osherove's Blog
 James Kovacs' Weblog
 Jason Haley
 Jean-Luc David
 Jeremy D. Miller -- The Shade Tree Developer
 JetBrains .NET Tools Blog
 Jimmy Nilsson's weblog
 John Bristowe's Weblog
 John Papa [MVP C#]
 Jon Skeet's Coding Blog
 JonGalloway.ToString()
 Jump the Fence or Walk Around
 Lambda the Ultimate - Programming Languages Weblog
 Larkware News
 Lutz Roeder
 Marquee de Sells: Chris's insight outlet
 Martin Fowler's Bliki
 Mike Nichols - SonOfNun Technology
 MSDN Magazine - .NET Matters
 MSDN Magazine - All Articles
 OdeToCode Blogs
 Onion Blog
 Planet TW
 Raymond Lewallen [MVP]
 Rockford Lhotka
 RodMan's Corner
 Roger Johansson's blog
 Sahil Malik - blah.winsmarts.com
 Sam Gentile's Blog
 Scott Bellware [MVP]
 Scott Hanselman's Computer Zen
 ScottGu's Blog
 secretGeek
 Service Station, by Aaron Skonnard
 Signum sine tinnitu--by Guy Kawasaki
 Stephen Toub
 Steve Eichert's Blog
 Steven Rockarts
 The Blog Ride
 The Coding Hillbilly
 The Daily WTF
 TheServerSide.net: News
 Tim Gifford
 Vance Morrison's Weblog
 you've been HAACKED

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 519
This Year: 28
This Month: 0
This Week: 0
Comments: 1593

 Thursday, July 02, 2009
Thursday, July 02, 2009 2:00:00 PM (Mountain Standard Time, UTC-07:00) ( Tools )

One of the discussions that comes up with a lot with other developers that I talk with is the question of "How productive I would be if I were not able to use the tools/frameworks that I use to make me a much more productive software developer." The basis answers is: "much less". Having worked in environments where people can be forced to use "standardized" developer images with a common toolset that give no room for individual customization, I can tell you that the observations I have made are a couple of the following:

-Unwilling acceptance of substandard tooling to get the job done
-Potential ,in reality very often often, loss of individual developer productivity
-Developer frustration on a daily basis with the "policing" rules that are in place
......

I stopped the list short as it can really go on and on.

The reason that the standardized developer machine cannot work is that every developer "wields their lightsaber differently". The tools and customizations that I have made to my machine are the steps I have taken that allow "me" to achieve great levels of productivity. I have to stress these are the tools that make me productive. They make me productive because I know how to use them, I have taken the time to hone my ability to use them. I can't expect that another developer who comes onto my machine would be as productive if they were not familiar with the tools/techniques.

Of course if I were to bring another developer to pair with me on my machine and they were not proficient in using these tools, they would be just as unproductive (initially). It is more likely that they have a set of tools/customizations that they have made to their machine that allows them to work extremely effectively. The point is that they are able to make the modifications to their individual machine that allows them to become more productive.

What are your thoughts on approaches to machine/software configurations in teams?

Develop With Passion!!