My 🔥 take on interrupting developers: As a developer I want to be able to be
interrupted. This is what the agile manifesto rightfully points out: "The most
efficient and effective method of conveying information to and within a
development team is face-to-face conversation." >
3 replies
Replying to @coderbyheart
It is very likely that I can create more value by answering a coworkers question
than by continuously coding for hours.
If I need uninterrupted work for hours, I have optimized the way I work for
the wrong metrics.
I use TDD and can interrupt my work within seconds. >
Replying to @coderbyheart
I'll finish my current line of code, and maybe add a quick comment to the file.
I can even commit and push it to a WIP branch. When I get back I see the failing
test, and can quickly pick up the work again.
Here is a great video about this approach: https://youtu.be/a6oP24CSdUg >
Replying to @coderbyheart
This way I can be responsive to external events/ I am often traveling and not
always in full control over my schedule. This habit enables me to be productive
within a few minutes everywhere I find time.