Live data from Hacker News

Learnings from building AI agents

cubic.dev

21–30 of 70 posts

Re: Learnings from building AI agents

#21
> 2.3 Specialized Micro-Agents Over Generalized Rules Initially, our instinct was to continuously add more rules into a single large prompt to handle edge cases

This has been my experience as well. However, it seems like the platforms like Cursor/Lovable/v0/et al are doing things differently

For example, this is Lovable’s leaked system prompt, 1550 lines: https://github.com/x1xhlol/system-prompts-and-models-of-ai-t...

Is there a trick to making gigantic system prompts work well?

Re: Learnings from building AI agents

#22
post #20

"After extensive trial-and-error..." IMO, this is the difference between building deterministic software and non-deterministic software (like an AI agent). It often boils down to randomly making tweaks and evaluating the outcome of those tweaks.

Afaik alchemists had a more reliable method than ... whatever this state of affairs is ^^

Re: Learnings from building AI agents

#23

> Encouraged structured thinking by forcing the AI to justify its findings first, significantly reducing arbitrary conclusions. Ah yes, because we know very well that the current generation of AI models reasons and draws conclusions based on logic and understanding... This is the true face palm.

Humans work pretty much the same way

Several studies have shown that we first make the decision and then we reason about it to justify it

In that sense, we are not much more rational than an LLM

Re: Learnings from building AI agents

#26
post #20

"After extensive trial-and-error..." IMO, this is the difference between building deterministic software and non-deterministic software (like an AI agent). It often boils down to randomly making tweaks and evaluating the outcome of those tweaks.

Otherwise known as science

1:Observation 2:Hypothesis 3:test 4:GOTO:1

This is every thing ever built ever

What is the problem exactly?

Re: Learnings from building AI agents

#27
post #18

I think they skipped over a non-obvious motivating example too fast. On first glance, commenting out your CI test suite would be very bad to sneak into a random PR, and that review note might be justified. I could imagine the situation might actually be more nuanced (e.g. adding new tests and some of them are commented out), but there isn't enough context to really determine that, and even in that case, it can be wor…

yep completely agreed, how can that be the best example they chose to use?

If I reviewed that PR, absolutely I'd question why you're commenting that out. There better be a very good reason, or even a link to a ticket with a clear deadline of when it can be cleaned up/reverted

Re: Learnings from building AI agents

#28
When I read "51% fewer false positives" followed immediately by "Median comments per pull request cut by half" it makes me wonder how many true positives they find. That's maybe unfair as my reference is automated tooling in the security world, where the true-positive/false-positive ratio is so bad that a 50% reduction in false positives is a drop in the bucket

Re: Learnings from building AI agents

#29
post #10
post #9

Lessons.

https://nolearnings.com/

I don't like the word learnings either, but you write for your audience and this article was probably written with the hope that it would be shared on LinkedIn.

Learnings might be the right choice here.

I wouldn't complain if the HN headline mutator were to replace "Learnings" with "lessons".

Re: Learnings from building AI agents

#30
post #20

"After extensive trial-and-error..." IMO, this is the difference between building deterministic software and non-deterministic software (like an AI agent). It often boils down to randomly making tweaks and evaluating the outcome of those tweaks.

Afaik alchemists had a more reliable method than ... whatever this state of affairs is ^^

You're saying alchemy is better than the scientific method?
Post reply on HN