The higher you're your bar for safety and securities, the more you should care about this. You can only get so much confidence in your code until some one's using it. The best practice is to ship from one to fat, from one engineer at a time. If if you can't do that quickly, then you're ging to start batching, i up, anywhere from one to 50 enginesdifts.
Charity Majors, co-founder, and CTO of honeycomb.io, joins us to talk about everything that's wrong with engineering cycles, how throwing money at the problem by hiring more people is making it worse, and what we can do about it.
Find out:
- How to create systems that increase software engineering productivity,
- Which toolsets can enable shorter feedback loops,
- How elite teams have figured it out,
- How infrastructure engineering is key to all of this and more!
Deep dive into the topics discussed in this episode at go.developingleadership.co/ep22
Join the discussion and follow us on twitter @ devleadership_
Developing Leadership is a podcast presented by Athenian. We are introducing the world of engineering to metrics and data that improve processes and help teams. If you want to learn more about data-enabled engineering, go to athenian.com