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

This is called the bargaining phase.


I am using a model that runs on a 100 GB300s, near AGI, all bets are off, $10B training run on a 1GW cluster, and it can't realize that when I told it to "please implement v2 of feature X" that I mean delete v1, not support v1 and v2 together, in a weird Frankenstein's monster of the two. Sorry, but I think my job is quite secure for the forseeable future.


This is a perpetual pet peeve of mine with LLMs. They will always opt to ensure "backwards compatibility" with a codebase built 30 seconds ago.

I always have to explicitly state, "we are making a clean break to v1.0, do not implement any compatibility layers".


This is hilarious and blindingly obvious in hindsight that an LLM would fall for that




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: