← Back to context

Comment by steveBK123

9 hours ago

> Being handed a baked and glazed artefact that approximates what you thought you wanted to make

Isn't this also an overstatement, and the problem is worse. That is - the code being handed back is a great prototype, needs polishing/finishing, and is ignorant of obvious implicit edge cases unless you explicitly innumerate all of them in your prompts??

For me, the state of things reminds me of a bad job I had years ago.

Worked with a well-regarded long tenured but truculent senior engineer who was immune to feedback due to his seniority. He committed code that either didn't run, didn't past tests, or implemented only the most obvious happy path robotically literal interpretation of requirements.

He was however, very very fast... underbidding teammates on time estimates by 10x.

He would hand back the broken prototype and we'd then spend the 10x time making his code actually something you can run in production.

Management kept pushing this because he had a great reputation, promised great things, and every once in a while did actually deliver stuff fast. It took years for management to come around to the fact that this was not working.