Hacker News new | ask | show | jobs
by eudamoniac 25 days ago
The code I write is pretty good, and it stays good throughout the years because it was already good. If you're frequently finding month old code to be shit, your code is just shit to begin with.
1 comments

Or .. you are working in an unstable environment. If the system you take as a base changes frequently(like the web), your code becomes bad, outdated code, no matter how shiny it was before. But if it was good, migration and maintaining it is easier.
React is 13 years old
So?

Are you implying I should have switched to react 13 years ago, when it was just another framework who come and go?

And then my experience would have been stable?

(I kind of doubt it, when my unstable web experience was caused by changes into how canvas works, webrtc, indexeddb, webgl, webgpu. I don't make simple UI's)

Or well, just that "let" was introduced makes all my beautiful old code with only "var" bad code by modern standards.

"let" is 11 years old.

My point is that the web is not really an unstable platform anymore, it's just something people say that used to be true. Also using var and other superceded constructions doesn't make the code bad; that's not what bad code is. I think you know this.

I think I know that different people have different metrics what bad code is.

My main metric is, if it is readable. So yes, I also don't consider my old code with var bad. But other people do.