In June 2026, Stack Overflow unveiled a full rebrand by studio Koto, repositioning from Q&A platform to “the world’s most vital source for technologists” right as monthly new questions on the site are down roughly 77% since ChatGPT launched. The brand investment and the traffic freefall are happening simultaneously. That is the context for Ishan Gupta, a software engineer at Amazon, and his five-phase history of how the old engineering workflow collapsed.
Software engineering was a craft you absorbed slowly, then practiced in a long, predictable sequence: Dive deep on the technology, write the code, ask Stack Overflow when stuck, escalate to a senior engineer when Stack Overflow failed, ship the ticket. The product manager owned the funnel. The engineer owned the build. Both sides treated this division as physics.
That division is dissolving. Gupta traces it through the IDE-native era (e.g., GitHub Copilot and Cursor), the spec-driven era, and the Claude Code Routines era (Anthropic’s scheduled, persistent agents). At each step, another piece of work that used to require a human gets handed off. Gupta’s diagnosis:
Anthropic recently told its growth team to hire more product managers, not fewer. The reason, as reported in industry coverage, was that Claude Code had quietly turned its engineering org into a team that ships at roughly three times its actual headcount, and the bottleneck moved from the integrated development environment (IDE) to the people deciding what to build.
That detail is easy to miss in the noise of every AI productivity claim. It is also the structural shift the rest of the industry is now living through. The bottleneck in software is no longer typing. It is deciding what to type. And the engineers who treat that as someone else’s problem are about to plateau.
That same shift is what Koto’s rebrand is responding to. Cat Hill, senior strategist at Koto, put the rebrand angle plainly: “In the AI era, everyone wants faster answers. But speed is useful only if the knowledge underneath is trusted.” For designers, that is the opening: the product-thinking gap is no longer a soft skill around the edge of engineering work. It is where the work is moving.
Gupta’s clearest description of the new engineering identity is also the case for why product judgment matters more:
The 2026 version of a great engineer is not the one who writes the most code. It is the one who knows what to build, can prove it is worth building, and has the agent fleet plus the review discipline to ship it without the system collapsing under its own velocity.
