People more often do the same thing and act like llm’s.

Exactly. Who you blame depends on if it was introduced in beta 1 or RC.

Years ago API’s and apps that used them were expected to do some work offline and on slow networks. Then, suddenly, everyone was expected to have stable Internet to do anything. The reason, I think, is the few apps that expected to be always online seemed better to users and easier to architect. So most architectures went that way.

The reason is developers are worse. A decade or two ago, developers were nerds who loved tinkering with computers. Today tech is big money so everyone wants in. Most devs don't care, it's just a paycheck. Until someone starts setting expectations and holding people responsible for their trash code, we'll continue to see code monkeys write broken codebases. Not to mention where is the mentorship? I've worked as a mechanic, I've worked in construction, I've worked in a store. In all the above, I was mentored. Not for very long in the store but still, the other two have 2 year apprenticeship programs.

The i got a degree and a dev job, apprenticeship? Nah dude here's a big legacy app for you, have fun. Mentorship? Okay I technically had a mentor. We had a lunch every couple months, talked about stuff a bit but nothing much. And I mean this is going to sound a bit pompous but I'm above average. I had mostly A's in university, I finished every single project alone and then helped others. I was a TA. I corrected the professors when they made mistakes. I wrote a lot of code in my free time. I can't imagine what it must be like for one of my peers who honestly didn't know Jack shit and still graduated somehow.

I'm working on an app right now, took over after two other guys worked on it for about a year. This app isn't even in prod yet and it's already legacy code. Complete mess, everything takes like 5 seconds to load, the frontend does a crapload of processing because the data is stored and transferred in entirely the wrong structure so basically they just send all the data and sort it out on the frontend.

I honestly think the fastest way to get this app working properly is to scrap the whole thing and start from scratch but we have a deadline in a couple months so I guess I'll see how it goes.

> Then, suddenly, everyone was expected to have stable Internet to do anything.

I had reasonable - not mega - internet in Australia at the time. But the first 5 years of Steam sucked hard. Get home from work, go to play [game of choice] only to find it will take hours to update.

Vision Pro, different kind of device but same idea

No one wants it, though.

The Apple Watch though is much more successful than the iPod ever was.

Times is taking a risk. The costs of all this will fall on them, if they don’t get the judgement they sought at the end of the day. Plus OpenAI controls those costs and could drive them up. Plus any future litigation by OpenAI users suffering damages due to this could arguably be brought against Time years forward. It’s an odd strategy on their part for evidence that could have just been adduced by a statistician (maybe).

Some of each

If you ask, just show me the prompts, you will invariable just get llm generated sets of prompts.

As long as they provide the prompt and output combo, and the output solves the requirements of the assignment, I don’t see the difference. Half the students are probably asking the llm for prompt help also anyway.

I’d argue that making students give generic regurgitated info as an assignment is the actual issue. Make a good assignment…

The request is not the one that would happen in real life, it's rather trying to point out where the actual value is.

Your right, the “own identity” part is the problem. You can act on your own agency or you act as an agent for someone else.

AI today is only the second. We tell it what we want, it acts by our impetus, but what it does or how it does it, is up to it.

So we’re back to programming?

True, it’s all machine language in the end. But could you imagine brute forcing UI elements and all, every single time? Maybe eventually.

It's funny you mention UI, because for me this is the first place I'm experiencing this, in web development: LLMs are better at the 'brute force' nature of e.g. Tailwind (inline UI styling) vs. needing to handle the abstractions of indirectly-applicable CSS classes. That's a really small, high level example, but to me it demonstrated how less abstraction actually makes prediction easier for the LLM.