PHP'ers:
Ben Ramsey
Brandon Savage
Cal Evans
Chris Shiflett
Eli White
Elizabeth Naramore
Joe LeBlanc
Justin Thorp
Mike Naberezny
Rasmus Lerdorf
Tony Bibbs
Zend Blogs
Zend DevZone
DC Social Media:
Aaron Brazell
Geoff Livingston
Jessie X
Ken Yeung
New Media Jim
Shashi B
Social Times
Technologists:
Jimmy Gardner
O'Reilly Radar
Scott Berkun
Steve McConnell
Business/mISV:
Bob Walsh
Eric Sink
Gavin Bowman
Guy Kawasaki
Joel Spolsky
Micah Baldwin
Paul Graham
Planet mISV
Past Projects:
CodeSnipers
HOBY
Judicial Watch
mobile Fox Affiliates
mobile FoxNews.com
MyDearJohnLetter
NRTW
techRepublican
Great Tools I use:
BaseCamp
Drupal
getClicky
Highrise
phpUnit
Qcodo
Subversion
web2Project
Zend Framework
This is not the home of dotProject. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
Some points, but I think you're off...
You note:
While you are 100% correct that many startups do this, I think it's the fundamentally wrong way to go.
This is when the risk is the largest. This is when the spec is the softest. This is the primary time that if something is going to go screwy, it can damage things fundamentally and for a long time to come. This is the time where you need yor key players to be close and "smackable" if something isn't right.
Later on, once the foundation is in place, things are solid, and the early decisions are made correctly, it's much safer to spread things out. Because it's harder to do major damage. Not impossible, but harder...
And I mean "smackable" in the least violent sense possible. ;)