_mu

A big issue to solve is battery life. Right now there's already a lot that goes on at night while the user sleeps with their phone plugged in. This helps to preserve battery life because you can run intensive tasks while hooked up to a power source.

If apps are doing a lot of AI stuff in the course of regular interaction, that could drain the battery fairly quickly.

Amazingly, I think the memory footprint of the phones will also need to get quite a bit larger to really support the big uses cases and workflows. (I do feel somewhat crazy that it is already possible to purchase an iPhone with 1TB of storage and 8GB of RAM).

This is the danger - I get why you think it's true, but it's not true. I've mentored many many bootcamp grads. The biggest danger with y'all is you don't know what you don't know.

Even if you are a really good bootcamp grad and you have good taste and ability, you do not have experience. Software experience is measured really in years and decades, not months.

I like this phrasing because that really feels like how the employer looks at it ultimately.

"Why, it's as irresponsible as calling in sick!"

Geeks are as emotional and irrational as everybody else. They are even worse in fact because they can rationalize their behavior even harder.

But this is plainly ridiculous. The Bay Area has been full of high achievers the entire time I've lived here (since the 20th century). All the startups I worked at, people would work Saturdays. Not all the time, of course, but it was quite common.

Agree - for me this leads to the conclusion that some services should not be run for-profit, or at least they should be run for public benefit. Similar to how governments in some countries own part of the railway.