Show notes
Engineering docs don’t have to be boring. We’ve all written (and skipped reading) those 50-page design docs that are technically accurate but put you to sleep by page 3. This article explores when to lean into storytelling, when to stay technical, and how to find the sweet spot where your docs are both precise and actually readable. Spoiler: it’s not an either-or choice.
If you like written articles, feel free to check out my medium here: https://medium.com/@patrickkoss
The Document Nobody Reads
Picture this: You’ve just spent three weeks writing the most comprehensive design document of…
Website: patrickkoss.substack.com

