An IDE should act as a system that manages the entire Software Development Life Cycle process, including Business Requirements Documents (BRD), requirements workflows, and ticketing, especially for Team Leads and Architects.
Yesterday I wrote that my IDE is GitHub, and many people asked what that really means in the era of AI led development. So here’s the continuation of that thought. Right now the industry is in an IDE race. Everyone is trying to build the “AI native editor” that will define how developers work. But after spending the last year building agentic workflows across real engineering teams, it’s clear that the biggest shift isn’t happening inside the editor at all. ‼️ The real transformation is happening in the workflow layer where tickets, PRs, approvals, context, and decisions live. AI agents don’t fit naturally inside a local IDE. They operate at the level of the SDLC: triaging issues, drafting requirements, producing designs, generating PRs, responding to code reviews, and moving work forward across multiple roles. And all of that already lives in GitHub and Jira, not inside an editor. So instead of replacing the IDE, we should rethink the interface where humans and agents collaborate. 🤯 I wrote a deeper, more detailed piece about this shift, why the current direction is incomplete, and what a better model could look like. If you’re curious about what the next generation of software development actually feels like when humans and agents share the workflow, here’s the full post: 👉 https://lnkd.in/gZYexpAk Would love to hear your thoughts.