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

> I don't consider this my project, and I have no sense of acomplishment or growth.

Trigger warning incoming... if you are in a for-profit company, does the business really care whether you feel accomplished as long as you are producing code? As an analog - the assembly line worker on a highly automated Tesla assembly line is essentially a replaceable commodity at this point.

> The main issue is taste, when I write code I feel if its good or bad, as I am writing it, I know if its wrong, but using claude code I get desensitized very quickly and I just can't tell, it "reads" OK, but I don't know how it feels. In this case it happened when the code grew about 4x, from 1k to 4k lines. And worse of all, my mental model of the code is completely gone, and with it my ownership.

Does the code work? If so, why does any of this matter?

In an age of automated manufacturing, I've noticed more and more independent wood workers. This is okay - but you aren't going to supply the world's furniture needs with thousands or hundreds of thousands of artisan wood workers.



But a chair cannot be copied from one home to another. Code uniquely can be. Good (perhaps artisanal) code is useful and better for everyone. The foundational improvements by a single person can get magnified throughout a project, while with other crafts the quality of their output does not have the same effect.


> Good (perhaps artisanal) code is useful and better for everyone.

How so? We actually don't have any specific characteristics on what makes code "good", nor do we have any quantifiable metrics that say "said good code is better"?

I may think your chair is more comfortable or that it lasts longer under load, but that doesn't always mean is "better". A cheaper chair could be considered better because its cheaper to acquire, even if its not as comfortable or doesn't last as long.


> But a chair cannot be copied from one home to another.

Some 3D printing enthusiast: "Hold my beer ..." :-)


I really feel the same about LLM generated code: LLM does not know what is good, it does not have `taste`. When I explain what's wrong with LLM I use the same word `taste` and it is kind of amusing that someone has the same feeling.

So why this matter if code works? If you will not look at it anymore then no problem at all, but that's definition of dead code that does not need support and will not be used anymore. I have projects that I do not support for years, but I can return to them anytime and work on them, because they age well like wine.




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

Search: