> in exchange for paying this cost, you gain maintainability, developer efficiency, and (hopefully) better performance during runtime.
You also gain responsiveness to user interactions, a programmatic way to reason about your application/website & and some animation-sugar if you want. Don't throw the baby out with the bath water simply because people follow trends instead of good design practices.
The amount of colossal horror stories I've heard about that company has made sure I don't go near it with a 9 foot pole. Their platform is designed to obscure process in lieu of exploiting workers - all whilst advocating to "serve the client". Utterly toxic.
But this is exactly what the article talks about - and what I agree with - let them ask for help. To each his own, I agree that some people need that intervention, but for the rest of us, don't assume it.
Co-workers who have a tendency to "shepherd" newbies are downright annoying. Other than the initial on-boarding, there is no reason to be involved in solving someone's "new comer experience".
This reminded me a lot of how DHH described their thinking (paraphrasing A LOT): other people don't have to have a bad product for yours to be successful. Good article!
The way Redux works is that it essentially stores all the dynamic information of an app in a single JavaScript object.
This is the temptation when starting with Redux/Mobx/GraphQL/etc. You can't simply relegate reasoning through your application architecture to a single library or because some big company solved a problem with it.
Redux is a fantastic way to organise some of your app state & GraphQL is also great at a lot of stuff! Absolute no need to play the all-your-eggs-in-one-basket game.
I don't know why, but some people assume these services are being used as a utility rather than a community. So they make their case based on stats and data, and completely ignore the relational aspect of being part of it.
You can spit facts & figures all day long, but unless you make it clear why your own community is intentionally betraying you, it's all noise.
That is sad! My condolences. That was a very well written letter from Slack and I completely agree with them, but unfortunate for BetterSlack nonetheless. Always room to pivot!
As a non-user of Facebook, I completely take their side with all of this.
1) If people don't want to read the fine print, whose fault is that? 2) How have we gotten to a point where we are abdicating our choice voluntary, and then acting begrudgingly toward the new owners when they misuse it?
I must apologize for my cynicism here, but we've been going around this mountain for a very long time now (circa 2013 IINM?). I'm getting tired of hearing how people are feeling violated due to their own actions.
Mr. Robot was stupid because - why do I want marketing in a product I use as an eveyday utility? Chrome is the standard because of the majority market share and also because they do a great job of delivering a good developer AND user experience.