Blog
Practical notes on calls, code and keeping your word, from the person building Stuart.
Where was I? Getting back into code after an interruption
A meeting, a message, a weekend. Here is why coming back to code is slow, and five small habits that make it fast.
Write your standup from what you actually did
Standups go wrong when they are written from memory. Here is a simple format, and the commands that pull the truth from your own work.
Recording or transcribing a call? Tell people first
A plain guide to consent for recorded and transcribed calls: one-party and all-party rules, calls across borders, and what to actually say.
The promises that slip: keeping track of what you said on calls
“I’ll send that over” is easy to say and easy to forget. A few habits keep casual promises from quietly slipping.
Why every answer should come with a source
A fluent wrong answer is worse than a slow right one. Why Stuart puts a source on every sentence, and says “Not sure” when it has none.