The End of IDEs

https://aifordevs.substack.com/p/the-end-of-ides

Ten months ago, I talked about AI x Software Development (“Natural Language Coding”) and what it means for software development workflows and tools like the IDE.

GitHub's announcement of Copilot Workspace this week marks the start of the sunsetting of IDEs as the main interface for building software.

IDEs have been long, trusty companions for software developers. However, with the rise of AI-assisted dev workflows, the traditional IDEs days as we know them (= fancy code editors), are about to make ways for new tools and interfaces.

There’s a new paradigm in software development. Call it “Natural Language Coding” or “AI-assisted dev workflows”. It follows a specs-driven approach, where the role of human developers is to steer the wheel and guide the AI on how to write code, rather than actually writing the code themselves. Here is how it goes:

Issue description: Product/Engineer “open a ticket” and describe the scope of work: business requirements and high-level specs.
AI writes specifications: AI analyzes the issue, generates technical specs, and breaks it down into an actionable, step-by-step work plan - followed by a human review and refinement.
AI generates code: AI executes the steps defined in the work plan
Inner Feedback Loop: AI autonomously iterates using internal tools (tests, builds, linters, self-reflection).
Human Feedback Loop: The AI hands off the task to the operator for code review and revision.
Hand-off to CI Process (“Last Mile”): Once the operator approves, the AI creates a pull request, and the rest of the workflow continues: Other developers review code, the CI/CD process kicks in and may run tests or create preview environments. If CI/CD process fails, it may bring back the AI to re-work and edit the Pull Request.
Deployment 🚢

We need new tools and interfaces to facilitate the new collaboration model between AI and human developers. Could we implement them in current IDEs? Probably yes. Should we do it? Probably not, as natural-language coding workflows have almost nothing in common with traditional coding workflows.

I'm glad to see the industry adopting the new paradigm and shifting to AI-centric software development workflows that are not dependent on the IDE.

Cloud development environments (CDEs) like Gitpod and Github Codespaces set the stage for AI-native development environments. These environments facilitate AI's "inner loop"—automated iterations of code generation, testing, and refining.

Also, AI-driven development involves a lot of waiting, and these platforms allow AI to run asynchronously, away from the operator’s computer, freeing them to do whatever.

Even though the essay I’m paraphrasing (Hey @swyx, The End of Localhost) anticipates otherwise, Web IDEs and cloud dev environments have been slowly adopted by the mainstream. For me, AI-Native dev environments look like the next evolution of Cloud Dev Environments, with the huge benefits of coding from the mobile.

The other day, I took the bus to the office and solved 3 issues with my iPhone on the go. By the time I got to the office, I only had to review the code and make a few tweaks, and it was done. What’s that, if not the ultimate developer experience?

In this new era, code is no longer the “main dish” in software development. On the other hand, technical specifications are now becoming first-class citizens.

It reminds me of the concept of README Driven Development, introduced by GitHub's founder Tom Preston-Werner 14 years ago. When thinking of natural language coding, it seems relevant than ever. RDD advocates for crafting a clear and concise README before coding, serving as a blueprint for AI to generate accurate and aligned code. In a way, what we’re seeing now is RDD becoming a reality.

The promise of this new workflow is bigger though. Well-crafted specs provide valuable documentation of the thought process behind a project, preserving the rationale and decisions for future reference.

Mixed with some more LLM magic, this could be the key to understanding software projects and retaining knowledge in the organization.

Skepticism regarding AI's ability to develop software is understandable. Concerns about code quality, security, and maintainability are valid, as AI-generated code may be prone to errors or inconsistencies. Is it worth it? Will you end up spending more time reviewing code and fixing AI bugs?

The ones who will benefit the most are those who can find the right balance between AI-assisted automation and human oversight and can identify the appropriate use cases.

There is a learning curve. Coding in natural language is a skill most of us need to learn and improve (how many of you truly master technical writing?)
Prefer low-value tasks over high-value tasks. AI (usually) lacks the domain knowledge and contextual understanding that human developers bring to the table, so it works better for routine tasks: write a new endpoint, a unit test, add error handling or do a limited refactor.
“Good enough boilerplate”: If you’re looking for 100% working code exactly as you imagine it, come back in a few years. Expect 80% and be prepared to read and modify someone else’s code though, and you’d be surprised how powerful these tools are.

