My intention for this one was to remake an earlier version of a calendar demo app but this time applying the
OOP practice of Loose Coupling and Strong Cohesion in a React context.... Re-visiting this project was a happy
coincidence: during an hour-long mock front-end interview I was given the task of creating a scheduling modal.
Since I already had developed this mock scheduling app a couple years ago, I figured that I would just use that
as a base. Please forgive the wonky Bootsrap logos, the free icons are giving me trouble. After the interview I
noticed that my old code, comprised of only 3 dev-made components, was very tightly coupled. Coupling is
typically a concern for Object-Oriented languages like Java or C#. It isn't something that is discused as
much in contexts like React, as the backbone of React.js- props - is inherently a tight coupling archetype.
I was curious to see if I could improve my code to make it scalable, by reducing coupling via Redux.
I actually opted to use redux because I've been hearing abuot redux alternatives like Zustand
and Jotai . I want to see what the hub-bub was about. I felt that the best way to
understand why I keep hearing about these Redux alternatives is to use both Redux and the alternatives!
