A short talk arguing against relying on AI models (e.g., ChatGPT) for coding because software and libraries evolve rapidly; the speaker emphasizes the fast-changing nature of programming tools and questions how quickly AI models are updated to reflect library changes. The piece highlights occupational obsolescence and the need for developers to stay current.
In terms of the coding, there are a few reasons why it's probably not a good idea to use these type of models for that. Because our industry is very dynamic. Things change on a daily basis. Just because something works now, it doesn't mean that it's going to work tomorrow or in a few days. You know, Python has new versions almost every couple of weeks. It's something that keeps changing, so you need to be on top of things. And it's, you know, an occupational hazard. You can say that you learn something in university and by the time you're done, nobody's using it anymore. So that's number one. If you're using a model like ChatGPT, how often is it being updated? Like, if there's an update happening in one of the libraries, how long before ChatGPT is aware of it?
AI News: Dots, GPT-6.1 Sol, Sonnet 5.5, Gemini 4, and everything you need to know
