Soft Skills Engineering · Hands-On Engineering Podcasts · November 2026
Dave had said someone working across a seven-hour time gap needs good writing and a team that actually reads it. Jamison adds that AI-generated status write-ups won't get read.
…do this thing. Or you make it very easy for people to pick it back up in the morning and give feedback on it. Or I don't know. That's a thing you have to figure out: how do you make sure that you don't waste six hours of your day because you assumed the wrong thing and worked for a long time on it?
That is a fantastic question. And I think one of the ways you got to do that is really good writing and actually getting your team to read what you write, which is actually getting harder and harder these days.
If you send somebody a giant AI slop article of what you did the past day, good luck. Yeah. I'm not reading that crap. Yeah. If it's really important that they read it and understand or that you read it and understand, yeah, I think human care in the crafting of the content is probably more important.
You probably need a pipeline of these things. Like I'm thinking about a pipeline system where you say you've got docs you've written, maybe you're sitting down and reading them with your team on your remote meetings, getting buy-in and making sure everyone's aligned so that you can get to work on…
I think this also lends itself to more isolated tasks, right? It's just going to be hard to be iterating really quickly on a product with another person. So you might be working on some kind of like background infrastructure bit that is it's it's there's a lot of work in building it but kind of the…
yeah me too it's not very fun this