CharlieDigital

3 ms·

1.
by CharlieDigital 5d ago
The specific design of this system uses the raw memories and allows rebuilding the operational memory from the raw memory (the LLL "Left Leg Layer"). To do this requires that there is an ordering of which memory came last. &
2.
by CharlieDigital 5d ago
I also take a lot of the guidance from influencers with a grain of salt for that reason. What works for the solo dev on greenfield projects rarely scales to the enterprise 1:1. Brownfield. Security policies. Enterprise controls. Legacy
3.
by CharlieDigital 5d ago
I think many devs misunderstand MCP because they work in solo mode . In solo mode, you just have your secrets local. You don't care about auditing access. There's no IT managing the infra and third party secrets. You don&#x27
4.
by CharlieDigital 6d ago
The US is kind of "collapsing" in third spaces both public and private, but especially public due to funding cuts.
5.
by CharlieDigital 6d ago
I would certainly consider Roslyn analyzers capable of covering "a tiny fraction" of possible errors :) They are quite capable of covering for many common types of structural coding mistakes.
6.
by CharlieDigital 8d ago
You would be surprised. Humans will do human things like be extremely inconsistent, ignore warnings (if they are not enforced as errors), skip steps because they are lazy (devs often chose to skip our pre-push hooks and preferred to run in
7.
by CharlieDigital 8d ago
Yes, agree, but also limited to specific types of use cases.
8.
by CharlieDigital 8d ago
I don't think I implied that they could. Each of these are just layers of control at different lifecycles of agent code generation. Analyzers are nice because it gives targeted, static analysis that can prevent certain classes of erro
9.
by CharlieDigital 8d ago
> In other words, MCP was just a bunch of bullshit This is a complete misunderstanding of why a team would want MCP. If you're just using bash scripts, where are you putting your enterprise secrets for external systems? Ho
10.
by CharlieDigital 8d ago
OP's point here is that the overall approach of restricting output token space and using parallel prompts to produce concurrent results and taking the most relevant ones isn't something novel to Jev (not saying there's nothin
11.
by CharlieDigital 9d ago
You can express them as tests, but you also need a feedback mechanism that creates the rule that when the LLM generates some net new code or performs some refactor, that there are these CAPAs that it needs to cover with test cases. The CAPA
12.
by CharlieDigital 9d ago
This may be platform dependent. C# Roslyn Analyzers[0], for example, are quite powerful and can identify complex patterns in code. One approach to deterministic enforcement would be to ensure that the project is set up with an analyzers li
13.
by CharlieDigital 9d ago
This is a question of context management and I suppose some would classify this as "harness engineering" as the trend of the moment. One approach, for example, might be to have the a standalone code reviewer agent that is solely r
14.
by CharlieDigital 9d ago
> It’s actually fine if agents make a lot of boneheaded mistakes. What’s not ok is if they keep making the same mistakes. I worked in life sciences for a bit. There is a process in clinical trials called corrective and preven
15.
by CharlieDigital 9d ago
This is not fully true. Most agents will use curl | jq to slice what they need (assuming a known API)
16.
by CharlieDigital 9d ago
Claude Code (CLI) has been really bad with handling window resizing and layout changes. For long sessions, it will freeze while redrawing. On an M3 Max. With 64 GB or memory. Codex CLI does not have this problem, nor does OpenCode. Ever
17.
Foundations of Agent Friendly Codebases(chrlschn.dev)
1 points by CharlieDigital 9d ago|0 comments
18.
by CharlieDigital 9d ago
Not the case!
19.
by CharlieDigital 9d ago
This section https://openspec.dev/docs/setup links to "Concepts" Concepts links here: https://github.com/Fission-AI/OpenSpec/blob/main/docs-lab/gu... All the docs her
20.
by CharlieDigital 9d ago
Flip side: LLMs have to be very explicitly told to code in "modern" .NET and C# due to lack of representation in the training set. Case in point: extension members from C# 14 is one that LLMs commonly stumble on and requires an ex
21.
by CharlieDigital 9d ago
I recently had a similar episode as the author in another east Asia country: Taiwan. Found myself in Taitung (along the much less densely populated, remote east coast) with several inches of rain forecast. Spent the day at the Taitung Coun
22.
by CharlieDigital 10d ago
This is only true if you only run the code reviewer in the final PR. The way we set it up was that the code review responded to two signals: 1. GH PR webhook 2. The exact same review agents running as an MCP tool that the local agent can in
23.
by CharlieDigital 10d ago
C# gRPC story is really, really good, too.
24.
by CharlieDigital 11d ago
Because your local agent can already see the full codebase; the code review only needs to see what's changing and evaluate the change.
25.
by CharlieDigital 12d ago
I found Luna and even 5.4-mini to be quite good at code review provided a few things: 1. Run it in multiple cycles, only on the diff, and only emit a few findings at a time. 2. Give it a memory so each cycle, it knows the previous finding t
26.
by CharlieDigital 12d ago
Way too shallow; was expecting a lot more meat here...
27.
by CharlieDigital 12d ago
Nowadays, it seems that catering to any audience other than 1) white 2) male is "culture war".
28.
by CharlieDigital 12d ago
> How do you let an agent use a tool that needs credentials without giving the credentials to the agent? I took a different approach [0]. 1. Register a secret and get back an opaque identifier (out-of-band, human action;
29.
by CharlieDigital 13d ago
I think this is a very classic "waterfall" world view. In many cases, the problem can only be understood through many failed solution attempts. It could be because the actual problem is novel. It could be because there is a diff
30.
by CharlieDigital 13d ago
> Then you look at the code. Code that has passed review, generally. You realize that the database schema has been broken silently, and that the agent has rewritten the tests or the golden fixtures to match. I find that the co

More ›