geeewhy

why i prefer invisible tools. screens are our environment right now. it feels like interior design of a casino these days. all the spinners and flowing streaming of text and media...

this is cool! i started tracking file changes across sessions with file hunk method on a binlog.. to see hot paths, or do partial reverts where files werent committed across my sessions. not for visual, but operational for the harness i use. approach lets you see the whole rollups on a period of days or minutes. think there are many use cases where you can run a side agent to check things / progress analyze risky areas as you go etc etcs .. all file change lookups are 3-5ms. script here: https://github.com/geeewhy/haicue-brew/tree/main/scripts

i wonder if i would be able to visualize with mindwalk

word for word why softwares like herdr, haicue, ampcode is getting adopted for ai tooling where it is hot, although just because its cli bound it doesnt mean you cant have elaborate almost-gui text interfaces... lynx is a good example from past.

ive beeen experimenting with this for a while, (im sure in a way, most of us did). Would be good to numerate some examples. When it comes to coding, here's a few:

- compile scripts that can grep / compile list of your relevant files as files of interest

- make temp symlinks in relevant repos to each other for documentation generation, pass each documentation collected from respective repos to to enable cross-repo ops to be performed atomically

- build scripts to copy schemas, db ddls, dtos, example records, api specs, contracts (still works better than MCP in most cases)

I found these steps not only help better output but also reduces cost greatly avoiding some "reasoning" hops. I'm sure practice can extend beyond coding.