You'll like this too then

https://github.com/mas-bandwidth/fixed3d -- port of box3d to fixed point :)

https://github.com/mas-bandwidth/fixed -- fixed point math library

Cool! I’d forgotten until now, but I had that exact idea back in the stone age, 10 or 15 years ago, and started working on it but got bogged down. It was clearly feasible but a huge amount of work, too much to justify the cost. So it’s a perfect job for coding agents now. Nice one!

I do you think now need to watch out for the opposite problem. These things become so easy to build that the temptation is just to go ahead and build. But unless you really do need them, all that new code just goes to waste. The cost to produce has become very low, but sometimes the value can end up being negative.

This is so true. At the end of the day you just have to have good taste to know what is worth creating.

You are right!

Big fan of RDF, your sexpr notes are hilarious https://github.com/mas-bandwidth/fixed/blob/main/docs/roadma...

What tooling do you have around this?

I have some stuff inside nova-sprint that uses lisp sexpr to store issues, roadmaps and various things as primary structures. Basically, anything that is free-form structured tree data it's a great fit.

And then the AIs can easily write tooling in lisp to manipulate these structures, and you can talk to them from some golang program in a verb like way, sort of like a redis client.

I was planning on doing this to effectively replace issues/PRs in git, and have my entire future work set that I import into sprints stored inside this lisp sexpr.

It's implemented in nova-sprint as a tracer bullet (search for "roadmap" scripts in lisp...), but I definitely see this as something I want to keep pushing harder on.

It's a really effective thing, storing all your work in a data structure, and then being able to manipulate that data structure. beats having to hammer the GitHub API when you ask questions like "OK so what else can we bring into the sprint now?"

=)

I totally agree, I have been moving to XML and custom formats inside of markdown. I only use github as a dumb datastore, keeping all issues, todos, etc inside the repo itself (where it belongs). Github should have made issues a branch of the repo.

Here is the roadmap tool that uses lisp sexp: https://github.com/mas-bandwidth/nova-roadmap

I find it really useful to track future work, and then bring it in the current session or sprint. It also regenerates nice roadmap tables in markdown that people can read like these ones:

https://github.com/mas-bandwidth/schema/blob/main/ROADMAP.md