Earlier quoted context omitted.
I've dealt with lots of code which could be fixed permanently - ie. put in proper error handling and rearchitect to be robust and maintenance free. More so than ever with the push for MVP and agile ticket stat chasing.
MVP's are supposed to be temporary, that's a weird cherry pick. Regardless, code is contextual and relies on so many things other than its own quality at the time of that assessment being made that to say it's been fixed permanently, as if there's some Platonic ideal code that can be written, is, in my view, something I'd only hear from someone new to the industry or not in the industry at all, like Graeber. The job…
And it looks great at the start, the project is making great progress until people start to leave and the tech debt starts to kick in. By that stage all the "high performance" agile rock stars have pissed off to another company and left behind their legacy.
And then its death by 1000 cuts, things aren't logged correctly, no proper exception handling rather just do a print(e) and falling over, any integrations with 3rd parties aren't documented when they break and its just a mess.