4 ms·
Having done both, I'd say: 1. In a startup you do it* 2. In a big company you document it * that's not to say you don't do some planning and sketching and th
by papa 18y ago
Having done both, I'd say:
1. In a startup you do it*
2. In a big company you document it
* that's not to say you don't do some planning and sketching and the like, but you don't need a ginormous stack of docs.
It's worth remembering that one significant reason for heavy documentation is accuracy/fidelity of ideas when transmitting/coordinating across a large team of people.
- bmj 18y agoI agree, but there can be some danger in this as the start-up grows. I worked for a "we'll figure it out as we go along" start-up, but as clients grew (and the original dev left) the rest of us were left with nothing more than generally uncommented code as documentation.