The article discusses the author's experience building two web applications, one being a party game and the other a SaaS platform for user feedback. Preferring simplicity, the author highlights a backend-focused approach to avoid extensive JavaScript coding challenges, like maintaining state. Using TailwindCSS for styling, the author acknowledges its downsides while valuing its organizational benefits. Ultimately, the approach may not suit everyone, but it aligns with their programming preferences and project goals.
one of the issues I found in my side projects was that I would always lose motivation when I had to write frontend code... they would quickly become a mess.
If we drive everything from the backend we can maintain most of our state there, which works pretty well for a simple CRUD app.
I have stuck with TailwindCSS for a number of years... it leads to bloated class and makes the HTML look more complicated...
I want to keep things as simple as possible... this stack might not make sense for you.
Collection
[
|
...
]