I know, you're already so excited.
Immutability and state are two developer buzzwords it took me forever to "get."
Their underlying meanings aren't necessarily that complex.
But it's tough to fully comprehend what they mean, and why they're important, until you see them in action.
State just means the way an application is at a single point in time.
For example, if we've typed "how does CSS grid work" into the search bar, and there are three checkboxes ticked, and we have a dropdown menu open that's the current "state" of things.
If we close the menu that's a state change.
It's the same as copying and pasting a new ImportantThing_Version2_Draft.md document before liberally changing enourmous chunks of it. Then when you realise your poor editing choices and want to go back to the original version, it's there waiting for you.
Okay now you're all caught up on the jargon, lets get to some sketchnotes!
Despite my allegic intolerance towards thinking about state and immutability, this course turned out to be a delight.
Michel walks us through building a gifting app with React & Immer that seamlessly handles all the messy state work.
Visually drawing out how all the functions and drafts and edits fit together was essential for this one. I wouldn't have grokked it otherwise.
Yes the cup in the illustration is based on this classic CSS one that I don't own, but kind of want to.
If you're currently allergic to state & immutability as well, it might be the time to re-test your tolerances and see if Immer can help cure it.