Hacker News Reader

Comment by chrisco255 | Hacker News Reader

So you see a thriving ecosystem of millions of developers and you choose to nit about some quirky library? I definitely assume the worst of elitist statements like that.

View on HN

The question I'd ask is whether they're up front about it. It's one thing to ask and see whether someone knows how to check if a number is odd or even - for that matter, it's one thing to use it as a programming quiz! Probably better than Fizzbuzz, everybody knows that one anyway. That's fine.

What would not be fine is to just quietly have that attitude and assume without checking that no one who uses Node a lot has any idea how to do basic things without relying on a library. It's not terribly uncommon for people to think that at least here on HN, I suppose, although I have yet to run into it in an interview or an engineering culture. But if your engineering culture is host to such attitudes, it's best for all involved to be open about that. You'll avoid wasting both candidates' time and your own.

It's particularly absurd. I work on a product that has tens of millions of users built on Node with a team of dozens of talented developers. The aforementioned library checks both the number version and the string version of a number, to indicate it's "even" or "odd". That Node.js makes it easy and cheap to package up small utility libraries like this is a feature, not a bug, and quite in line with Unix-philosophy. Very easy to troll through a list of millions of packages on a marketplace that's as big and broadly used as NPM, which covers not only backend dev, but also front-end dev since the front-end ecosystem is largely powered by NPM these days. So it's a particularly ignorant hot take.

> both the number version and the string version of a number, to indicate it's "even" or "odd"

You're saying that like it's some kind of defense of the library. In the real world it isn't.

Eh. Evenness is a property only of integers, so if someone's going to pull in a library to check it, I could argue it makes sense for that library to enforce that the comparison only be attempted over values where it's defined.

Granted that this seems a lot of effort to put into analyzing the contents of a Github repo tagged "troll-bait", from the user "i-voted-for-trump". But hey, this is HN, so it's whatever I guess.

Have we forgotten the left-pad fiasco already? These kind of things just keep happening in npm-land.

Yeah we forgot it years ago because it was only an issue for a few hours and then lock files were introduced into NPM along with a CLI warning system for vulnerabilities.

Lockfiles don't fix a fundamentally broken dev ecosystem. Users of left-pad fell into one of two categories: people who don't understand the most basic programming tasks, and people who do understand these tasks but are so apprehensive about their own ability that they pull in random libs without even glancing at the source (a single glance would have informed them that they didn't need it). These are both signs of inexperienced programmers.

Amateurishness is normal to some extent, but JS has the ecosystem where beginner mistakes are often seen as the right way to do things.

Reply on news.ycombinator.com