41–43 of 43 posts
It’s remarkable (but not reassuring) how carefully they avoid saying “part of the Atlassian family” in any promotional material for some reason.
my current place uses DX and it's well received, if done transparently and for the right reasons. there's a lot of very interesting research in these areas (e.g. EngThrive) where the focus is on measuring things that if gamed result in better outcomes there's strong correlation when onboarding an engineer between the time to first/tenth/fiftieith PR and their PR throughput two years later, so the answer is make it re…
honestly asking, whats the point of measuring time to first, etc. PR when it is all done by AI these days?
correlating all of these let's you know if you're accelerating one activity metric but getting worse in an outcome metric - lots if slop PRs but more incidents is obviously the wrong outcome, and can be addressed by improving local verification, safer deployments, faster rollbacks, better observability, etc.
even with AI writing the code (and much more) all of these things matter. actually seeing positive outcomes (and thus RoI from AI use) requires knowing what's signal and what's noise. ive spoken to founders who see anecdotal increases in everything negative as their AI code volume goes up, and none of them are actually measuring anything effectively enough to understand what to do about it