Wasnt suggesting it was a chatbot, just pointing out that it hasnt really changed, its just getting trained even faster and being given even larger data sets.
No, the approach for coding tools has changed quite a lot - they don't work the same way that the chatbots do anymore. Individual steps do, but there's a much larger shift in terms of orchestration and mixed-in non-llm tools, as well as changing ways that context inputs work to avoid the existing limits on model contexts.
For example, they used to be terrible at doing something like 'apply this change to all files in the project', because there were too many files with too much context for that to be possible for an LLM, so they'd just get part way through and then give up. What it will do now instead is break it down into steps like :
Check how many files there are
Do regex search for those files to find which ones need update
Create a temp file with the list of files that need to be worked on
For each of the files from the temp file, spawn off an LLM instance to actually do that change
Inspect the files for code/style errors
Run the unit tests, if there are any errors, work through them one at a time
That's even for basic changes - there's been an explosion in the adoption of MCP servers - every cloud provider and their dog is all-in on that. For some concrete examples on what that means - one of popular tools for designers is Figma - they'd make basically a pretty picture of what a mobile or web app is supposed to look like - with the MCP server for Figma integrated, tools like github copilot and claude can ask for the picture to be provided in a way they understand, and then produce an actual functional UI out of it that is identical to the design, and can be dynamically updated to meet new designs without user input.
These are all productivity enhancement tools for developers though - where the future is starting to look grim for junior devs is in the 'agent' space, where the paperwork and administration is bundled in with the actual coding. As a real life example, I recently ran across a problem ticket that was raised with a blurry screenshot of an error message and no other information. I raised an issue in the github repository for that application, pasted in the screenshot, and then assigned the issue to copilot. The result was, about 5 minutes later, a pull request from copilot with complete patch notes. If that ticket had gone to an actual human I'd give it a 95% chance that they just assigned it back to the call centre saying something like 'at least provide some details like when it happened or what the customer's login was'.
Think of the difference between, say, asking ChatGPT for a recipe for pancakes, and having it attached to some robot arms that can make you pancakes.