Engineering teams are starting to resemble legacy Java apps hitting thread exhaustion. I believe change is unavoidable, and we need a better way to organize the work.
> 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
I let the dust settle, and this is what I think: regular apps usually need teams of dozens to ideate, build, and test before they ship. Odysseus, PewDiePie’s new AI platform, doesn’t - at least, not in the usual way.
At the AI Engineer conference in San Francisco, I heard Instagram co-founder Mike Krieger say developers no longer need to review every line of code by hand. The real job now is judging AI’s decisions and whether the product solves the right problem.
A new kind of builder is emerging inside organizations - one that works fast, ships often, and rarely follows the instincts of a software engineer. That raises a simple question: what happens to security?
That mismatch is becoming the real cost of AI-assisted development: code ships faster, but the work of understanding it, checking it, and trusting it hasn’t sped up at all.
The jump from mid-level to senior engineer is often framed as a technical one. Michelle Brenner says the real difference is judgment: understanding the business, making pragmatic trade-offs, and knowing when to ask for help.
I went to Raise Summit in Paris to see whether Lovable is just another tool for non-technical founders - or something developers can actually use to build faster.
Building software is full of ups and downs. Some days, you're working with the best team you can find, and others it's up to you to fix something with no idea how it works and no access to documentation.