why-oh-why

Hackers. Managed WordPress is great, unmanaged means you're the manager, devops, security expert, etc

I hope you’re being sarcastic.

At heart, Slack is a chat app. Chat apps have existed for 40 years and don’t require a whole lot of data.

The complex part might be displaying the data, but that’s not much different than what an RSS reader does.

Even calling a chat app “complex” sounds absolutely ludicrous. It’s just that devs are now used to shipping 100MB apps in the name of fast development, so Slack is what we get.

It's a fat joke.

If you think StackOverflow needs to be “saved” you’re deathly mistaken.

Just because some complain about it it doesn’t mean that it’s failing.

> The overhead of setting up NPM

What overhead? You don’t run any optimization step on your code? I haven’t seen a single front end project without package.json in years in all the companies I consulted for, and I don’t even deal with fancy frameworks.

The more offensive the better. This is bad and they should feel bad.

It is because if a file is made of a hundred 1-line functions that’s not good code. The separation of concerns is likely not meaningful and it’s detrimental to the reading/understanding of the file.

Why create a function that shortens/clarifies nothing and is used once? If you want to explain some code, use a comment, don’t make spaghetti

> Your CI system isn't going to re-run your tests when your dependencies or sub-dependencies get updates.

Yes and no. Your CI system runs when you want it to. If you want to check the latest dependencies,

- with a lockfile you have to delete it, create a new one and commit it;

- without a lock you just press the “rerun tests” on your CI

What’s the point of reproducibility in your team but not with your users (which is by definition the most common use case)?

Libraries should skip lockfiles because they are ignored by the end user and therefore any testing you do based on them helps no one.

I’ve had lockfiles being broken for no reason* so if you can avoid them, do.

* For example, multiple versions of the same package were installed after several install/updates, but nuking the lock would avoid this issue and solve the problems it caused.

Some bad code is hard to lint automatically (e.g. if there’s a single function that all it does is arg.slice(1), no linter will catch that).

I’ve found all kind of bugs just refactoring code because poor code obfuscates them.

Your way of building things will lead to debt and bug reports

If your code has 20 if else in a row I don’t care if it’s performant and has no bugs, you’ll get a change request because I don’t want to maintain that pile of garbage.

There are minor code style preferences and others that affect maintainability. Just because it works now it doesn’t mean the code is done.

You’re right in having no trust in them. Recently I complained about my price increasing by a couple % once I signed up. Nobody could tell me what the problem was. It took them several messages to finally spill up that they were charging me more due to my country’s taxes.

Why is this not clear? Airbnb is so opaque. It would be really easy to list this extra tax but they don’t, so I end up creating a new account.

Are you sure it said confidential? As far as I know Airbnb has always had a field for “A private note for the owner”. This is “confidential” between you and the owner, as in “not public”, but not between you and Airbnb.