Are corporate programmers bad for startups?

Kevin Dewalt suggests that programmers with experience in large corportions are bad for startups, because the emphasis in corporations is on doing things the right way, whereas the emphasis in startups has to be on cutting corners so that you can hip quickly:

So how did I design the database for my most recent startup? Having been in situations where poorly managed database relationships resulted in months of rework, I used foreign keys. That was my experience, and I’m guessing the experience of the developers who made the comments above.

Unfortunately I found that foreign keys in my Rails migrations were a constant source of headaches. Moreover, I decided to migrate to Heroku during the project and had to re-write the foreign keys for Postgres instead of MySQL. What did I learn about customers in this process? Nothing.

In retrospect, I believe I followed bad practice for lean startups building working prototypes. Database integrity is an important issue when you have achieved some measure of success.

May I be so blessed to have these type of problems in my next startup.

One Response to “Are corporate programmers bad for startups?”

  1. Closer To The Ideal » Blog Archive » What comes after the prototype? Says:

    [...] http://www.teamlalala.com/blog/2009/11/07/are-corporate-programmers-bad-for-startups/ [...]

Leave a Reply