Every time you find a runtime bug, ask the LLM if a static lint rule could be turned on to prevent it, or have it write a custom rule for you. Very few of us have time to deep dive into esoteric custom rule configuration, but now it's easy. Bonus: the error message for the custom rule can be very specific about how to fix the error. Including pointing to documentation that explains entire architectural principles, concurrency rules, etc. Stuff that is very tailored to your codebase and are far more precise than a generic compiler/lint error.
Needless to say, spending and income are two different things. This is very easy to see if, for example, one spouse loses their job and the other continues to do exactly the same housework and child rearing -- but now can spend much less.
I probably should have said "all economic systems since the dawn of time" but I took a shortcut that covers most of the modern world's economy instead. I certainly didn't say that communism was somehow different or better in this regard.
Consider what happens if one spouse loses a job and is forced to take one with half the pay. The spouse doing the work at home suddenly has to make do with less, even though their work has not really changed.
My point is not really about slavery, it is about how this example shows how much work there is and how difficult it is, and how we don't seem to account for it even in normal life.
"the history of paid work suggests that the unpaid labor of mothers in the family is the critical thing"
Thank you for this much needed shift in perspective. It should be obvious: mothers' work has been on the critical path for humanity, and other work has shifted around to accommodate it. This is such a forehead slapping observation.
My point is that the systems we've built optimize for things we choose to measure. We're very much measuring and optimizing for money and the kinds of goods and services money can be exchanged for. But to a startling degree we're not choosing to measure all the other hard work that has to get done if we expect humanity to exist beyond one generation.
This article just puts it in stark relief for me. All of the work that Lola had to do for so many decades, working herself to exhaustion... all of that work still needs to get done for every other family too.
One thing that struck me is that Lola did so much of the work of a traditional mother's role: raising the kids, cooking, cleaning, laundry, and even providing emotional support. The mother had to take on a traditional father's role in bringing home an income. And the actual father - well, he did neither role and seemed to just freeload, gamble, abuse, and finally disappear.
All of the work in a traditional mother's role, well it's usually uncompensated too. Sure it's a "labor of love" but it's also just a huge amount of work, for decades. An argument could be made that the entire capitalist system is built upon uncompensated labor. Just ask your mom.
Every time you find a runtime bug, ask the LLM if a static lint rule could be turned on to prevent it, or have it write a custom rule for you. Very few of us have time to deep dive into esoteric custom rule configuration, but now it's easy. Bonus: the error message for the custom rule can be very specific about how to fix the error. Including pointing to documentation that explains entire architectural principles, concurrency rules, etc. Stuff that is very tailored to your codebase and are far more precise than a generic compiler/lint error.