Live data from Hacker News

Nobody cares about your clean code

felipecsl.com

151–160 of 177 posts

Re: Nobody cares about your clean code

#151
post #142
post #43

Earlier quoted context omitted.

Oh boy... I believe I'm this kind of psycho, when I see my name in a git blame after tracing a bug that I didn't foresee... I feel awful, disgusted, then I fix it and think "You sure are dumbass, now try to be a lesser one".

this is always fun with git-bisect because if you can reliably reproduce the bug it will always leads you exactly to the commit that caused the problem. Nothing worse than tracing for a half hour and... it spits out your name.

Holy Molly, learned about git bisect, ty paulmd. HN comments amazes me, I always learn a thing or two.

Re: Nobody cares about your clean code

#152
post #89
post #43

Earlier quoted context omitted.

Oh boy... I believe I'm this kind of psycho, when I see my name in a git blame after tracing a bug that I didn't foresee... I feel awful, disgusted, then I fix it and think "You sure are dumbass, now try to be a lesser one".

And the relief when you see your name is nowhere near the defect.

Yes!

Re: Nobody cares about your clean code

#154
post #111

Meta observation: OP says nothing new, but I guess that people have to (re)discover this sort of principles by themselves, no matter how many times they're told by the wise and old. We often say that we hate reinventing the wheel. But life is actually full of reinventing-the-wheel experiences. Maybe that's the point of a life.

Do we say we hate reinventing the wheel? I think the reason it’s even an axiom, “don’t reinvent the wheel,” is because it is so very tempting to reinvent the wheel rather than building on established wisdom.

Re: Nobody cares about your clean code

#156
post #137
post #116

Earlier quoted context omitted.

Yes, but this often occurs a few months or years into production, way too late to throw it away. I've never written a prototype, nor seen one written, in actual businesses. I've never had an employer with the patience to let me play with a prototype either.

If it happens years into production, especially after the load has increased or requirements have changed, it is a legitimate version 2 :)

> it is a legitimate version 2

Maybe, but then the previous one was version 1, not a prototype. I've never seen people actually write prototypes, nor management accept time invested on writing prototypes, in any job I've had.

Prototypes always directly become version 1 on production, unless of course the whole project gets canceled mid-development.

Re: Nobody cares about your clean code

#157
post #11

Weird post. The main insight is easily captured by the phrase "technical debt is a resource, not a vice". It also disregards that developers who care about clean code do exist, such that the title becomes merely metaphorical, and is more accurately rendered as "users don't care about clean code". Except that they do, they just don't know it. Time to new features and time to bug fixes (both of which users do care abou…

Technical debt not only makes it harder to add features, it makes it harder to remove technical debt and make technical improvements. Choosing not to pay down technical debt is fine, but at some point it will be such a mess you won't be able add features or fix the technical debt issues without a total rewrite scale project.

Re: Nobody cares about your clean code

#158

The fatal flaw of this article is assuming that having a single PHP file implies ugly code, or at least uglier than the average codebase. I would, in fact, guess that its code is much cleaner than the average Fullstack Javascript app. If you're capable of writing a full, functional website in one PHP file, you know what every line of code does, you have only what you need and the ways to factor your code become more…

I've spent some time trying to pick up modern JS tooling. I used to code JS back in the early days of JS and stopped around the time Backbone JS stopped being used

The learning curve right now in JS is ridiculous. Onboarding developers is hard. We wrote a new project in ember js and threw it away for react.

Sometimes new tools, like Ruby on Rails, make it way easier to get started. Not so with JS. But I'm sure you get a lot of dynamic rendering power to make up for it

Re: Nobody cares about your clean code

#159

"Users couldn't care less about the programming language you used", and yet the author is so protective of his work that I can't copy paste this phrase. Unhappy user right here. We code for ourselves. We deliver value to the costumer. Two different things.

The inability to copy/paste was actually an oversight on my part, will fix. Thanks for pointing it out, not even sure why that's the case right now :)
Post reply on HN