I think pi-mono (https://github.com/badlogic/pi-mono) is pretty close.
The extensibility is wonderful and a much better fit for how I work compared to Claude Code.
I’m in a similar boat. Many artists I listen to on Bandcamp offer cassettes(!) at a fair price and will charge a comparable price for the digital. However, I’ve seen some artists charge thousands for digital only but $10 for a tape that includes the digital version.
I don’t know why they do this, but I do know I have an ever growing stack of tapes I can’t listen to…
I am coming back to this. I’ve been using Claude pretty hard at work and for personal projects, but the longer I do it, the more disappointed I become with the quality of output for anything bigger than a script.
I do love planning things out and clarifying my thoughts. It’s a turbocharged rubber duck - but it’s not a great engineer
At first I thought becoming “10x” meant outputting 10x as much code.
Now that I’m using Claude more as an expensive rubber duck, I’m hoping that I spend more time defining the fundamentals correctly that will lead to a large improvement in outcomes in the long run.
My personal experience was that of a decrease in productivity until I spent significant time with it. Managing configurations, prompting it the right way, asking other models for code reviews…
And I still see there is more I can unlock with more time learning the right interaction patterns.
For nasty, legacy codebases there is only so much you can do IMO. With green field (in certain domains), I become more confident every day that coding will be reduced to an AI task. I’m learning how to be a product manager / ideas guy in response
Neat! I am going to check this out.
I recently built an MCP system similar to this called Nonlinear (so clever) that uses SQLite for storage that lives outside the repo.
Honestly though, in repo is the better option.
Claude recommended I use Tilt for setting up a new project at work.
I wasn’t sure if it was worth it…is it pretty easy to set up a debugger? Not only do I have to adopt it, but I have to get a small team to be OK with it.
Our target deploy environment is K8S if that makes a difference. Right now I’m using mise tasks to run everything
Yeah I find it pretty funny that so much of us (myself included) threw out strict documentation practices because “the code should be self documenting!”
Now I want as much of it as I can get.
Create a file like conventions.md in the root of your repository with specific commands for common tasks: running tests, linters, formatters, adding packages
Set this as part of the files it reads on startup. Then ask aider to look at your codebase and add to it :)
Aider has a lot of slash commands to familiarize yourself with. Ask and web are crucial commands to get the most out of it.
My recommendation to anyone is to use ask the most then tell it to “implement what we discussed” when it looks good.
I’ve been floating around a similar set of ideas and it’s been very fun (if not all that useful yet) to build
Did you try taking it one step further where a “recruiter” has to hire the engineers after a screening process? I wonder if this could get you even better AI engineers
Yeah that was what I was afraid of. I thought I saw in the caddy code that they did a sort on file name, but I must have misread it.
Thanks for responding!
Edit: after looking more closely at sprig, the solve was sortAlpha