Faster feedback loops make for faster developer velocity (Ep. 499)

If you want a fast highway, you should have fewer cars. 

Article hero image


When some people hear the phrase “developer velocity,” they cringe and think about delivering an increasingly large number of story points during a sprint. Others push to tighten feedback loops for engineers in order to remove the roadblocks between writing code and getting it into production. But few will understand that much of the “feedback” in that loop is human, so giving them a little more slack lets them provide feedback faster. After all, if you want a fast highway, you should have fewer cars.

On this sponsored episode of the podcast, Ben and Ryan talk with Matthew Groves, Senior Product Marketing Manager at Couchbase, and Cory House, the founder of Reactjsconsulting.com and a Pluralsight course author, about how to increase velocity without increasing pressure on your engineers, whether cloud native technologies can help (or hurt), and how to design your toolchain so it improves velocity.

Show notes

Having trouble with understanding your team’s productivity outside of frameworks and tooling? Create a backlog and work through it: Instant Agile! How much of that backlog you work through is a good baseline measure.

The Stack Overflow blog recently featured an article from Stack Overflow’s Director of Engineering, Ben Matthews: Does high velocity lead to burnout? That may be the wrong question to ask

If you're interested in seeing how Couchbase’s SQL database solutions can help improve your team’s velocity, check out Capella.

Cory House helps teams deliver successful React projects through his consulting business, ReactJS Consulting.

If you want to learn more about Matt, check out his LinkedIn.

Congrats to Lifeboat badge winner, Alohci, who threw a great answer to rescue the question, Display button with inline CSS.


Login with your stackoverflow.com account to take part in the discussion.