601 karma · joined September 3, 2013
bobbbygrayson[at]gmail.com, bsky.app/profile/@bobbby.online
I see some issues in the map display I would like to fix.
It wouldn’t be hard to make a skill that went through and did this at a basic level if you have a good healthy and well organized git history (most people don’t)
There is already tooling to link commits to nodes and re author chains so you could tell it to explore and start making this.
I might do an experiment trying this with an existing project in the OSS ecosystem tonight, sounds fun
http://notactuallytreyanastasio.github.io/deciduous/story.ht...
There is also a living graph of the entire development lifecycle thus far here
http://notactuallytreyanastasio.github.io/deciduous/demo/
I began the project 12 days ago, so this is all very fresh. I extracted it from another tool I built after building it to help me build that tool.
http://notactuallytreyanastasio.github.io/deciduous/story.ht...
the time-relevant stuff is all well beyond anything it does. It keeps confidence weights and decision paths and can analyze those.
I've also been using it at work with pretty great success.
It's a way of working/tools for working with an LLM that allow you to track decision tree graphs, have the robot make more informed decisions and build its own logical chain for history keeping, and modeling all the work as a DAG of events, goals, outcomes, decisions, and observations that network together to allow you to work better/smarter/faster, giving it a living and recorded memory and ways to explore all this.
It's easiest to check out the short demo on the site.
It also links to the live graph of how the tool has built itself.
tl;dr: browse all the choices/logical flows an LLM made. Come back from compaction better. Ask questions about the why of some code and get better insights to work with and around it. Also: really great PR review cycles enabled by having the graph around.
The site goes a bit into the how and why.
If you want to see the live graph of how deciduous made choices while building itself, check out this link
https://notactuallytreyanastasio.github.io/deciduous/demo/
For examples of some code and PRs deciduous wrote up, check out
https://github.com/notactuallytreyanastasio/deciduous/pulls?...
Feedback has been good has quality of work solid using it with my coworkers so far. Would love to hear more thoughts.
I've been working on this maybe 3 days. There are/will be more bugs.
There are a lot of opportunities here that could be levered to offer much better experiences and fundamental control and long term viability if they continue to execute this way.
I can't seem to authenticate because it had a localhost URL in the address when I was first authenticating. Now my work laptop has blocked the site completely to sign in or anything at all due to the activity of rapidly trying to bypass a site with no certificate because of that pass-on or something. Bummer, this computer has some more juice vs mine!
Might be an issue with "Sign In With Apple" if no one else has reported.
This is the link I got
https://omnara.com/cli-auth?callback=http%3A//localhost%3A58...
If they don't address this reasonably, it will be a very bad image for their brand! It is a simple problem, and an honest mistake that functionally should cost them nothing.
My customer service experience with them has sometimes required turnaround time, but never been helpful or unreasonable.
At work, we use both Windsurf and Cursor. At home, I also use Claude Code.
> Have you used tidewave.ai?
My coworkers have and are impressed, I can't speak to it.
> What use-cases have LLMs shined in for you?
Well, I managed to literally have it do all my work for 3 weeks. I didn't write a single line of code. That was pretty cool. I didn't even cherry-pick work best for the LLM. It was my normal flow.
I also use Claude code as an interactive tutor. I will have it implement something, break it into logical commits, then in each one break a few pieces and write tests for them and have me learn by fixing the broken tests.
I sometimes have different thoughts of approach than Zach, but this post really resonates with me. I've been in Elixir full time for over 10 years and would love to see an evolution in its adoption fueled by this.
Overall, I'm wildly impressed at how this Elixir code held up, and it was a joy to revisit this.