I'm a newish dad and full stack dev. I've found that what's been most effective for me, aside from spending (admittedly, far too much) time coding in the evenings before sleep, is making a concerted effort to share whole-day responsibility of the kids on weekends. I'll take the kids on one day, my wife will take the kids on another day. We trade off during the week too so we can both have large stretches of uninterrupted time.
Exercise (and for me, meditation) are important balancers too - don't neglect them for the sake of coding, you'll find that you just get burnt out.
Although I don't usually get full-days this has become really helpful for me. 4 or 6 hours of time to do something is incredibly productive for me now.
Isn't what you're describing essentially the ActiveRecord pattern? An object that has the internal capabilities to perform the various CRUD operations direct to a persistence store and only operates on itself?
EDIT: Also, from an architectural standpoint, do you not think that having SQL-speaking objects written in this fashion is too tightly coupled? What do you think of a "Clean Architecture" implementation with respect to your idea?
People (in my experience, anyways) would prefer a product that is fast and gets the job done without fault or error over a product that looks really awesome but performs poorly and is buggy.
In other words you can put as much makeup on the pig as you like, but in the end it's still a pig.
Try telling that to one of my former bosses though ;)
I hear ya... from what I can see it looks like it would be great for rapid prototyping, even big systems... however why anyone would go with a JS-backed framework for a serious application is beyond me - it's just not ready as a language (and a framework)
Exercise (and for me, meditation) are important balancers too - don't neglect them for the sake of coding, you'll find that you just get burnt out.