Here's part one of a post I shared with our team on the radical change and evolution of our jobs. AI won't make software engineers redundant. It will expose what engineering was always supposed to be about: understanding systems, not just writing code.
Reflecting on whether teaching traditional coding skills still makes sense in 2026. Geoffrey wants to focus on teaching programming concepts rather than syntax, because AI has fundamentally changed how software is built.
The first Jump Start Competition has a winner. Three promising teams, one jury decision, and a strong start to hands-on collaboration with madewithlove. Here are the winners!
CTOs often come from engineering backgrounds and, particularly when newly promoted, tend to focus on what they know best, the technology. While this is understandable given their previous success, technology is rarely the hardest part of the CTO role.
Early-stage startups want full-stack unicorns who can do it all on a tight budget, but asking one dev to wear every hat is less strategic hiring and more duct-taping a rocket and hoping for the best.
By 2030, nobody will write code anymore and here is why. The difference between agent-powered engineers and those who handcraft code is huge. Here's our prediction on software engineering.
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
LLMs generate code on demand, but they do not replace maintainers, communities, or years of shared learning. This piece explores how AI-assisted coding risks fragmenting logic, increasing technical debt, and slowly eroding the open source ecosystem.
