Everyone Feels Faster. Almost Nobody Can Prove It.
What 554 developers and engineering leaders told us about AI, agents, and the measurement gap nobody’s closing. Ask a developer if AI made them faster
What 554 developers and engineering leaders told us about AI, agents, and the measurement gap nobody’s closing. Ask a developer if AI made them faster
TL;DR: There have been a couple tweets and posts about the AI adoption curve that I found interesting: I highly recommend reading the original posts
AI coding tools were supposed to mean developers work less. On a recent webinar recorded with LeadDev, senior engineering manager Vernon put words to something
Splitting one big pull request into five smaller ones doesn’t automatically make review faster. It just moves the complexity from the diff to your head,
Most companies buy AI tools for developers and hope the impact shows up somewhere. A faster sprint. Fewer escaped bugs. Something. What they don’t have
Most companies will tell you they’re customer-obsessed. Fewer can point to the actual mechanism. At GitKraken, it isn’t a quarterly survey or a roadmap council.
The Commit Graph is where your development and agentic workflows come together. Visualize branches and commits, manage parallel work and agents, and run your entire
The secret sauce that powers Agentic Development Environments (ADEs) like Kepler is a little thing called the Agent Client Protocol (ACP). In this context, Kepler
The State of AI In Engineering Everyone feels faster. Almost nobody can prove it. AI is now part of nearly every engineering workflow, and developers
Leadership has stopped asking whether your team is using AI. They’re asking what you’re delivering with it. That’s a harder question, because most of the
winget install gitkraken.cli