3 ms·
Having a meeting involves more than 1 person spending time. Reading a spec involved only one person investing time (only those that need to know it anyway). Do
by Aeolun 5y ago
Having a meeting involves more than 1 person spending time. Reading a spec involved only one person investing time (only those that need to know it anyway).
Doing it in a meeting where everyone has different questions, tangents and other cruft that you have to sit through is extremely inefficient.
- yibg 5y agoYes but if you have 2 part time devs, that requires 2 people spending time. The discussion here isn't meetings vs doc, it's full time vs part time.
- keerthiko 5y agoIf you have 2 part time devs with a manager giving them the info in the meeting, that's 3 people spending time, and the two part-time devs won't have 100% overlap of information needed and questions asked and answered (and if you have two separate meetings with each PT, then they won't have access to the questions/answers discussed with the other dev _in case_ they need it). Additionally, everyone can focus on producing and consuming information in the downtime between focus-work sessions, without interrupting flow at someone else's convenience. In all cases, quality documentation is more likely to produce accurate information transfer with less time wasted by everyone involved.
- yibg 5y agoI dunno. I for one wouldn't want to work at a place where I'm just handed a bunch of docs to implement. I want to be able to ask questions for clarification, suggest alternatives etc. All of which takes time.