- The Great Googly Moogly in the Cloud (Google)
- More hours in each a day.
Edit: explaining why…
Firebase might seem like an odd choice for someone who uses MSSQL in his day job and has 22 years experience with it (omg has it really been that long?! Since v6.0 in 1995, so yeah).
But, that is precisely why!
First, using a fresh database paradigm (and fresh tech stack, bottom to top) for a real app with real, paying customers forces deep, focused learning. Looking at the same problems from a different perspective, and solving those problems with a different toolbelt gives renewed insight into how I look at problems in the old sphere of knowledge.
Second, a current employer can never rightly lay claim to my work, as the entire stack is entirely novel from what I work with at the 9-5.
Third, sysops. In my stack, starting with Firebase, sysops are someone else’s concern. Yes, this does come at a price. I build and maintain SaaS apps and eCom sites for a living at the day job, so I know how much care and feeding can be required just to keep the server racks happy and humming along. As a solo founder, I need to delegate as much as possible to leave time to concentrate on more important things like product, customer support, and marketing. Someday, if I can ever burn the boats and concentrate full time on this app, maybe I reconsider this stance, but for now, let someone else cut the lawn, let someone else keep the database running fast. And for all its many shortcomings, Firebase is verifiably and consistently fast.