Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Schedule tasks on the web

code.claude.com

Post reply on HN
Print view View original

121–130 of 261 posts

Re: Schedule tasks on the web

#121

Post by x187463 »

michaelmior wrote: post #116
chatmasta wrote: post #19

Earlier quoted context omitted.

I love everything about this direction except for the insane inference costs. I don’t mind the training costs, since models are commoditized as soon as they’re released. Although I do worry that if inference costs drop, the companies training the models will have no incentive to publish their weights because inference revenue is where they recuperate the training cost. Either way… we badly need more innovation in inf…

I worry about the costs from an energy and environmental impact perspective. I love that AI tools make me more productive, but I don't like the side effects.

[dead]

Re: Schedule tasks on the web

#122

Post by TeMPOraL »

discreteevent wrote: post #113
TeMPOraL wrote: post #108

Earlier quoted context omitted.

There is no "parameter substitution" equivalent possible . Prompt injection isn't like SQL injection, it has no technical solution (that isn't AGI-complete). Prompt injection is "social engineering" but applied to LLMs. It's not a bug, it's fundamentally just a facet of its (LLM/human) general nature. Mitigations can be placed, at the cost of generality/utility of the system.

> It's not a bug, it's fundamentally just a facet of its (LLM/human) general nature Fair enough but then that means that MCP is not "a bit like asking if "an API" was a critical link in some cybersec incident" Because I can secure an API but I can't secure the the "(LLM/human) general nature."

MCP itself is just an API. Unless the MCP server had a hidden LLM for some reason, it's still piece of regular, deterministic software.

The security risk here is the LLM, not the MCP, and you cannot secure the LLM in such system any more you can secure user - unless you put that LLM there and own it, at which point it becomes a question of whether it should've been there in the first place (and the answer might very well be "yes").

Re: Schedule tasks on the web

#123

Post by primer42 »

simianwords wrote: post #50

I remember when I tried to set something up with the ChatGPT equivalent like "notify me only if there are traffic disruptions in my route every morning at 8am" and it would notify me every morning even if there was no disruption.

“A programmer is going to the store and his wife tells him to buy a gallon of milk, and if there are eggs, buy a dozen. So the programmer goes shopping, does as she says, and returns home to show his wife what he bought. But she gets angry and asks, ‘Why’d you buy 13 gallons of milk?’ The programmer replies, ‘There were eggs!’”

You need to write a clearer prompt.

Re: Schedule tasks on the web

#124

Post by dominotw »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

I dont mean this as a shade but ppl who are not coders now seem to think "coding is now solved" and seem to be pushing absurd ideas like shipping software with slack messages. These ppl are often high up in the chain and have never done serious coding.

Stripe is apparently pushing gazzaliion prs now from slack but their feature velocity has not changed. so what gives?

how is that number of pr is now the primary metric of productivity and no one cares about what is being shipped or if we are shipping product faster. Its total madness right now. Everyone has lost their collective minds.

Re: Schedule tasks on the web

#125

Post by rkomorn »

dominotw wrote: post #124
nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

I dont mean this as a shade but ppl who are not coders now seem to think "coding is now solved" and seem to be pushing absurd ideas like shipping software with slack messages. These ppl are often high up in the chain and have never done serious coding. Stripe is apparently pushing gazzaliion prs now from slack but their feature velocity has not changed. so what gives? how is that number of pr is now the primary metri…

I ask myself the same question.

I'm not seeing the apps, SaaS, and other tools I use getting better, with either more features or fewer bugs.

Whatever is being shipped, as an end user, I'm just not seeing it.

Re: Schedule tasks on the web

#126

Post by dominotw »

rkomorn wrote: post #125
dominotw wrote: post #124

Earlier quoted context omitted.

I dont mean this as a shade but ppl who are not coders now seem to think "coding is now solved" and seem to be pushing absurd ideas like shipping software with slack messages. These ppl are often high up in the chain and have never done serious coding. Stripe is apparently pushing gazzaliion prs now from slack but their feature velocity has not changed. so what gives? how is that number of pr is now the primary metri…

I ask myself the same question. I'm not seeing the apps, SaaS, and other tools I use getting better, with either more features or fewer bugs. Whatever is being shipped, as an end user, I'm just not seeing it.

cto and ceo are now feeling insane pressure to show how they are using ai but its not evident in output. So now they've resorted to blabbering publicly about prs, lines of code ect to save face. And ofcourse ppl giving them voice and platform have their own agendas that prevent them from asking "so what exactly have you shipped stripe from million pr/day".

Its baffling to see these comments on hacknernews though. I guess you have to prove that you are not a luddite by making "ai forward" predictions and show that you "get it"

Re: Schedule tasks on the web

#128

Post by EdgeNRoots »

jwpapi wrote: post #120
nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

I just don’t see it coming. I was full on that camp 3 months ago, but I just realize every step makes more mistakes. It leads into a deadlock and when no human has the mental model anymore. Don’t you guys have hard business problems where AI just cant solve it or just very slowly and it’s presenting you 17 ideas till it found the right one. I’m using the most expensive models. I think the nature of AI might block tha…

[dead]

Re: Schedule tasks on the web

#129

Post by obastani »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

I don't know if this is the future, but if it is, why bother building one version of the software for everyone? We can have agents build the website for each user exactly the way they want. That would be the most exciting possibility to come out of AI-generated software.

Re: Schedule tasks on the web

#130

Post by lancekey »

nickandbro wrote: post #4

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

Ha I just SPECed out a version of this. I have a simple static website that I want a few people to be able to update.

So, we will give these 3 or 4 trusted users access to an on-site chat interface to request updates.

Next, a dev environment is spun up, agent makes the changes, creates PR and sends branch preview link back to user.

Sort of an agent driven CMS for non-technical stakeholders.

Let’s see if it works.

Post reply on HN