It’s going to be a long adoption process. Developers will not shift away from their beloved companions tomorrow morning, and IDEs will be here for a long time (I’m here to remind you some people still enjoy using VIM!).
While interfaces, tools, and practices might change, the essence of the software engineering job remains the same: Analyze a problem, and propose a beautiful, simple solution.
When we started Fine, we made a critical product decision: We decided to build Fine outside of the IDE. Though many people urged us to build it as an IDE plug-in, it was clear to us that AI would play a much more significant role in software development than just code completion.
Even though GitHub Copilot Workspace is a competing product with Fine, I felt somewhat proud to see them following similar design patterns and UX decisions we made months ago 🙂

I am excited about this future. I’ve been writing code for the last 15 years, and I’ve never enjoyed it as much as I did for the last year. Extraordinary times for everyone excited about Natural Language Coding!

Hey, it’s Dan 👋 I’m writing a practical guide about Natural Language Coding and AI in software engineering. Do you have any ideas? Let’s chat.

{
  "by": "danleshem",
  "descendants": 5,
  "id": 40246791,
  "kids": [
    40252698,
    40246934,
    40247184,
    40246792,
    40248810
  ],
  "score": 1,
  "time": 1714738505,
  "title": "The End of IDEs",
  "type": "story",
  "url": "https://aifordevs.substack.com/p/the-end-of-ides"
}

{
  "author": "Dan Leshem",
  "date": "2024-05-03T12:04:16.000Z",
  "description": "AI-Native Development Environment is about to take over traditional IDEs",
  "image": "https://substackcdn.com/image/fetch/w_1200,h_600,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faacff56f-bdfb-40a4-a7c1-6a28981dfece_1283x614.png",
  "logo": "https://logo.clearbit.com/substack.com",
  "publisher": "Substack",
  "title": "The End of IDEs",
  "url": "https://aifordevs.substack.com/p/the-end-of-ides"
}

