There wont be as many. The previous automation waves since the late 1800s have optimized or automated away a lot of tasks humans used to do, while what human beings do and need have not increased at the same pace. Today, we arent using flying cars or cyberpunk technologies that require a whole industry chain in which millions of people can participate, like how it was depicted in sci fi movies for example. Whatever scarce new thing that came to being, was consolidated in the hands of megacorps and automated to max extent to reduce workforce. Since the 1970s we automated away almost all the workforce in factories - what used to require ~2000-3000 people in a factory to produce now requires ~100 people using extremely efficient automated systems. Only white collar work remained, and now the AI is automating away the white collars too, who were the last remaining holdout that helped infuse the economy with cash through their salaries.
Blackrock CEO's surprising speech at Davos is spot on and what Marx said 150 years ago. It just happened, in front of our eyes, in our lifetime: Capitalism literally choked itself by automating production, firing workers and ending up with an economy that has products, but no one with the money to buy them.
I have been very hesitant to have kids for a long time for many reasons. My wife have been wanting to have kids, so have felt quite conflicted.
Then this year I read the book after the spike which put a lot of this in perspective which made the thought of having kids less daunting somehow.
https://www.barnesandnoble.com/w/after-the-spike-dean-spears...
I wish both of you well in how you navigate the path forwards.
1. Each kid gets their own email 2. Each kid gets a password manager 3. The emails are managed by the parents, sometimes as a child account (Gmail) 4. Use a VCC service to generate a VCC for each child with a spending limit/require approval for all transactions. Keep it in the password manager so they can easily use it anywhere
Once the emails are managed, setting up parental controls on the devices themself should be easy.
On another note, keep the barrier low. Let them figure out a way to get past it. This is what they actually want to learn about, and by doing this it kinda "forces" them. This is how most kids that I've taught got into tech.
A lot of how I form my thoughts is driven by writing code, and seeing it on screen, running into its limitations.
Maybe it's the kind of work I'm doing, or maybe I just suck, but the code to me is a forcing mechanism into ironing out the details, and I don't get that when I'm writing a specification.