aprinsen

We've all been there: waiting for brew, waiting for a CI pipeline, running the full integration suite, xcode doing anything at all.

What's your useful advice for staying "on task" when your dev cycle is peppered with 15-120 second interruptions?

Of course where possible we should pour effort into minimizing these interruptions but for this question I'm talking mental tricks etc.

This type of thing may go by different names, but I'm talking about the sort of regular meeting where engineers and perhaps product folks discuss a list of possible work items individually to clarify, prioritize, and estimate effort.

I've often found it hard to keep these meetings engaging, so I'm curious if folks have tips for running them. What has worked for your teams? What should be avoided?