Code reviews dont scale, inherently bottlenecked by how fast you can read code + cognitive capacity. But there are ways to make it easy to make sure PRs dont break prod and keep the quality stable: linters with best practices + company specific coding guidelines, dev environments per PR, comprehensive e2e tests that verify both correctness and performance. Not so easy to setup, but benefits are worth it.
Im working on karinja.ai which I lets teammates share live agent sessions backed by cloud sandboxes, that way you can centralized your agent config within a team so that the output is consistent and results can be previewed without even leaving your browser.
I was about to write what advantage it has over linters but then saw the built on section. Good work. We use megalinter with our flavour of go and vite rules, plus extensive e2e testing after each agent run. Quality of the spec driven agentic PRs are significantly better than the baseline. Megalinter is quite resource heavy and slow, so will definitely check this out
Love it! I think the minimal approach you took is the right path forward. As others mentioned, small harnesses make it possible to run many agents in parallel and in small cloud instances. working on a minimal agent in Go myself for this use case.
I'm betting my startup on it. The subsidised model subscription will start to dry out and providers will lean heavier into locking down how they want their models to be used (Anhropic has been paving the way already). The only way forward is open weight models. If you are working on any LLM powered product be careful betting on utilising user subscriptions.
S3 lifecycle policies and scheduled RDBMS jobs are the low hanging fruit here.
I used to work at a data platform team and built a cleaning service that used tags and object hierarchy trees to find and clean old PII data. Not an easy thing to do as our data analytics bucket had over 7PiB of data.
Overall the architecture was based of 3 components: detector, enforcer, cleaner. Detector sifted through the datalake to find PII datasets(llm based), enforcer tracked down ETL of the datasets in our VCS to set appropriate tags/metada(custom coding agent), finally cleaner used search to find and clean the data based on the metadata.
nice work! I built a similar system at my previous company. It was built on top of github. agent was triggered by the created issue, run in actions, save state in PR as hidden markdown.
It worked great but time to first token was slow and multi repo PRs took very long to create (30+ mins)
Now im working on my standalone implementation for cloud native agents
Im working on karinja.ai which I lets teammates share live agent sessions backed by cloud sandboxes, that way you can centralized your agent config within a team so that the output is consistent and results can be previewed without even leaving your browser.