Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Has any project tried forcing a planning layer as //TODO all throughout the code before making any changes? small loops like one //TODO at a time? What about limiting changes to a function at a time to remain focused? Or is everyone a slave to however the model was designed and currently they are designed for giant one-shot generations only?

Is it possible that all local models need to be better is more context used to make simpler smaller changes at a time? I haven't seen enough specific comparisons of how local models fail vs the expensive cloud models.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: