A product requirements document is a short, shared artifact that states the core problem a piece of work solves and what has to be true to call it done. It is not a full spec with every edge case and acceptance criterion. It sits higher than that: the problem, the goals, the boundaries of scope, […] The post Build Alignment…
#personal optimization
5 posts
18 Jul
15 Jul
With the rollout of Atomic Object’s agentic delivery model, keeping my thoughts straight has been more challenging than before. Though agentic delivery noticeably speeds up the implementation process, it also increases context-switching for team leads and product folks. It feels more pressing to keep my memory and thought processes in good order. Something that helps […] The post How I’m…
27 Jun
Years ago, I started a Zettlekasten-style collection of notes using Emacs’ org-roam package. A Zettlekasten system is typically comprised of hundreds of linked notes covering all topics of interest to the maintainer (if you’re interested in learning more on such systems, I recommend the book How To Take Smart Notes by Sönke Ahrens). It can […] The post Teach Your…
22 Feb
As a software developer, I spend much of my day thinking about reliability, automation, eliminating repetitive work, and building tools that help me do my best work. Most of that effort is focused on serving project goals and delivering high-quality software. But my sense of purpose at Atomic comes from more than just the code […] The post Never Missing…
21 Feb
When you’re first starting your career, there are a lot of day-to-day tasks that a college degree doesn’t adequately prepare you for. You might even find that skills you thought you knew how to do just aren’t transferable. One of the things I’ve had to relearn is note-taking. How note-taking is different in the office […] The post Upgrade Your…