https://www.stuartdesk.com/blog Practical notes on calls, code and keeping your word, from the person building Stuart. en https://www.stuartdesk.com/blog/getting-back-into-code-after-an-interruption https://www.stuartdesk.com/blog/getting-back-into-code-after-an-interruption Sun, 27 Sep 2026 00:00:00 +0000 Focus A meeting, a message, a weekend. Here is why coming back to code is slow, and five small habits that make it fast. https://www.stuartdesk.com/blog/write-your-standup-from-what-you-actually-did https://www.stuartdesk.com/blog/write-your-standup-from-what-you-actually-did Sun, 27 Sep 2026 00:00:00 +0000 Work 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. https://www.stuartdesk.com/blog/call-recording-consent-guide https://www.stuartdesk.com/blog/call-recording-consent-guide Sun, 27 Sep 2026 00:00:00 +0000 Calls A plain guide to consent for recorded and transcribed calls: one-party and all-party rules, calls across borders, and what to actually say. https://www.stuartdesk.com/blog/keeping-track-of-promises-you-make-on-calls https://www.stuartdesk.com/blog/keeping-track-of-promises-you-make-on-calls Sun, 27 Sep 2026 00:00:00 +0000 Calls “I’ll send that over” is easy to say and easy to forget. A few habits keep casual promises from quietly slipping. https://www.stuartdesk.com/blog/why-every-answer-should-come-with-a-source https://www.stuartdesk.com/blog/why-every-answer-should-come-with-a-source Sun, 27 Sep 2026 00:00:00 +0000 Product 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.