Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
knighthacker
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Show HN: AQ – A multiplayer workspace for coding agents on your own cloud
(aq.dev)
4 points
by
knighthacker
14d ago
|
1 comments
2.
▲
by
knighthacker
1mo ago
Hope-Driven-Development lol We're growing very rapidly. So honestly, standup meetings now became the most important meeting and "definitely not a standup". A lot of product/customer things are decided during the call, en
3.
▲
by
knighthacker
1mo ago
I'm 100% fully in the cloud and strongly recommend it to others. I'm building (AQ.dev) so I'm obviously biased, but almost every single one of our customers ends up bringing their own VMs to the platform instead of using the
4.
▲
by
knighthacker
1mo ago
We still create a ton of end-to-end tests and run them a lot. What changed for us is the review process. While our whole team uses agents to do reviews, we also ask other team members to review the coding session itself rather than the diff
5.
▲
by
knighthacker
1mo ago
Microsoft just shipped something literally called the Agent Framework Harness, plus a "build your own agent harness" tutorial series. The harness is officially a product category now. Their harness is the loop around the model: to
6.
▲
The Microsoft Agent Framework Harness
(devblogs.microsoft.com)
2 points
by
knighthacker
1mo ago
|
1 comments
7.
▲
by
knighthacker
1mo ago
I'm not against open source. However, if I were to guess, I think less than 1% of people actually review, let alone modify the open source projects they use. I don't really buy this argument. I think we're seeing a new modali
8.
▲
by
knighthacker
2mo ago
Love seeing this direction along with Buzz. The hardest problem in multiplayer agents, at least for us, has not been the agent loop. It is scoping and QM's per-person scopes plus shared rooms is a sane answer for a company-wide assista
9.
▲
by
knighthacker
2mo ago
It hurts my eyes looking at this haha .. but that's different than the actual harness as we know it tho! Given their ecosystem, they'll always control the CI/CD part of it, which is fine. It's just painful to use XCode t
10.
▲
by
knighthacker
2mo ago
Since we stopped writing code and started writing prompts instead :)
11.
▲
by
knighthacker
2mo ago
Buy vs Build? Buy. They need this yesterday. Xcode has gotten so bad. It's not even funny anymore.
12.
▲
Apple needs a better coding harness than Xcode
3 points
by
knighthacker
2mo ago
|
6 comments
13.
▲
by
knighthacker
2mo ago
look into .worktreeinclude
14.
▲
by
knighthacker
2mo ago
Agreed. I had to solve this at the harness layer myself. It just makes more sense to me this way. We basically created hooks around these operations and you can configure what happens at these calls. Disclosure: I'm building AQ (aq.dev
15.
▲
Engineers have stopped reviewing PRs
(aq.dev)
11 points
by
knighthacker
2mo ago
|
1 comments
16.
▲
by
knighthacker
2mo ago
I'm a huge proponent of that with my team. We stopped doing PR reviews and instead do session reviews. It just makes so much more sense now. It's more important to understand the conversation, context, decisions made, why were the
17.
▲
by
knighthacker
2mo ago
Ugh .. what do we do now? jk
18.
▲
by
knighthacker
2mo ago
I'm obviously biased, but I'm building aq.dev, a shared workspace for running coding agents with a team, so I watch a lot of people's sessions more than my own haha. If I'm between meetings, then I'm really watching
19.
▲
by
knighthacker
2mo ago
Local AI is going to win. Not because it's cheaper btw.
20.
▲
by
knighthacker
2mo ago
The most interesting part is Boris' recommendation to delete your Claude.md every 6 months to see what the model is capable of. The link in the post sends you directly to that moment.
21.
▲
by
knighthacker
2mo ago
I'm thinking a lot about this recently as I'm building AQ.dev (Multiplayer coding harness). My instinct is to keep it simple and not trying to do too many shenanigans with these files and let engineers maintain control.
22.
▲
by
knighthacker
2mo ago
Yup. That's pretty much the most interesting part.
23.
▲
by
knighthacker
2mo ago
The scanner is the least interesting part of this. The harness around it is the product: dedup across runs, false-positive tracking, budget controls, CI gating. That is the layer where we'll see most interesting innovations in my opini
24.
▲
by
knighthacker
2mo ago
This is where Opus 5 shines
25.
▲
Interview with Boris Cherny [video]
(youtube.com)
74 points
by
knighthacker
2mo ago
|
80 comments
26.
▲
by
knighthacker
2mo ago
There's probably a ton of intangible factors to this, but how do you measure the ROI on this?
27.
▲
by
knighthacker
6y ago
Nope. You can easily refresh/retake the interview.
28.
▲
by
knighthacker
6y ago
We've designed BetterLeap to simplify and enhance the most painful and complicated part of career development — job search. So whether you're just beginning your journey, or are actively looking to transition, I hope that you find
29.
▲
Show HN: BetterLeap – Interview Once, Apply Everywhere
(betterleap.com)
19 points
by
knighthacker
6y ago
|
3 comments
30.
▲
by
knighthacker
8y ago
Amazing founder and a great company. I’ve worked for and with him before in prior ventures. One of the most intelligent and sincere people I’ve ever met.
More ›