876 karma · joined January 17, 2023
The key I’ve found is human peer review. The reviewer jumps on a live call with the developer, pulls up the PR with transcription on, and asks questions. At the end of the call, the transcript passes back into the coding agent and the PR is polished up, becoming more self-documenting, and the humans are left with some degree of common understanding of what’s going on.
I’ve been operating my team of ~15 this way for 9mo to great effect… there is simply no going back to the stone ages.
Maybe this open invitation to the world pushes the boundaries of that definition, but I don’t see where an expectation of privacy comes in here.
With index funds you never have the strong winners to do this with, and so giving is far less tax-efficient.
The main limitation we’ve had to agentic coding is an understanding of this system that spans processes running on different machines and architectures.
I’ve become so cynical that I cannot read this phrasing without thinking it came from… an LLM.
This cynicism also negatively impacts human communication. This constant doubt of whether there was a thinker on the other side of the text.
I’ve always wanted to use NetBSD for an application for an embedded system / IoT device but never had the pleasure (yet!).
I have found that the “pro” approach is much more holistic and able to tackle rather “creative” problems that require very careful design and the overall artifact is tight and self-consistent. — Claude Code by comparison is incredible in exploration and targeted implementation but indeed is not great at seeing the forest.
But problem is this could lead to abuse of the CVE system to try to force rapid adoption of attacked packages. What prevents this?