I think on-device AI will show up more front and center but in a few more years.
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).
> But I’ve seen enough repos that I know what good practices look like.
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.
Nowadays people throw the term "refactoring" around quite loosely, usually meaning "rewrite" when that was not at all the original meaning of the term!
A little bit like how "vibe coding" quickly went from one definition to another even though people should have known better.
This article is attempting to make some kind of statement about 996 and "look, now it's here!"
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.
> I think this is just a natural consequence of structuring everything around engagement.
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.
What is really missing is good sex education in schools, especially public schools - and in particular in the United States. The state of sex education in America actually deserves the work deplorable, it's so bad.
Looking at this comment thread, I get the sense that people are coming from vastly different backgrounds and upbringings. There's no baseline established for what people are trying to discuss.
There are a lot of topics that should simply be explained to children up front from a very early age. When a topic is not shrouded in mystery, it becomes boring. So kids should learn from an early age what is sex, puberty, menstruation, homosexuality, etc. and it should be presented in a manner-of-fact way that takes the emotional charge out of the picture. When people are educated, they have more latitude to make good decisions.
It's not that Claude can't but iOS / Apple development is such a bear and beast. You could really build a whole model just to solve for that ecosystem. There are huge issues in the Apple ecosystem with documentation and so much tribal knowledge. In many cases it's hard to know what is the right thing to do, and there is keeping up with all of Apple's required changes.
So Claude could do it, it just seems like they're focusing on a different set of developers for the moment.
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).