@bcherny How do you handle sharing skills, commands, etc with multiple repositories? Just check them in everywhere and do a bunch of prs on each change?
I'll be speaking today at GlueCon on why measuring developer productivity is a terrible idea (and what to do instead). Come by and say hi!
https://t.co/8FiPr15ibc
@repus_dvorak @GergelyOrosz I interpret deployment frequency as any change to prod, including feature flags. Therefore, using progressive delivery, you can recover in seconds.
@sobes@GergelyOrosz@bajicdusko I don't think these are mutually exclusive. There is value in a consistently applied set of standardized metrics proven to strongly correlate to high performing teams, but also in a team taking ownership of what they track and improve.
@GergelyOrosz Measuring metrics doesn't improve anything, but it can let you know if your efforts to improve are working (and continue to work as you scale).
All the more reason to measure on the right metrics such as team output (DORA metrics) vs distractions (tickets closed)
@GergelyOrosz@bajicdusko For a high performing team, agreed you don't need DORA metrics to drive change, but they can still be useful to help track performance as the team grows and changes. Think a CPU monitor alerting on 80% cpu when you generally sit at 30%.
💥Episode Up!💥
@sleuth_io is a way to get metrics about deployments that will "make shipping less stressful for developers" — @mrdonbrown will teach us how!
Watch Here! 👀 ⬇️
https://t.co/IveXBtEMvf
For those that missed the stream, I lightly edited the 3D-printed, RGB Sleuth logo unboxing and programming into a youtube video: https://t.co/FN9YSSRb6e
Thanks again Andy!