When Slack Isn’t Enough

Tech teams need to communicate. Many have ritualized this into a daily “standup.”

I have an alternative way. It’s push-to-screen record.

You press a hotkey and your (main) screen + default audio starts recording in milliseconds. No dialog, confirm, or start buttons.

Press the hotkey again to end and, if you don’t intervene within a minute, post it for others to see in a sort of “social network” feed.

Why might you try to integrate this into your development process?

Think about how communication occurs during developer interviews, or pair programming. A good candidate will verbalize the algorithm they’re writing, and verbalize any issues they’re thinking about when they stop coding.

This style of communication, if done in production software development, will result in the following benefits:

• Eliminate the need for standups, while providing a greater level of understanding of where things really are at
• Accurately gauge developer activity. They can show how they’re trying to solve the problem, even if they don’t have a solution yet
• Increase productivity by having “rubber duck programming” ritualized that can reduce the amount of breaks developers take because they answer their problem while talking about it
• Speed up code reviews: If developers watch each other’s postings, they can see how things are being implemented giving them a useful background when reviewing the commit later
• Help out another dev if they’re stuck and you know the answer
• Catch bugs or the wrong approaches being taken, before time has been wasted going down that path

This product essentially allows you to get the benefits of pair programming, without the cost of having two devs be together.

To book a demo, leave your email and I will reach out