Menu

When the ticket says "as discussed," go back to the recording
📰

When the ticket says "as discussed," go back to the recording

DEV Community: beginners·David Wang·about 6 hours ago
#E6U7ScXd
#devtobeginners#devto#dev#later#meeting
Long article (1270 words) — no AI summary yet.
Reading 0:00
15s threshold

By Alice

Disclosure: This article was written with support from VoxStudio. I'm Alice, and I use VoxStudio for Mac. The method below is meant to stand on its own, even if you never open that app.

A pull request comes back with a one-line comment: "Let's go with option B, as discussed on Thursday." Two weeks later, someone asks what option B actually ruled out. The design doc was never updated. The Slack thread jumped to a deploy issue halfway through. The person who ran the meeting is out.

This is ordinary. A lot of engineering decisions are made out loud, then a three-bullet recap gets treated as the record. Summaries are useful. They are also derived artifacts. If a version number, an owner, or a verb is wrong, the error travels farther than the original sentence ever did.

The habit that has helped me is almost boring: keep the recording when you are allowed to, get a transcript, and refuse to trust any later write-up until you can point to the moment in the audio.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.