AI assistants use rich developer tools like we do.To do this well, a few key pieces need to be in place: Can you imagine giving a big task to a developer, who writes the code but never runs or tests it before submitting a PR? *shudders* This works surprisingly well! If we extrapolate this to a year from now, the time cost of iterating over large changes (across files, packages and entire codebases) drops exponentially-and what a wonderful world that would be!īut this is where the developer experience is going to be extremely crucial. Write a prompt, get some code, don’t like the result? Delete it all, update the prompt and try again. And of course, all their other workflows still remain the same.Ī remarkable shift in how I write code has been the big drop in the cost of replacing code written by AI. That part is left to developers, who are now tasked with evaluating the correctness of the generated code. They can still write code, but with no way to evaluate any part of their work. While many are just a wrapper around OpenAI’s GPT APIs, the best of them combine it with very clever techniques to give the language models the right context to generate code.īut even with additional context, in their current form, AI assistants generating code are like senior engineers with only a notepad. The most famous is GitHub Copilot, which comes as an IDE extension similar to a ton of others (Tabnine, Codeium, Cody and the 1000+ results on the VSCode Marketplace). Since the transformer paper, the launch of GPT models and most crucially ChatGPT, we've seen a Cambrian explosion of AI-powered developer tooling. JetBrains is famous for its language-first IDEs with rich framework support, whereas VSCode is closer to a general-purpose editor with a huge glut of extensions.īut how does the idea of an IDE change in a world with AI? The dial-up era of AI Each IDE has a different take on how to approach this. Fundamentally, IDEs are designed to help developers with their core workflows: searching, navigating and writing code, using static analysis tools, debugging, refactoring, running tests and dev tools, and probably version control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |