I think specifically those opinionated within current generations mostly hate it. Fruit celebrity love island shows that plenty of younger generations are entirely content to consume its content. Its possible that most current generations would as well. Trash TV is extremely popular and LLMs are well suited to produce that type of content.
Nicki Minaj has factor 10 listens over a band like Tool. The money will pick the close to zero production cost for 9/10ths of the viewers every time and the platforms will prioritise the many.
I very much doubt boycott has enough weight in the long run to hold back generated content from taking over most of the bigger spaces. We've already seen this happen in recent years with staged content mopping up a lot of the most viewed content by manipulating potential viewers. Cheap influencer content has similarly squeezed cultivated content ad revenue through volume and consistency on YouTube.
If you want change then the route would have to be a legal one, not a social movement. Especially since we've mostly forgotten how to do the groundwork for social movements, leaving us all hand wringing and shouting into the void.
> Someone said it as a joke, but I want AI to be doing my dishes and sorting my laundry while I write books and compose music. I don't want AI writing books and composing music so I have more time to do my dishes and sort my laundry.
Well then we should maybe ask ourselves why RealityTV gets more views than well written work.
and you'll blow the context over time and send to the LLM sanitorium. It doesn't fit like the human brain can.
If a junior fucks production that will have extroadinary weight because it appreciates the severity, the social shame and they will have nightmares about it. If you write some negative prompt to "not destroy production" then you also need to define some sort of non-existing watertight memory weighting system and specify it in great detail. Otherwise the LLM will treat that command only as important as the last negative prompt you typed in or ignore it when it conflicts with a more recent command.
> and you'll blow the context over time and send to the LLM sanitorium. It doesn't fit like the human brain can.
The LLM did have this capability at training time, but weights are frozen at inference time. This is a big weakness in current transformer architectures.
> the employer can hire a new senior engineer at below market rates to accommodate the specific learning they have to do for their new role.
Money doesn't cleanly convert into time.
Having juniors and mid-levels is about being able to promote an existing mid-level that knows the team and the system, with zero downtime. It's much easier to replace a junior than a senior because of the lower expectations and risk.
Furthermore, a lot of companies are struggling to hire right now because the market conditions creates a flood of applications and its quite hard to discern who's a waste of time or not which leads to hiring processes taking longer.
> Having juniors and mid-levels is about being able to promote an existing mid-level that knows the team and the system, with zero downtime. It's much easier to replace a junior than a senior.
Yeah but the point of this post is that it makes an assumption that your company doesn't have mid-levels or juniors.
as knowledge is commoditized the bar for junior raises, what was advanced math research a century ago is now undergrads' homework. I don't see why code is so special in that regard that cannot progress beyond artisanship.
> Furthermore, a lot of companies are struggling to hire right now because the market conditions creates a flood of applications and its quite hard to discern who's a waste of time or not which leads to hiring processes taking longer.
Hiring is the most important function in any company, full stop.
If they aren't good at hiring, well then they shouldn't be running a company. There are no excuses. If HR aren't up to the task, then they should be replaced, and so on up to the level of the CEO, until whatever incompetence has been flushed out. Shareholders have to demand this.
A company not being able to hire is just as ridiculous as a restaurant not being able to serve food.
If they are receiving a flood of applications which is hard to sift through, they are already doing everything wrong. Shareholders have to nuke these kind of people.
> If they are receiving a flood of applications which is hard to sift through, they are already doing everything wrong. Shareholders have to nuke these kind of people.
That's why some companies will contract with temp agencies for relief.
> This isn't a story about one bad agent or one bad API. It's about an entire industry building AI-agent integrations into production infrastructure faster than it's building the safety architecture to make those integrations safe.
Are they really so clueless that they cannot recognise that there is no guardrail to give an agent other than restricted tokens?
Through this entire rant (which, by the way, they didn't even bother to fucking write themselves), they point blank refuse to acknowledge that they chose to hand the reins over to something that can never have guardrails, knowing full well that it can never have guardrails, and now they're trying to blame the supplier of the can't-have-guardrails product, complaining that the product that literally cannot have guardrails did not, in actual fact, have guardrails.
They get exactly the sympathy that I reserve for people who buy magic crystals and who then complain that they don't work. Of course they don't fucking work.
Now they're blaming their suppliers for not performing the impossible.
Giving agents direct access to devops? Idk man, that's quite the bleeding edge. I mean how hard is it to retain the most important procedures as manual steps?
If we must have GasTown/City/Metropolis then at least get an agent to examine and block potentially harmful commands your principal agent is about to run.
People can sell me layers ontop of JIRA but you can't position yourself to replace it, too much already integrates with JIRA and if you're not a startup then its a political cliff edge to try to make a case to replace JIRA.
reply