It’s not about freedoms. Your self-censorship is wasting everyone’s time, because we need to decipher what you meant.

This was not supposed to be a fucking riddle.

Your self-censorship actually makes your already bad meme even worse because it’s incomprehensible.

But sure, it’s your right.

Which advertiser are you talking about? 😵‍💫

She’s a doctor FFS. We don’t want those crazy fucks to be practicing medicine.

This is a notoriously bad book. If you read the part about comments (which I don’t know about, and am willing to accept is good) make sure to skip everything else because Robert Martin is a fraud.

deleted by creator

deleted by creator

Even though I like intermediate variables myself, I’ve been told the same thing when co-authoring code.

What these anecdotes suggest is that this is subjective, and I think it can be overdone. I don’t think objective general rules can be established from the article, even though I think it’s good advice.

In my examples, I was overdoing it and causing too many indirections, creating leaky abstractions (leaky because, in my context, the abstraction was not tightly self-contained and understanding the “implementation” of the abstraction was necessary to understand what the line of code that was using it was doing).

I don’t think it’s a black-and-white matter. Your reviewer might not necessarily have been a moron, or might have lacked the self-awareness to realize they were imposing their own preferences onto you. But there’s a slight chance that you legitimately confused them with your indirections. Hard to say without context.

It’s the first time I see it, but that doesn’t mean it’s uncommon! 🙂

I had to look up what IINM means. For anyone wondering, it means “If I’m Not Wrong”.

Not sure this is worthy of an acronym, but that’s your choice! I just wanted to contribute context for people like me.

Thank you!

Do you have any example in mind? I’m very interested!

I do use neovim myself too 😁

Please don’t hack me, mister FBI

I assume this was a joke 😁

On top of helping reduce power bills, maybe, and thus reducing the government’s carbon footprint.

I’m not sure if the numbers add up, but that’s definitely a factor worth considering.

That last point truly bothers me, too. It’s fine to have a bloated work environment (some people use Visual Studio, after all). But that complexity should not get offloaded to your users. Webdevs need to do better on this front, it’s not 2015 anymore.

NPM is definitely saner for that use case because it works out of the box. Pip is not because it is based on shakier foundations. With NPM, you don’t get to a point where you rely on things to work correctly, and they suddenly don’t and you have trouble understanding why. And it does not force me to look at its nuts and bolts to allow me to work with it.

I can afford big node_modules directories, even if it’s not optimal. It’s still small compared to the cruft I’ve accumulated on other projects I’ve worked on with other technologies. Remember the order of priority of things: make it work >> make it efficient. Software engineering is about delivering software, it’s not an art. It doesn’t have to be pretty everywhere.

I will concede that NPM is not perfect. Despite its flaws, I love how Conan solves the issue we’re talking about.

Is that still a valid argument in 2024? The standard library has grown since the leftpad scandal. JS does have standard leftpad now.

It’s a genuine question, I no longer write Javascript for a living.

Pip is definitely not saner. The way installs are centralized has bitten me in the ass multiple times, when I wanted to have two different versions of Conan installed on a single machine.

And I know there are workarounds like virtualenvs, but they’re complex hacks. Stockholm syndrome yadda yadda yadda.

If it was sane, downloads would be centralized (no point in downloading the same package over and over again) but installs would be project-local (symlinks? There are multiple ways to do this, cf Conan)

Sure, NPM is wasteful with storage space but I’ll take inefficient over brittle any day.