Recent submissions

Comment · 9 months ago
> Naturally, I blamed React.

Did the author start a client-side debugging process without running any kind of diagnostics in the dev tools?

To me this sounds like "I saw some slowness in my application, so naturally I started adjusting indexes in my database." Without doing any upfront research, you're basically just throwing darts and hoping one sticks. This type of approach to debugging has never served me well.

Comment · 1 year ago
> given choice between complexity or one on one against t-rex, grug take t-rex: at least grug see t-rex

I think about this line at least once a week

Comment · 1 year ago
I can only speak to my own experience of doing this professionally in northern climes without power tools for ~5 years, but both of your suggestions are foreign to me. I take this as a nice reminder that there is lots of regional variation to this craft around the world, which isn't surprising.

Even then, building a barn with dried pine or hemlock is much more tedious and incurs many more trips to the sharpening wheel. It is in no way easier.

Comment · 1 year ago
left-pad even being a package is pretty funny, no? How many bytes got pumped across CDNs, proxies, build pipelines, etc. just to write a tiny utility function? I'm all for taking advantage of existing solutions, but I can't wrap my head around needing to pad a string and thinking "oh, I bet there's a package for that"
Comment · 1 year ago
Comment · 1 year ago
What's particularly wild about the choice to tax software development in this way is that it assumes that code is always asset. For companies that are pre product market fit, it's often a liability!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton