Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ramoz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
31.
▲
Show HN: Code walkthroughs you can send as a file
(guides.show)
3 points
by
ramoz
1mo ago
|
0 comments
32.
▲
by
ramoz
1mo ago
Nobody's replacing the social and community aspects of GitHub. I think it's fine if we begin to move back towards distributed software supply chain infrastructure.
33.
▲
Show HN: An interactive UI for the grill-me skill
(plannotator.ai)
4 points
by
ramoz
1mo ago
|
0 comments
34.
▲
by
ramoz
2mo ago
> On (2), I do find myself consuming agents' gigantic text responses, writing 8-bullet-point responses to guide them, then iterating that way. It's pretty exhausting. I could see inline comments providing much better ergonomics
35.
▲
by
ramoz
2mo ago
I'm trying some of the diagrams in elk and it seems to break the logical flow. You can try it with Line9's first chart: https://mermaid.ai/live/edit#pako:eNpVVEtv2zAM_iuCTilgB1mbxq... While it's nice and
36.
▲
by
ramoz
2mo ago
That does not seem like a fair/accurate reference? The antithesis author states: "we’ve found bugs in every Raft implementation we’ve tested, including HashiCorp Raft, Aeron Cluster, OpenRaft, and MicroRaft"
37.
▲
by
ramoz
2mo ago
idk. In my experience the build/compile experience has been far worse esp for fast iterating. Even concurrency models did not seem as intuitive as Go's. Im no systems expert - have deployed practical and performant distributed sys
38.
▲
Show HN: Local Code Review
(plannotator.ai)
2 points
by
ramoz
2mo ago
|
0 comments
39.
▲
by
ramoz
2mo ago
Some confusion in this thread... this is not a patent application. This is a fully granted patent. Looks like they fast-tracked it. Filed application in March, granted in June. You can see the actual claims here: https://ibb.co&#
40.
▲
by
ramoz
2mo ago
This is not a patent application. This is granted. They applied in March and was fast-tracked & issued in June. This is a full grant. You can see the claims here: https://ibb.co/k2mVVkFN
41.
▲
by
ramoz
2mo ago
This is the official search by the way for anybody wondering. It mirrors the internal examiner tool. search: "12670045".did
42.
▲
by
ramoz
2mo ago
> The problem is that these instructions are not applied after the model has finished doing the work, it becomes part of the same work - This is why /bro skill works. https://github.com/backnotprop/bro/blob
43.
▲
by
ramoz
2mo ago
Fair, I don't. The same is still true with an LLM as a judge in the loop
44.
▲
by
ramoz
2mo ago
> I have been using Codex with auto-approve mode for a couple months and haven't had a single incident I've been running both in yolo mode and haven't had a single incident. --- None of this is really about figuring out ho
45.
▲
by
ramoz
2mo ago
https://github.com/backnotprop/plannotator is still very useful for annotating html prototypes and markdown plans (as well as terminal agent messages). Was glad to see codex team pick up the feature requests in the Cod
46.
▲
by
ramoz
2mo ago
Also on the front page this morning: "An OpenAI Strategist Says AI Labs Should Rival Government Power" https://news.ycombinator.com/item?id=49232778
47.
▲
Show HN: Play Tetris in the terminal (solo and pvp)
(github.com)
3 points
by
ramoz
2mo ago
|
1 comments
48.
▲
Opinion: Sandboxing efforts falter to the law of diminishing returns
(twitter.com)
2 points
by
ramoz
2mo ago
|
0 comments
49.
▲
Bro
(github.com)
4 points
by
ramoz
2mo ago
|
1 comments
50.
▲
by
ramoz
2mo ago
example: https://x.com/dillon_mulroy/status/2079238358358778142?s=20 original: https://github.com/backnotprop/bro
51.
▲
by
ramoz
2mo ago
> The problem is defining what quality means, and providing a way for agents to optimize the harness using that lever. I've built and my team uses plannotator [1] for specs and code review. It stores all human annotated feedback, w
52.
▲
by
ramoz
2mo ago
I mean, the dude uses a lot of jargon, ego, and mythologizes stuff but the article comes down to a pretty simple practice: Run a big task queue, have a smart model manage a cheap model on every ticket, set up a cron for models to automatica
53.
▲
by
ramoz
2mo ago
Most of this is ai generated, but those exact words were mine.
54.
▲
by
ramoz
2mo ago
in other words, the web is beautiful again
55.
▲
by
ramoz
2mo ago
Funny bc I built it with codex and largely though codex image gen https://x.com/backnotprop/status/2083211982338146553
56.
▲
Effective HTML
(effectivehtml.com)
9 points
by
ramoz
2mo ago
|
8 comments
57.
▲
by
ramoz
2mo ago
The friction of agents having to monitor CLI is just too annoying right now Thus, this is ultimately: 1. a harness problem (or harness orchestrator) 2. a protocol problem With 1. Claude Code does this very well - yet most OSS har
58.
▲
Show HN: View GitHub attachments in a gallery (HTML explainers, screen videos)
(twitter.com)
1 points
by
ramoz
2mo ago
|
0 comments
59.
▲
by
ramoz
3mo ago
A harness is a part of the intelligence stack. It's no longer about raw access to the model Also, I have seriously used most harnesses - One feels like it's being built in a place that truly understands AI and where agentic engine
60.
▲
Show HN: 2n – write directory based notes in the terminal
(github.com)
2 points
by
ramoz
3mo ago
|
0 comments
More ›