Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aroussi
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
Show HN: Open Royalties – Fund projects with revenue sharing, not equity
(openroyalties.org)
2 points
by
aroussi
8mo ago
|
0 comments
2.
▲
by
aroussi
9mo ago
Thanks! You can download the first few chapters here (free, no opt-in): https://productionaibook.com/hn If it makes you want to get the full book - I wont stand in your way
3.
▲
Show HN: I Wrote a Book – Production-Grade Agentic AI
(productionaibook.com)
1 points
by
aroussi
9mo ago
|
3 comments
4.
▲
Why companies should still hire junior developers in the AI era
(aroussi.com)
6 points
by
aroussi
9mo ago
|
0 comments
5.
▲
Show HN: I wrote a book for engineers building production AI systems
(productionaibook.com)
1 points
by
aroussi
10mo ago
|
0 comments
6.
▲
by
aroussi
1y ago
That's where the human architect comes in (for now at least). We'll try to think of features that would have the least amount of conflicts when merged back to main. We usually max it at 3, and have a senior dev handle any merge co
7.
▲
by
aroussi
1y ago
The system is trying to solve: breaking down large projects into small tasks and assigning sub-agents to work on each task, so the code, research, test logs, etc. stay inside the agent, with only a summary being surfaced back up to the main
8.
▲
by
aroussi
1y ago
The real idea is to make sure that each agent works in its own little world and documents everything. So the main thread context is occupied with the understanding of the project instead of code snippets.
9.
▲
by
aroussi
1y ago
That's exactly why we use separate agents as "context firewalls". Instead of having the main thread do all the work and get its context polluted, with sub-agents, each agent works on one thing, then provides a summary to the
10.
▲
by
aroussi
1y ago
We created a "/pm:import" command before making this project public to pull existing repo issues into local. Hopefully, this will work well. We have tested it, but this is not one of the functionalities that we use on a daily
11.
▲
by
aroussi
1y ago
OP here. It really depends on how you use parallel agents. Personally, I don't run multiple instances of Cloud Code nor do I use multiple screens. I find it hard to focus :) That being said, if a task requires editing three different f
12.
▲
by
aroussi
1y ago
OP here. I wouldn't necessarily call it a waterfall, but it's definitely systemized. The main idea was to remove the vibe from vibe coding and use the AI as a tool rather than as the developer itself. By starting off with knowing
13.
▲
by
aroussi
1y ago
OP here. These numbers are definitely in the ballpark. I personally went from having to compact or clear my sessions 10-12 times a day to doing this about once or twice since we've started to use the system. Obviously, results may vary
14.
▲
by
aroussi
1y ago
Damn those em dashes lol Kidding aside, of course we used AI to build this tool and get it ready for the "public". This includes the README. I will post a video here and on the repository over the weekend with an end-to-end tutori
15.
▲
by
aroussi
1y ago
Cheatsheet is available via /pm:help With that being said, a video will be coming very soon.
16.
▲
by
aroussi
1y ago
We gave up on that dream a while back lol. Instead, we analyze which tasks can be run in parallel (different files, etc) and which need to be worked on sequentially.
17.
▲
by
aroussi
1y ago
I'm going to create a video and post it both here and on the repository over the weekend
18.
▲
by
aroussi
1y ago
100%! Use agents as "context firewalls". Let them read files, run tests, research bugs, etc, and pass essential data back to the main thread.
19.
▲
by
aroussi
1y ago
Yeah, I agree. I never let the AI make any architectural decisions (and I also watch Claude Code like a hawk lol). That being said, since we started using this system, we noticed that our PRDs and implementation plans (epics) became more de
20.
▲
by
aroussi
1y ago
I agree wholeheartedly! When we break down an epics into tasks, we get CC to analyze what can be run in parallel and use each issue as a conceptual grouping of smaller tasks, so multiple agents can work on the same issue in parallel. The is
21.
▲
by
aroussi
1y ago
Great idea! I'll whip something up over the weekend and post the video here and on the repo
22.
▲
Show HN: Project management system for Claude Code
(github.com)
175 points
by
aroussi
1y ago
|
112 comments