I wanted to add something in response to this bit - I have, for most of my dev career, tended to avoid doing big projects when I'm playing around on the side. I have, for example, completed one year of Advent of Code, done quite a few puzzles from other years, and done lots of little one-off things like that.
The current project has been interesting because it's forcing me to take a bigger picture view and grapple with the difficulties of integrating lots of different modules together into something cohesive. As I get closer to releasing something, I'll also have to figure out some things I've never done before - how to accept payments, set up an LLC, and so on and so forth.
I've been repeatedly telling myself that even if I never have a single paying user (well, besides myself), that the knowledge I gain by going from an empty text file to an actual "business entity" capable of accepting a payment for a service will be worth a lot as I continue my career. Truly "full stack", you could say.
Whenever I set myself a large project and prepare to undertake something large, my motivation to work on it changes and I start wanting to do other things.
But when I just commit to do a small task of part of something large I feel I can do anything I want. I just need to get the small task done. You can scale a mountain doing a little part at a time.
I think LiveView is a really interesting idea and can be extremely powerful to building responsive applications.
I've always wondered how LiveView scales when you add a load balancer to the mix and what you need to do to cause it to work at scale.
I'm not much of a frontend (css/html) person either!
I just set myself a task and work until it's done, it's not part of an overreaching project but sometimes they do join up together and I merge the work together.