The Developer Role, Redefined

Developer = Product + Architect + QA. That is the role of a software engineer today around the new reality brought upon us by AI agents. And if that formula sounds reductive, stay with me — because I think it describes what great developers have always done, and what every developer now needs to do deliberately. This isn't new — it's newly visible Developers have always worn these hats. You've always pushed back on requirements that didn't make sense. You've always made architectural calls — choosing a pattern, weighing a trade-off, deciding what to abstract and what to leave concrete. You've always been the last line of defense before code ships, testing the edges, catching what the specs missed. What varied was the mix. A developer with deep domain experience leaned heavier into product thinking. Someone on an infrastructure team lived in the architecture space. A developer on a small startup team with no QA department? They became QA out of necessity. The distribution was always per