{
  "url": "https://aifordevs.substack.com/p/the-end-of-ides",
  "title": "The End of IDEs",
  "description": "Ten months ago, I talked about AI x Software Development (“Natural Language Coding”) and what it means for software development workflows and tools like the IDE. GitHub's announcement of Copilot Workspace...",
  "links": [
    "https://aifordevs.substack.com/p/the-end-of-ides"
  ],
  "image": "https://substackcdn.com/image/fetch/f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Faifordevs.substack.com%2Fapi%2Fv1%2Fpost_preview%2F144269495%2Ftwitter.jpg%3Fversion%3D4",
  "content": "<div><article><div><p>Ten months ago, I talked about AI x Software Development (“Natural Language Coding”) and what it means for software development workflows and tools like the IDE. </p><p>GitHub's announcement of Copilot Workspace this week marks the start of the sunsetting of IDEs as the main interface for building software.</p><p>IDEs have been long, trusty companions for software developers. However, with the rise of AI-assisted dev workflows, the traditional IDEs days as we know them (= fancy code editors), are about to make ways for new tools and interfaces.</p><p>There’s a new paradigm in software development. Call it “Natural Language Coding” or “AI-assisted dev workflows”. It follows a specs-driven approach, where the role of human developers is to steer the wheel and guide the AI on how to write code, rather than actually writing the code themselves. Here is how it goes:</p><ol><li><p><strong>Issue description:</strong><span> Product/Engineer “open a ticket” and describe the scope of work: business requirements and high-level specs.</span></p></li><li><p><strong>AI writes specifications: </strong><span>AI analyzes the issue, generates technical specs, and breaks it down into an actionable, step-by-step work plan - followed by a human review and refinement. </span></p></li><li><p><strong>AI generates code: AI executes the steps defined in the work plan</strong></p></li><li><p><strong>Inner Feedback Loop:</strong><span> AI autonomously iterates using internal tools (tests, builds, linters, self-reflection).</span></p></li><li><p><strong>Human Feedback Loop: </strong><span>The AI hands off the task to the operator for code review and revision. </span></p></li><li><p><strong>Hand-off to CI Process (“Last Mile”):</strong><span>  Once the operator approves, the AI creates a pull request, and the rest of the workflow continues: Other developers review code, the CI/CD process kicks in and may run tests or create preview environments. If CI/CD process fails, it may bring back the AI to re-work and edit the Pull Request.</span></p></li><li><p><strong>Deployment 🚢</strong></p></li></ol><p>We need new tools and interfaces to facilitate the new collaboration model between AI and human developers.  Could we implement them in current IDEs? Probably yes. Should we do it? Probably not, as natural-language coding workflows have almost nothing in common with traditional coding workflows.</p><p>I'm glad to see the industry adopting the new paradigm and shifting to AI-centric software development workflows that are not dependent on the IDE. </p><p>Cloud development environments (CDEs) like Gitpod and Github Codespaces set the stage for AI-native development environments. These environments facilitate AI's \"inner loop\"—automated iterations of code generation, testing, and refining.</p><p>Also, AI-driven development involves a lot of waiting, and these platforms allow AI to run asynchronously, away from the operator’s computer, freeing them to do whatever. </p><p><span>Even though the essay I’m paraphrasing (Hey </span><a target=\"_blank\" href=\"https://twitter.com/swyx\">@swyx</a><span>, </span><a target=\"_blank\" href=\"https://dx.tips/the-end-of-localhost\">The End of Localhost</a><span>) anticipates otherwise, Web IDEs and cloud dev environments have been slowly adopted by the mainstream. For me, AI-Native dev environments look like the next evolution of Cloud Dev Environments, with the huge benefits of coding from the mobile.</span></p><p>The other day, I took the bus to the office and solved 3 issues with my iPhone on the go. By the time I got to the office, I only had to review the code and make a few tweaks, and it was done. What’s that, if not the ultimate developer experience?</p><p>In this new era, code is no longer the “main dish” in software development. On the other hand, technical specifications are now becoming first-class citizens.</p><p><span>It reminds me of the concept of </span><a target=\"_blank\" href=\"https://tom.preston-werner.com/2010/08/23/readme-driven-development\">README Driven Development</a><span>, introduced by GitHub's founder Tom Preston-Werner 14 years ago. When thinking of natural language coding, it seems relevant than ever. RDD advocates for crafting a clear and concise README before coding, serving as a blueprint for AI to generate accurate and aligned code. In a way, what we’re seeing now is RDD becoming a reality.</span></p><p>The promise of this new workflow is bigger though. Well-crafted specs provide valuable documentation of the thought process behind a project, preserving the rationale and decisions for future reference.</p><p>Mixed with some more LLM magic, this could be the key to understanding software projects and retaining knowledge in the organization. </p><p>Skepticism regarding AI's ability to develop software is understandable. Concerns about code quality, security, and maintainability are valid, as AI-generated code may be prone to errors or inconsistencies. Is it worth it? Will you end up spending more time reviewing code and fixing AI bugs? </p><p>The ones who will benefit the most are those who can find the right balance between AI-assisted automation and human oversight and can identify the appropriate use cases.</p><ul><li><p><strong>There is a learning curve.</strong><span> Coding in natural language is a skill most of us need to learn and improve (how many of you truly master technical writing?)</span></p></li><li><p><strong>Prefer low-value tasks over high-value tasks.</strong><span> AI (usually) lacks the domain knowledge and contextual understanding that human developers bring to the table, so it works better for routine tasks: write a new endpoint, a unit test, add error handling or do a limited refactor.</span></p></li><li><p><strong>“Good enough boilerplate”:</strong><span> If you’re looking for 100% working code exactly as you imagine it, come back in a few years. Expect 80% and be prepared to read and modify someone else’s code though, and you’d be surprised how powerful these tools are.</span></p></li></ul><ul><li><p>It’s going to be a long adoption process. Developers will not shift away from their beloved companions tomorrow morning, and IDEs will be here for a long time (I’m here to remind you some people still enjoy using VIM!). </p></li><li><p>While interfaces, tools, and practices might change, the essence of the software engineering job remains the same: Analyze a problem, and propose a beautiful, simple solution. </p></li><li><p>When we started Fine, we made a critical product decision: We decided to build Fine outside of the IDE. Though many people urged us to build it as an IDE plug-in, it was clear to us that AI would play a much more significant role in software development than just code completion.</p></li><li><p>Even though GitHub Copilot Workspace is a competing product with Fine, I felt somewhat proud to see them following similar design patterns and UX decisions we made months ago 🙂</p></li></ul><p><span>I am excited about this future. I’ve been writing code for the last 15 years, and I’ve never enjoyed it as much as I did for the last year.</span><em><strong> </strong></em><span>Extraordinary times for everyone excited about Natural Language Coding!</span></p><p><span>Hey, it’s Dan 👋 I’m writing a practical guide about Natural Language Coding and AI in software engineering. Do you have any ideas? </span><a target=\"_blank\" href=\"https://twitter.com/leshemco\">Let’s chat.</a><span> </span></p></div></article></div>",
  "author": "Dan Leshem",
  "favicon": "https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f397c69-27e9-45da-8993-383356aad808%2Ffavicon-48x48.png",
  "source": "aifordevs.substack.com",
  "published": "2024-05-03t12:04:16+00:00",
  "ttr": 206,
  "type": "article"
}