I abandoned an entire project. from can-lang to canlang. that removal of the dash means a world of difference. Before I had a General Purpose Language. But I realized that a Domain Specific Language could be a better market fit if you specify the target audience well enough.

One of the most satisfying things in programming is when you find a simplification pattern without changing the behavior at all... it turns out that the Can-lang linter DID NOT warn the user when there is a overtly convoluted piece of code that can be simplified. Soon it will.

Removed the entire legacy OAUTH hack that dominated the forgejo seams. Because what I've done now is forked forgejo to make it extendible instead. And called it fountain. Now authentication will become a first class forgejo primitive for soda OS pages. Instead of some crazy hack.

sodaos.dev We did a full redesign

Soda OS takes an issue, runs your AI CLI on your own server and opens a PR. then it runs the review... and sends the findings back for fixes. up to the limit you set. the whole thing runs in a terminal inside your repo page. you can actually see what it's doing.

Me: "Make sure that we use API from upstream" Astra: "A specific API endpoint isn't available upstream, hmm, and the user only approved API usage from upstream" ... Also Astra: "Well I guess I just have to fork and build upstream myself."

The first thing I asked Astra. me: "Please clean up all the issues that is superseded by issue X"; Astra: "sure" Astra ended up placing a comment on all those issues that they are superseded by issue X... AGI? I don't think so