@jerryjliu0
Coding agents are fundamentally changing software engineering in terms of velocity, role, and org structure. We published a memo to our internal engineering team detailing our growing expectations in terms of role/scope. 🟠 Before, the tasks of prioritization, engineering planning, and implementation were divided between EMs, PMs, senior ICs, and junior ICs 🟢 Now, ICs are expected to handle *all* of product prioritization, product speccing, and implementation This is due to a few trends 📈: - Coding agents have brought implementation costs down to ~0. The role of engineers is writing prompts - LLMs and sub-agents have reduced the PM work of synthesizing feedback down to ~0 too The main job of any “engineer” is to be an e2e product owner: being able to translate requirements into specifications, and delegate tasks to various subagents for implementation. Every engineer is told to offload as much as possible to their favorite tools, whether it’s Claude Code, Cursor, Devin, Codex, regular ChatGPT and more. We celebrate and share learnings around burning tokens, as long as it helps drive additional productivity!