rsalus

8 ms·

31.
by rsalus 4mo ago
tests are an important signal of course, but the use case you describe doesn't necessarily mean you need to follow TDD. the data suggests that creating the tests after the code is just as or even more effective, and at significantly ch
32.
by rsalus 4mo ago
this is not really backed by any empirical evidence. there are simply more efficient means of verifying outputs than TDD.
33.
by rsalus 4mo ago
for LLMs, TDD amounts to little more than ceremony. there is a study on this exact topic: https://arxiv.org/pdf/2602.07900
34.
by rsalus 4mo ago
not necessarily, TDD has little bearing on output quality
35.
by rsalus 4mo ago
I was a big proponent of encoding TDD red-green-refactor methodology into my agent workflows until recently when I made the same realization after reading this study: https://arxiv.org/pdf/2602.07900 TLDR; it found tes
36.
by rsalus 4mo ago
agreed but depends on then language. for instance, the .NET equivalent (MemoryCache) is pretty poor.
37.
by rsalus 4mo ago
not really true, SQLite supports WAL mode which allows concurrent writes (technically write _attempts_, but these writes are exceptionally fast and are serialized to the file-system anyway, so functionally equivalent to concurrent writes fo
38.
by rsalus 4mo ago
functionally they operate as a marketplace for cloud providers. I feel like there is value there, especially as API costs rise and companies explore cost-saving/efficiency. IMO, this is a particularly attractive value prop in the SMB s
39.
by rsalus 4mo ago
there is a difference between concurrency in a distributed environment and concurrency on a single machine across processes. SQLite is incredibly useful for the latter. you seem like the inexperienced one to me..
40.
by rsalus 4mo ago
mirrors my own experience creating a persistent event log. I started with JSON, then JSONL, etc until finally landing on SQLite.
41.
by rsalus 4mo ago
they need to make 5t-10t back, but not necessarily through selling tokens. as we can see, the frontier labs are making vertically integrated products. their revenue is no longer strictly tied to inference.
42.
by rsalus 5mo ago
often times the classical Greeks + Romans would cite their family lineage using works of Homer and other poets
43.
by rsalus 5mo ago
https://github.com/lvlup-sw/exarchos It's an SDLC workflow harness for agents. Instead of using skills to encode my typical workflows (e.g., create PRD, then create plan using TDD, then dispatch subagents, etc) I&
44.
by rsalus 5mo ago
not really.. I never understand the inclination to be reductive. the patterns emerging can be fairly novel.
45.
by rsalus 5mo ago
agree, although the pattern I've been following is to provide a self-contained CLI for portability and usability purposes, and then an "mcp" subcommand which launches an MCP server over stdio. ultimately the "CLI" a
46.
by rsalus 5mo ago
the real solution is to simply provide hints in responses so that the model may self-correct, e.g., recommended next actions, describe commands to get schema definitions, etc.
47.
by rsalus 6mo ago
100p agree. Most code reviews devolve to nitpicking anyway. I think it's much more valuable for teammates to review the _design_ and _intent_ rather than the explicit artifacts.
48.
by rsalus 6mo ago
Great paper. > If AI displaces human workers faster than the economy can reabsorb them Big if.
49.
by rsalus 7mo ago
mostly by virtue of being a common standard. MCP servers are primarily useful in a remote environment, where centralized management of cross-cutting concerns matters. also its really useful for integrating existing distributed services, e.g
50.
by rsalus 7mo ago
that's a pretty interesting idea. It would be nice if there was such a standard. the approach I'm taking right now: a CLI that accepts structured JSON as input, with an 'mcp' subcommand that starts a stdio server. I bun
51.
by rsalus 7mo ago
yes, but clis thus need self-service commands to provide guidance, and their responses need to be optimized for consumption by agents. in a sense, this is the same sort of context tax that MCP servers incur. so in my view cli and MCP are co
52.
by rsalus 7mo ago
MCP is very much not dead. centralized remote MCP servers are incredibly useful. also bespoke CLIs still require guidance for models to use effectively, so it's clear that token efficiency is still an issue regardless.
53.
by rsalus 7mo ago
Doubtful.
54.
by rsalus 7mo ago
what does devarch do exactly? why not OSS?