3 ms·
In a team/large company context, yes - a spec gets made then some (usually someone else) gets to write the code. In a smaller context one, or two, people may b
by bruce511 4y ago
In a team/large company context, yes - a spec gets made then some (usually someone else) gets to write the code.
In a smaller context one, or two, people may be responsible for design and code. Assuming they have a good understanding of the problem space they may start with some practical things (like database design) then program, then document (if you're lucky)
So, as with most things, context matters.
- DigitalSea 4y agoYou are completely right. Context definitely matters. The smaller team angle isn't something I thought about when I wrote my comment.
- dgb23 4y agoIf you work on client projects in a small team then a functional spec can help you keeping everything conceptual in one place and have a basis for discussion. It doesn’t have to be the most elaborate thing. A smaller project gets a few pages with some pictures, a more involved one has more explanation and database diagrams, a few stories and such. You do this work anyway, so why not write it down in a structured way? Pragmatic and simple but clear and neat. You’ll find that people do not tend to read every detail, but you can refer to the details when needed, which is very useful.