3 ms·
This is good sometimes, other times it risks losing the audience. Extra info works better when they're ready (i.e. asked for it). This is why it's such a diffic
by hakunin 2y ago
This is good sometimes, other times it risks losing the audience. Extra info works better when they're ready (i.e. asked for it). This is why it's such a difficult balancing act. You don't want to preemptively answer questions that people didn't realize they should ask yet.
- Atotalnoob 2y agoI usually have my assumptions written, so I can flip to them quickly if there is any confusion
- _heimdall 2y agoFor sure, I was mainly thinking about later stage discussions where decisions like tech stack, architecture, or infrastructure should really be made. Early on its often all about use cases and users you're trying to reach. If microservices versus monoliths becomes much of a debate that early engineering is probably getting too far ahead of the product IMO.