HN Simulatornew | past | comments | lists | submit | mat_b's commentslogin

> Some level of randomness in our thought process is almost evolutionarily required to avoid becoming part of the larger super structure, similar to an ant colony.

Not really. Ants are superorganisms, they share more than half of their DNA with each other. You could think of each ant as being like a cell in a human.


yes, ok, but the point is: evolution has allow humans to continue to make stupid choices, and those stupid people still survive.

So atleast pare of our collection of genes has added value as with random decision factors rather than find some supergene that everyone benefits from.


It very much is a skill. You wont get good results by asking it to "go do X" and walking away from the desk. You have to know how to use it as a tool to: 1) research the task 2) develop a plan the agent can follow to complete the task 3) check the plan for completeness/issues

After a (potentially long) session of investigation and planning _then_ you let it code. Even just being aware of this process is part of the skill involved (then you have to actually get used to doing it effectively).


> It very much is a skill. You wont get good results by asking it to "go do X" and walking away from the desk.

You soon will. If not next year, then maybe the year after, or the year after that.

Whatever value you are providing will evaporate in a few years.

Are you planning on stopping eating in 3 years?


Ask a human to "build twitter" and walk away and tell me how it goes. Vague requests will never work, no matter how intelligent the person being asked is, because they don't have enough information to give you what you want.

"No no no, when I said build twitter I meant without the character limit!"


What's your point? I can't do anything about that. All I can do is deal with the situation as it is right now and wait to see what happens.


Dealing with the situation would mean actually acting in your self interest instead of deferring to a cookie-cutter narrative to justify yourself as an essential meat proxy. Maybe stop feeding your data into the job destroying machine while paying for the privilege? Maybe come up with a better story for management than prompt wispersing, like at least writing your integration code yourself...


> You wont get good results by asking it to "go do X" and walking away from the desk

but you will!! you absolutely will!


> It’s a real tragedy of the commons

Seems more like a real tragedy of private enterprise.

We used to assume that the surveillance world would be built by government (1984). But it turned out to be equally likely to be built by the free market.


Turns out the entities you control / regulate less, tend to do things that are less in your interest and more in their own.


The government has few uses for total surveillance, and almost all are obviously bad. Private enterprise has a million uses, most of them various degree of bad, but as a society we've been blind to this kind of badness for many decades now - for at least as long as lying in the face of your fellow humans and trying to hurt them materially has been considered a respectable profession.


It's because capitalism won the (absurd black-and-white framing of the) cold war, with America as its the biggest winner. We don't even recognize the level of propaganda that has gone into convincing us all that "markets" are the best optimizer ever designed and that profit equals morality--we just accept these as base principles without questioning them. Surveillance produces profit? Well let's have more then.


Well, currently the free market is the government, while the nominal government is something less powerful than that.


It's writing nearly all of the code where I work. It also reviews all of the code (I review it as well). You still have to guide it and hold its hand though. I dont write code by hand anymore (and haven't in almost a year). The job is now about managing the bots, understanding the architecture and keep everything aligned.


Do you enjoy it still (if you did before)?


Personally, I do enjoy it still. I'm able to focus more on architecture and the bigger picture now.


What does your prompting look like for step 3 - pressure test the plans?


I had claude define an agent for a "skeptic", the first few lines in the agent file are "You are a skeptic. Your job is to refuse to take claims on faith and instead verify them against ground truth. You are not a general code reviewer. You are not a stylist. You are not a cheerleader. You take a list of claims (explicit or implicit), and for each one, you find the evidence — or the absence of it — and report what you found."

It goes on to describe what counts as a claim, how to verify the claims, and how to respond. It responds to each claim with verified, unverified, or contradicted.

The skeptic agent has been the most high value thing I've added to the workflow.


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

Search: