Documentation Formality and Developer’s Turn Rate

I’ve been working almost 3 years in the small company now (company with < 10 members). It’s an interesting point that most of our problem is that our developers gone so fast. Once they come, another 2-3 months they might gone forever. So, developing internal company capabilities are very difficult.

Lately, my company pushes the design formalization up to the limit. We have detailed documents about requirements, database design, protocol convention, architecture, stage plan, milestones, etc. It’s a bit tough for small company, where all of your work is changed into creating documents (we’re developers not type-writers anyway)…

But I guess this is just because I’m not used to it. For a long term, documents like these can save the company in the long term, because they can hold the knowledge inside.


    Leave a Reply

    Fill in your details below or click an icon to log in: Logo

    You are commenting using your account. Log Out /  Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out /  Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out /  Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out /  Change )


    Connecting to %s

  • Recent Posts

  • Archives

  • Categories

%d bloggers like this: