There was a time when backend engineers used to make fun of frontenders and tell them 'you arent a real software engineer', nowadays frontend is getting so complex and cool that even backenders are now starting to learn frontend. I am so happy that because of new tech and frameworks frontend has gained such a massive respect.

For state management, we use:
React state
Redux state
Local storage
Session storage

That’s it 😊

Recruiter bot just emailed me with some offers, let's take a look...

"Hand-on Experience with SQL and NO-SQL Databases preferably Redux"

Whew! I was worried for a second, thank god they are using a Redux database and not one of those really crappy React databases! I'll really consider applying now.

smh

If you feel it’s time to change I have a great job offer for you…
proceeds with offer with maximum wage that is half what you earn and by the way you need to know React, TypeScript, NextJS, Redux, NodeJS, ES6, Webpack, RESTful i GraphQL API
Nice to have is Python and Go

Girl you need to decide if it’s great offer or technology mishmash.
Hell no, glad you didn’t mentioned young and dynamic team cause I clearly see some dynamic technology stack there.

Company helps people find medical treatment clearly forgot about treatment on their stack.

Someone needs to tell them their tech leads are complete morons but since you’re not looking for head of technology it won’t be me lol.

Should I feel bad if I can’t set up redux configurations out of my head?

Redux is absolute fucking insanity. There is no way in hell there isn't a better way to do this. Absolutely unintelligible, convoluted piece of garbage.

The most annoying question, that has been asked many times through centuries.. here it goes again:

What Editor would you choose for Web, React.js, React Native and Flutter on Mac:

Atom || VSCode

Redux vs useContext. Go ahead …

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

Gggrrrr!!! React native and redux!!
God damn error city. Feck! 😫
But yet I love it.
Anyway, happy new year from Ireland!