We asked engineers how far AI can really go in software delivery, and their answer was simple: it can speed things up, but people still have to make the decisions.
Anyone who’s clicked "always allow" on an agent knows the outcome: broad permissions, minimal oversight, and results that are correct on paper but strange in practice.
As AI tools reshape how software is built, the engineers in our new video say the job is shifting from writing every line by hand to guiding, reviewing, and orchestrating what AI produces.
When tech company ustwo assessed one AI product’s carbon footprint, they found most came from AI inference. It raised a question: if AI has a measurable environmental impact, why is it almost invisible to everyday users?
Watching AI product evolution from the sidelines makes you feel like things are going fast, but according to Anthropic's Gian Segato, that might not be the best metric.
A CTO with 20 years of experience through multiple tech shifts sees layoffs not as an AI effect, but as a correction after an unsustainable hiring boom. He sees AI as a reset: an opportunity for strong junior engineers, and a wake-up call for senior developers facing an existential shift in how they stay relevant.
At Devoxx UK, I spoke with Trisha Gee - author and one of the most recognized voices in the Java space - about what really happens when teams lean heavily on AI. Her take was far darker than the conference hype.
Production incidents are a context problem. By the time an engineers understand what's happening, they've already bounced across several different tools - and the incident is still ongoing. PagerDuty thinks MCP is the fix.