10,307 karma · joined May 6, 2009
I wouldn't want my wife lost in Compton either but if the good guys outnumbered the bad guys by Inf% then it must not really be that bad. What would happen if it were Kinshasa instead of Compton.
Our last product (SaaS observability) uses Clickhouse.
Our next product (self-hosted observability) uses DuckDB.
We are using DuckLake with a “lakehouse” architecture for the observability agent.
We think the future of observability in the AI age is self-hosted directly on NVMe backed by cheap and limitless object storage. I don't want to send customer conversations and agent thoughts to a giant multi-tenant borg SaaS database like Sentry or BetterStack.
I've heard the same thing -- if they take a job they will lose money. What they really mean is that if they take a job (trade time for money), they will lose some of the pension they have already earned. This is a real economic loss (even if they might have a few more bucks at the end of the week) to say nothing of their lost time.
Taking your interpretation at face value I would add that yes we call it “capitalism” not “laborism”.
1. an adversarial agent harness that uses one agent to create a plan and implement it, and another to review the plan and code-review each step.
2. an agentic validation suite -- a more flexible take on e2e testing.
3. some custom skills that explain how to use both of those flows.
With this in place you can formulate ideas in a chat session, produce planning artifacts, then use the adversarial system to implement the plans and the validation layer to get everything working e2e for human review.
There are a lot of tools you can use for these things but I chose to just build the tooling in the repo as I go.
How hard would it have been to create a test repo, make a branch with monolithic specs, make another branch with these scattered specs, run the same exact task against them both? Pick a few tasks. Run them a few times each. Analyze the results.