Well, its a couple of short tweets that of a very terse anonymous claim about background and turning point of the conflict (but without any details of the conduct related to the internal tension it reports), and a journalists predictions prediction of Altman landing on his feet.
It doesn't justify anything because it doesn't tell you much of anything about what happened, even if you assume that it is entirely accurate as far as it goes.
If anything you'd probably drastically increase your salary if boomeranging. Inflation has been no joke these last years, and getting a new job usually outperforms a promotion by a large margin.
Not doubting that chart, but it's worth a bit of skepticism.
If people are making more money relative to inflation and the workforce participation rate has been steadily rising, then why is credit card debt at record highs and personal savings at near record lows? That should imply that people are buying tons more stuff than they used to, because if you make more money, don't save the money and you still need more credit where does the money go?
I've always done it like this as well. Initially I did it for the most obvious reason: it gave me the working software that I needed the fastest. Then later on, I always found it to be the best way to find natural abstractions as you go.
How can you say this when many of the worlds most used apps are written in React Native? Same with Electron and desktop apps. I find it hard to believe you can be more productive writing native code when you need two entirely different codebases, compared to a single one, no matter how good of an iOS and Android developer you are.
I don't know if I was using React Native "wrong" or what, but when I tried it out I found it to be a miserable experience. There's almost no usable components "built-in"...there seems to be an expectation that you cobble your UI together using one of a variety of different third-party components or component libraries, and every single one I tried was incomplete, buggy, poorly-maintained, poorly-documented...
Based on that trial: I'd much rather work on two sane codebases instead of one in React Native that's a maintenance disaster. As a bonus, since your apps will be native, they'll probably be faster, feel higher quality, integrate better with the platforms, etc.
You were using it wrong IMO. The platform comes with a lot of built-in components (just look at the docs!) just from importing the React Native package.
You do realize you still have to write a lot of native code in cross platform apps, right? It's what all the most used apps do.
This idea that individually you can be more productive on a cross platform app has no basis in reality. You're still having to concern yourself with platform specific aspects, except now you're also throwing in another layer into the mix for your shared aspects. These shared aspects tend to also not be up to user expectation most of the time, so you're having to rewrite things that comes easy for native apps, to ensure consistency and accessibility.
Such moves makes sense for Facebook. Given who they hire, what they work on. Same for Microsoft, but not sure using them is a good example considering their app experiences are universally terrible. For a lot of other places though? There has been a grand total of zero proven demonstration of increased productivity or dramatic savings. You still have to hire android/ios/windows/mac/linux devs respectfully whenever you eventually want to expand to those platforms.
This is very cool, impressive work in 2 weeks!
Each action seems to have some delay after it, is there any reason for that? Is it because you are streaming the OpenAI response and performing the actions as they come? If not, I imagine streaming the query response and executing each action as they emit would speed it up quite a bit?
There are multiple sources of latency: (1) parsing, simplifying and templatizing the DOM, (2) sending it to OpenAI and waiting for the response, (3) actually performing the action (which includes some internal waiting depending on what the actual action is), and (4) a hacky 2-second sleep() after each action to make sure any site changes are reflected in the DOM before running again. :)
(1) is already very fast. There's a lot of room for improvement in both (3) and (4); we currently set the timeouts very conservatively to improve reliability, but there are a number of heuristics we can use to cut those timeouts substantially in the average case.
Unfortunately for (2) I'm not sure there's much we can do. We only ask OpenAI for one action at a time to give it a chance to observe the state of the page between actions and correct course as necessary. We experimented with letting it return multiple actions at once but that hurt reliability; we can perform more experiments in that direction but it probably won't be a priority in the short term.
Software development isn't really about just acquiring and memorising knowledge to later spit out. You need reasoning, logic and creativity. That AGI can develop complex new software (not just some code that has been scraped of the internet years ago) in 10 years is something I doubt.
We don’t have AGI as of now but it could spark anytime and its acceleration could be extremely fast. It could almost spark and yet never really get there, just get closer and closer and quite never hit the mark. But this is not something that will simply stop a massive disruption in most professions and livelihoods, LLMs could do that easily
