|
My attitude when I start a new job: render myself redundant by developing a robust set of automated processes to deal with everything this side of project management. Besides, developing cool software is more fun then being a monkey pushing privileged buttons whenever the application development team throws their stuff over to your side of the fence. It's more fun for me anyway. I recently took a cursory look at Andrew Hunt and David Thomas' "The Pragmatic Programmer," and they argue what to me is clear through some combination of common sense and hard-earned experience: Tip 61 in their book is:
and here's their supporting scenario (which anyone in SCM should be able to relate to, quoted verbatim from page 231 of "The Pragmatic Programmer"):
IDE. Their system administrator gave each developer a set of instructions on installing add-on packages to the IDE. These instructions filled many pages - pages full of click here, scroll there, drag this, double-click that, and do it again." "Not surprisingly, every developer's machine was loaded slightly differently. Subtle differences in the application's behavior occurred when different developers ran the same code. Bugs would appear on one machine but not on others. Tracking down version differences of any one component revealed a surprise." Jeff Bunds Graduated UIUC 1998 with a degree in chemistry. Quality assurance at Wolfram Research. Developer at Packard BioScience (since acquired by Perkin Elmer). Now working as an applied architect with UBS in London.
Set as favorite
Bookmark
Email this
Hits: 6403 Trackback(0)Comments (0)
|
| Last Updated on Tuesday, 24 January 2006 04:54 |
TrackBack URI for this entry
Subscribe to this comment's feed