I may be misunderstanding your earlier statement then. The moat here is the knowledge, or how would the next iteration of RL solve that?

> it’s just that it can and should be faster.

Not sure if "Make it faster" works, it sounds like "Make no mistakes" 2.0

We came full circle on the problem that also exists with Google Search, and why so many people don't get good results out of it.

> For now, I have an advantage over these people when building applications. But perhaps that's just one round of RL away from being obsolete too.

I don't have a crystal ball, but my eggs are in the basket of "It isn't, and it won't be"

> The only thing that seems relatively future-proof is just being able to communicate clearly what you're trying to do

This somehow contradicts the previous statement. The advantage you have is, because of domain knowledge expertise, you're able to articulate what you want. It's not that you knowing what LazyLoading is that you now can describe it better, you can immediately tell that when your Frontend stalls for 5 seconds after hitting the "Load" button, perhaps it eagerly loads and blocks.

Yes, libraries aren't bug-free, but they give me a reliable abstraction tested in the field. Not rarely you dig into library code if you notice unexpected behavior.

If we could rely on our LLM or colleague written code, or own code, have run through the same amount of requests, sure I wouldn't need to review it, as my confidence can be north of 99.9999% it works correctly. But we can't.

Another example of "More AI, worse app" is amazon.com for me lately. Alexa AI Chat keeps showing whenever I scroll up on the amazon.com mobile page. I don't want Alexa to search for products. Worst thing is, I can't close it. The "X" button just isn't doing anything. So the only way out of it is to refresh the page and avoid scrolling up ...

This has been going on for at least 1 1/2 months by now, and I wonder if it'll ever be fixed.

It is kind of strange to see this sentence, when OAI's definition of what AGI is has been watered down throughout the years.

> I expect and hope for voluntary slowdowns to become commonplace until shared safety bars are established.

Read: Please play by our rules, so we can be the first.

[0] https://youtu.be/nM86DBOqgPM?si=BdoZzp1Dxa4S3C_9&t=616

I think this is a good argument to underline "It's not _just_ the scale". Adding to this, the Github Code Review experience is kind-of broken, the way comments/threads are stacked in the PR overview has not improved, pagination isn't really a thing, and these issues are age old. Hopefully, one day, Github will mature.

Genuine question, what is your alternative suggestion to accessing lower level features then? A hard time I have with GUIs is that their input/output can't be piped. It's much more cumbersome to try to automate a GUI than to automate something in the terminal.

Whilst I get that this is about TUIs, I do believe there is a reason for shell access due to automation. Good abstractions can be put into the GUI, but I'd argue that you should first build the abstraction, then put a GUI on top of it. AWS is a prime example, any of their APIs can be used w/out AWS Console.

The fact that the top comment on this thread calls it out, in a negative way, hints at that you aren't.

Where is this disruption? The longer we go, the more people report that the supposed net-gain of easily 100s of percents is not visible.

I do strongly believe "It's just a tool" - A powerful one, but not one like the invention of the steam machine.