My Secret Life as a Spaghetti Coder
home | about | contact | privacy statement
A great development team is an asset that gains you competitive advantage in the marketplace. They churn out features quicker than other teams, with higher quality code that contains fewer defects. You give them project after project and they routinely meet or exceed the deadline.

They're well known for hitting on all cylinders often enough to pull off seemingly miraculous feats of software engineering.

All is right in your world.

It's relieving to know you have a team you can trust, and your team members take pride in knowing that you believe so highly in their skills that you rely on them in the squirreliest of circumstances.

The pitfall shows itself when, instead of enjoying the benefits of such a team, you start to rely on those benefits. You start to assume the "firing on all cylinders" is the norm, and schedule accordingly. You let yourself believe those miraculous deliveries means you can put off important decision making until a week before they need to be delivered.

As long as everything goes good, you're in the clear. And it normally does. But what happens if someone gets sick or has a family emergency to attend to? What happens if your team just can't maintain that sort of intensity indefinitely?

You're going to be late. What's worse is you needn't have been so if you would have remembered to plan for things like that.

It's just a word of caution: don't assume perfection, even if empirical evidence suggests otherwise.

Hey! Why don't you make your life easier and subscribe to the full post or short blurb RSS feed? I'm so confident you'll love my smelly pasta plate wisdom that I'm offering a no-strings-attached, lifetime money back guarantee!

Leave a comment

As a one man team, I often find myself falling into the same pit you describe. It may be human nature, or ego, or just pride that often pins you into a corner at the last minute trying to meet an expectation promised long before 'real world' hurdles come into play. In my previous career (as a painter) I was told to bid 1.5x the proposed labor, and more often than not (even in this industry) I am finding that is more accurate in the end...

Posted by Seth Johnson on Nov 04, 2009 at 08:57 PM UTC - 5 hrs

Leave a comment

Leave this field empty
Your Name
Email (not displayed, more info?)


Subcribe to this comment thread
Remember my details

Picture of me

.NET (19)
AI/Machine Learning (14)
Answers To 100 Interview Questions (10)
Bioinformatics (2)
Business (1)
C and Cplusplus (6)
cfrails (22)
ColdFusion (78)
Customer Relations (15)
Databases (3)
DRY (18)
DSLs (11)
Future Tech (5)
Games (5)
Groovy/Grails (8)
Hardware (1)
IDEs (9)
Java (38)
JavaScript (4)
Linux (2)
Lisp (1)
Mac OS (4)
Management (15)
MediaServerX (1)
Miscellany (76)
OOAD (37)
Productivity (11)
Programming (168)
Programming Quotables (9)
Rails (31)
Ruby (67)
Save Your Job (58)
scriptaGulous (4)
Software Development Process (23)
TDD (41)
TDDing xorblog (6)
Tools (5)
Web Development (8)
Windows (1)
With (1)
YAGNI (10)

Agile Manifesto & Principles
Principles Of OOD
Ruby on Rails

RSS 2.0: Full Post | Short Blurb
Subscribe by email:

Delivered by FeedBurner