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.
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.
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
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.
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.
“Left behind” i.e. this API will work for USA only. Don’t be silly. The point of browser APIs is that they work for all/most, if it’s only Apple Pay and Google Pay they solve nothing.
Here's the thing: you can't have 1000 "discoverable" actions, there's no place for it.
Correction: you do have 1000 discoverable actions, but you discover them in the menu bar.
What you found out with this article is that users are bad at knowing things, because there are too many things to know. I know all of those actions and their keyboard shortcuts, but I still have to occasionally "google it."
Either you have iOS 1.0 where everything is clear and easy to do — because there's very little to do — or macOS, where each app has dozens of features but can only surface some of them.
I don’t think you can do 80kph in US cities either. Extra-urban EU roads allow 70 or 90 as well unless really curvy or with plenty of entrances, but in cities it’s 50 or less. I always thought that matched the US.
The difference I’d say is that 45kph get you much “farther” in EU cities than the average US city.