> It mostly boils down to this: delight customers and iterate as fast as you can.
This is maybe the second phase after AWS found a fit and built a consumer base? Once I am in the housing market, I have a need for everything (mortgage, building contractor, construction materials, designer, hardware and accessories, upholstery, decor, etc).
My entry to AWS started with EC2 in the very early days because it of its commodity nature (any size and shape, for however long, with per-minute billing) and instant availability. The elastic nature solved scale. A lot of people didn't move to RDS until later but it was inevitable.
Everything else followed on from there, cross-sells and up-sells for reliability and convenience were always a click away for captive consumers who were already onboarded.
The only thing that didn't sit well with a lot of people about the leaked memo is that it ignored the quality of GPT4 vs GPT3 and made claims that all LLMs were poised to be on par, yet that isn't true till now.
What it also ignored (along with some of the comments here) is data ranking. Google didn't just build a search engine by crawling more of the web -- many search engines before it had already done that. Google managed to rank what's relevant and what isn't. Relevancy is hard. Similarly, not all scientific publications are ranked equally. Or for that matter, even publications with a lot of peer reviews or citations can become obsolete through new discoveries.
Reddit's data has value in that it can fill in a lot of the gaps left by more qualitative sources and furthermore the data is user-ranked by a trusted community. This also has implications for specialised querying, for example training on just r/fitness could be fairly useful for that community.
As a side note, other valuable data stores are not just text but voice/video as well. YouTube and podcast transcripts are readily available, for example to Google. Data and ranking is valuable all over again.
Most likely, just as happened with Stable Diffusion, a community of models will emerge. You could use a pre-trained model for writing chrome extensions, or a model for writing material UI using tailwindCSS, or a very specific model for writing 2d games for Android.
Since a lot of this is trial-error, improving on each iteration the feedback loop (compile, deploy, run, etc) will matter a lot more. Real-time development workflows like React should be interesting at the least. Exciting stuff, truly.
They need to take this and similar AI and come up with better dubbing for movies in other languages. Netflix should really lead the way here with the amount of dubbed content that they currently possess.
Psychotherapy must be up his alley, he seems to have come to terms with it quite well and taken it with a sense of humor.
An initial run of 4 million copies is a lot of pressure on a single developer, the sort that can make you a legend or a catastrophe. I wonder if release management was considered to allow for bug fixes in subsequent production runs or phased production runs with hedged risk.
Probably adding to the pressure is the frustration that immediately following the production run you find a one-liner bug fix but you are 4 million copies too late.
Interestingly, Pac-Man also had millions of unsold cartridges left over. This candid Q&A talks more about the failure of ET, the frustrations and challenges:
This is maybe the second phase after AWS found a fit and built a consumer base? Once I am in the housing market, I have a need for everything (mortgage, building contractor, construction materials, designer, hardware and accessories, upholstery, decor, etc).
My entry to AWS started with EC2 in the very early days because it of its commodity nature (any size and shape, for however long, with per-minute billing) and instant availability. The elastic nature solved scale. A lot of people didn't move to RDS until later but it was inevitable.
Everything else followed on from there, cross-sells and up-sells for reliability and convenience were always a click away for captive consumers who were already onboarded.