That’s definitely on how works in real life. You have your decisions and then…some context brings questions. Thank you ! 😊

Woooow, this is cool, i was thinking about this and wasn’t sure…good idea !

I remember one hands-on code workshop that I attended gave a very simple example of the business project and while coding we were able to identify the pain points because of that 💖

@tekiegirl.bsky.social is the best ♥️

This is very interesting, I’ll take a look for sure

Likewise! For more effective communication and documentation!

Of course ! Thank you for laughing with me and teaching @golang.org to the #OrlandoDevs community! 💻

Then also @williamcook.dev brought the fun and sad parts of using @golang.org in a fun presentation. We know that go users are there because of the cute mascote! #OrlandoDevs rock it !

Exactly, using just those metrics to take decisions is not the best idea

I’m not saying that they aren’t useful or perfect, but if you base all your products on the Dora metrics then you aren’t looking far enough

I’ve experienced that some managers just care aboutDora metrics and some products like payroll or payments gateways don’t need to be changed so often.The important thing there is the time to recover,but do infinite commits just to get a metric up is the same as test minimum things just for coverage

The new Voldemort

I agree partially with this, because also DORA metrics can be use for the “evil”, what about if the product does not need to change so often? The one that I really like is the time to take to go back to business…and even that one can be controversial if it is not “that important”. Always depends