Hacker Newsnew | past | comments | ask | show | jobs | submit | Muromec's commentslogin

It may not be exploitation, but one can question how fair is the exchange rate of risk to reward and whether answering "free market" makes the question go away.

I mean they have a point if you account for issuing new shares.

If the bullshit job is really bullshit by design and is intended to solve unemployment crisis, then LLMs will not threaten them. There will be a new kind bullshit job to plug the new hole in the resource allocation algo.

They're by structural design but no individual employer thinks they're making a bullshit job. It's a bit like how every vendor sets prices but really, the federal reserve does.

>Morally speaking, figuring out how to mitigate this toxic byproduct is part of our remit

What's hard to figure out here? You either pay taxes or you build cathedrals. While you are doing neither the communist tendencies keep growing, because people see they are squeezed. It's that communism has any answer to it really, but the tendencies will keep growing until something happens.


> What's hard to figure out here?

Negative externalities are hard to figure out.

Since parent mentions "toxic byproduct": Say you're the company that invented Teflon pans. you made billions. You saved billions in time for all the users of the pans... A true entrepreneurial success.

But, by how many billions did you fuck up the environment, people's health etc with the spread of PFAS everywhere?


Free borders policy is a special case of free market, so of course more competition is intended to drive the cattle prices down .

That is kinda the intention, not the accident thing

I have a different way, but still trying to figure out how well it works. Instead of going into recursion, the agent is allowed to restart the thread by doing the summarize/debrief/reflect pass, writing key findings into persistent memory and rewriting the prompt whenever the context goes too large or it gets stuck. Recursion with TCO if you may.

In a way it's a generalization of the spec-driver approach, but in addition to the the formal spec the carryover buffer lives in the memory.


Kiro does this automatically from what I can tell using it

Most of the drones are operator guided and the ether is really badly jammed out there with the exception of glass and that new redacted thingy.

It will start moving really fast once the automatically targeted anti-drone turrets get to production pipeline. Now calling it anti drone is a bit of self delusion -- pattern recogniser gonna pattern recognise whatever it's told to, including "anything moving that emits EV or IR and not broadcasting the friendly signal hard enough".

I wonder how it is supposed to behave if the invasive fauna decides to call it quits and surrender. Should the robot following the Convention or is it yet another accountability sink?

One thing I'm sure of -- the killing not will b blessed by at least one Orthodox priest, maybe this year. OCU will have to develop guidance on that matter.


I saw an llm bootstrapping and testing it's own harness and rewriting it's own system prompt. If that's not self improving then I dunno what is.

Can the thing enter into an runaway looop while improving the model itself -- probably not, not without us not noticing at least


Then Anthropic did their part and blames the good customer after implementing "reasonable" measures to prevent it. They still get paid.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: