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.
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.
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.
As AI tools become part of developers’ everyday workflows, a lot of engineering leaders assume that getting started is just a matter of buying the right software.
Mackenzie Jackson, security researcher and advocate, told me that AI can’t catch the bugs, but it knows which ones actually matter and provides the context teams need.
The secret behind enabling teams to react swiftly and achieve optimal productivity without compromising compliance.
> subscribe shift-mag --latest
Sarcastic headline, but funny enough for engineers to sign up
Get curated content twice a month
Written by people, not robots - at least not yet. May or may not contain traces of sarcasm, but never spam. We value your privacy and if you subscribe, we will use your e-mail address just to send you our marketing newsletter. Check all the details in ShiftMag’s Privacy Notice