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

So the future is basically people asking (praying) to AI to make them money.

Yeah but these people will still think they made the money because they were the ones who asked the smart questions after all ...

While your developers are twiddling their thumbs waiting for Claude to come back online, your competitor is using alternatives to get work done right now and advancing on their go to market timeline.

If you work in marketing, you forgot to give us a link.


Could there be something like a VPN for AI models? VPP?

You send a prompt to a neutral third party who then sends it to an AI model and then routes the response back to you?


u can delete ur data in all of the platforms / use offline / use openrouter with crypto account...literally countless options.

Coming across perfect cubes in the wild must be insane

I wonder whether the four valence electrons occupy fixed quantum configurations or tokens for carbon approximating intellectual consciousness in life

When people say code is the bottleneck, they don’t always mean the lack of code: it’s also the accumulation of code, which becomes like plaque clogging your arteries. When you have too many people pumping out too much code, it can be the death of your startup. Startups have failed from writing way too much code.

amazing how many comments in these discussion talk about startups as if that is all there's to it, you either are at startup or you are plumber... [mind blown...]

Why bother with OpenClaw? Just call the CLI command directly. That is the point of a CLI.

I think the point is that I don't have to remember the command. I just have to tell my agent in plain-English to do X.

For example, we're dragging our feet on Github Config as Terraform at our org so in the meantime I've been using Claude + the gh cli to deploy changes across repos. I don't need to know / remember the gh cli command to pull or push a ruleset, or script a loop in Bash, I just have to say

> Claude pull the ruleset from <known good repo> and push it to <repo 1>, <repo 2>, <repo 3>

The CLI is also nice because it abstracts away authentication. I have another flow which doesn't have a CLI and Claude is more than happy to interpolate the API key that it read from a config file into the chat history (horrifying).


Exactly. Talking in plain English is a lot less mental overhead than reading the man page and figuring out the right command. Nowadays I just use AI instead of remembering ffmpeg commands too. Your point about authentication is important too.

What the hell am I reading, you guys know you can make little scripts for commands with prefilled options or even take in parameters?

That's what the coding agent does if you ask it to record a skill. Yes I can do that manually. But I'll get it wrong a few times before I get it right and waste half an hour in the documentation, if I'm lucky.

Or I just go, "I just created this cloudflare domain. Deploy the site via gh actions to cloudlare pages whenever I push to main. here are my credentials; put them in Github secrets." Or something similarly high level.

The clever thing here is not doing things manually but make sure you generate automation and scripts if you are going to do the same things more often along with skill files detailing how and when to call shit.


Actually if you read the first five sentences of the article, the point of the CLI is to be friendlier for AI agents (in addition to being useful for humans presumably).

> Increasingly, agents are the primary customer of our APIs. Developers bring their coding agents to build and deploy applications, agents, and platforms to Cloudflare, configure their account, and query our APIs for analytics and logs.

> We want to make every Cloudflare product available in all of the ways agents need.


Yeah but you can waste $10-50 having an LLM do that for you instead rather than using your engineering experience to do it. Think of the shareholder value!

That’s easy to game. You just burn tokens.

This won’t be the metric measured for success. It will be something more tractable like tickets completed.

  > more tractable like tickets completed
easy, just make tickets smaller in size (i see people doing this with prs already now to hit 'ai kpis')...

Absolutely not. It will be token usage.

Oh sweet summer child.

I won’t believe AI is truly being met with violence until I see one of these AI tech billionaires get shot multiple times by a person with nothing left to lose. Until we reach that point, it means people still have hope.

You mean like what happened with UnitedHealthcare?

That had nothing to do with AI

I mean, no shit? I was referring to how people are starting to feel powerless and marginalized. And the government, which is supposed to be of the people, by the people, and for the people, clearly doesn't give a fuck about them.

If using an LLM why bother with python? Go for straight shell scripts.

That’s exactly my plan. Too burned out on the npm ecosystem. I don’t have time to update all that shit constantly for a fucking static HTML page

Exactly, so many people reach for these complex toolings and ecosystems.

Their static pages are just a bunch of fucking text files you can print with some CLI commands.


Whether you like it or not, socialism is the key.

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

Search: