Isn't the common sentiment now that Redux is no longer considered a must-have for all greenfield projects?
Also aren't communication apps a perfect use case for Redux due to the need to have events from multiple sources happen in a single store in a linear order?
That's part of what I was getting at, and what I talk about in the first couple links.
Lots of folks have used Redux because they were _told_ they "need" to use it. That's always been overkill. And, yes, there are plenty of other viable alternatives that overlap Redux's capabilities in various ways (Apollo, MobX, React context, etc).
So sure, it's not a "must-have", because you should _always_ evaluate tools and determine what's really appropriate for your use case rather than just blindly using something.
But, at the same time, Redux is still very widely used (~50% of React apps), and not going away. So, there's a big difference between "not an automatic must-have" (which is true) and "dead/dying" (which is not).
What's the definition of a child's long term prosperity? Is it grades or does it take into account emotional/physical well-being? And do those studies go into adulthood?
> This research examined the association between parenting style and life satisfaction in adulthood (N=112). Participants responded to an online survey, called the Parenting Style and Life Satisfaction Survey, which included questions pertaining to parenting style experienced in childhood, parenting style used in adulthood, and levels of life satisfaction. A chi-square test was conducted to determine if there was a relationship between parenting style experienced in childhood and the adult's own parenting style. Analysis of variance tests were conducted to determine how parenting style experienced in childhood was connected to life satisfaction in adulthood and how the adult's parenting style was related to their life satisfaction. Correlations revealed that there were no statistically significant relationships between parenting style and life satisfaction. Results were interpreted and implications were discussed.
Yes, because that is how we determine whether or not someone needs help in the first place. If you have a better alternative, I invite you to elaborate.
This is the biggest counterpoint to the article. I think a bad developer promoted to a position of management wreaks much more havoc than an unhappy good one.
It definitely seems like two extremes right now. Personally I think we should strive for minimalism when working with JS. Things get bloated very quickly when non-technical departments have requests (tracking, A/B testing, ads, etc). These things often cannot be pushed back on.
My feelings are that front end devs should focus on performance by reducing what is in their control -- basically dependencies and overengineered clients
The hard part in my experience is that a lot of teams don't know if they absolutely need it. I have worked on some projects that are more hype driven development using React/Redux/Sagas for a barely interactive webapp. It adds a ton of complexity for little to no benefit.
Can we stop grouping React, Redux and Sagas when discussing complexity/bloat? They all have totally different complexity profiles. For example React adds tons of software complexity but very little development complexity, whereas Redux is the polar opposite. And Saga is just a clusterfuck. I don't even understand how people can use it with a straight face.
Ok, but only if we can also stop saying React and Vue in the same breath. React is the spearhead of a galaxy of the biggest, heaviest, enterprisiest solutions in it's class, and it has it's place, but Vue is at it's best in lighter applications. You can do quite robust SPA development with Vue, but I'd argue it's even better when it's sprinkled lightly into a project, as a drop-in replacement for the ajaxing and updating we used to use jQuery for.
Some people just want a project with particular frameworks on their resume. "Professional side projects" carry more weight than something up on Github.
One of the most talented engineers I ever met was 24. He built a 3D engine in JavaScript for fun as well as a raycaster for fun. He also enjoyed challenging himself in all sorts of interesting ways like doing Advent of Code in C++.
What's weird about doing Advent of Code in C++? You'll find a sizable number of the people on the leaderboard do it that way. I think it's partially due to competition programming habits dying extremely hard.
Of course, Python is by far the most popular, but C++ isn't that much more verbose.
I’ve only met a couple people who say “fire”. That’s a little overwrought. The less dramatic version is “we are too big for heroes” which unpacks into something like this:
You don’t want an organization that relies on one or two or three people to swoop in and save the company every time there’s an emergency. A production issue should look like disaster preparedness. Document, train, drill, prevent.
More concretely, make the important parts as obvious as you can, as similar to production as you can, so anyone can set up a system and try to repro the problem. Config, build, and deploy should be push button (very robust scripts with every cheap sanity and safety check you can manage). No flakiness is okay. Nor obscurity. Everybody should understand how it works.
Document everywhere diagnostic data comes from and goes to. Don’t let your most senior people solve production issues; assign them to people one step down (and throw in some promising mid-level team members for
diversity and longevity). Five why’s every outage and be sure your resolutions always involve making the problem easier to detect next time, not just prevent.
This was posted on HN a few weeks ago? Uses GPT to rank news