Am I missing something? How are people seemingly building complex applications if the models struggle with basic things like keeping up to date with releases? What are your experiences?
Am I missing something? How are people seemingly building complex applications if the models struggle with basic things like keeping up to date with releases? What are your experiences?
That being said, the speed at which I can explore solutions with it is greatly improved. This has a big effect on my motivation to start ideas. In some domains, simply getting more times at bat is the critical path.
I use roocode and auto-approve most tasks and then I do a code review at the end. It saves a ton of time but costs a ton of money too
If it does get fixed, who cares about the variables or mixed patterns? Vibe coding at this stage is expected to give running code, not clean and maintainable one. And it often does, but it's not there for complex applications yet.
codingdave•6mo ago
It also does not keep up to date with releases. That is not a valid expectation, and if you are working with leading-edge releases and libraries, LLMs will not help. On the same note, it cannot innovate - it will give you code that fits common conventions. Most of the time this works, but if you are doing truly novel work, its results will frustrate you more often than not.
PaulHoule•6mo ago
It loves to use deprecated APIs, for instance there are a lot of props that you aren't supposed to use anymore and you're supposed to use the "slots" prop instead. It's not hard to change the code and you could probably ask them to do it, but it's the kind of problem I run into.
With SQLAlchemy I find assistants cannot make up their mind what version of SQLAlchemy they are generating code for. Between talking to my assistants and reading the manual I understand a lot about what changed in different versions, but what I really want is to have it look at my POM/packages.json/pyproject.toml and always give me advice for the versions I am using.
This isn't just an LLM problem, one of the "product ideas I don't have time to work on" in my file is a search engine for programmers that indexes the documentation for the actual versions of all your dependencies, so you are not stuck with Google's brain damaged behavior of returning results from random JDK versions. For instance, "String Javadoc" returns results for JDK 8 and JDK 11 (end of life!),
https://www.google.com/search?client=firefox-b-1-e&channel=e...
whereas a lot of us are developing to JDK 21.