I just attempted to resolve a minor merge conflict via the GitHub web ui for merge resolution. The resolution commit deleted the whole file. This file is present in both commits, and I accepted incoming changes for both. This should never happen.
pi is cool, but it's hard to beat zed with codex via acp in guardian review mode. zed's vim mode is close enough to home where I can be comfortable now.
@mitchellh@ellie_huxtable I was waiting for the day where someone built a multiplexer on ghostty! I have a pretty advanced tmux configuration if you are looking for deeper insights. These are things which aren't worth implementing in the product, but may help with the design thinking.
AI still makes dumb mistakes like not seeding nonces and cryptographic keys properly. The code for these kinds of things always looks good on the surface, but the hidden mistake is very dangerous. Review every line it produces.
@shadcn It's because half of these projects don't even fit into the XDG standards anymore. They shove config, state, and sometimes even credentials all into the same file.
Can't even store some of my newer configs in my dotfiles repo because they would leak sensitive info.
The main feature keeping me on codex has been auto-reviews, which were experimental up until very recently. I did a quick and dirty port of the feature to pi: https://t.co/fUWrHjOQyG
I'll be using this to go back to a less agentic way of working in nvim: https://t.co/1993gJqJAu
Sometimes plan mode can be overkill, which is why I built a "clarify" skill. Functionally does the same thing, but without the rigid format.
I have been experimenting with bringing the same principles to spec driven development, kind of like memory, but more product focused.
@mitchellh Looking forward to trying this out!
A while back I switched over to custom base16 highlighting in vim to keep my ghostty & vim themes cohesive. It would have been nice to have one or two more colors, and soon I can!
@gordon_cassie@maddada@jarredsumner Sounds like a carefully written skill might be able to help. This is something I'd rather do by hand though personally.
@gordon_cassie@maddada@jarredsumner Interesting, I haven’t tried giving an LLM any conflicts yet.
I wonder if giving it the jj diff output for each change it needs to make resolutions in would help. The beauty of jj is that you can edit the files directly to resolve the conflicts.
I’ve been having quite a bit of fun experimenting with @TauriApps lately.
There are some pretty powerful use cases I’ve been exploring that aren’t well documented yet.
@gordon_cassie@maddada@jarredsumner That is my one gripe, but jj has been mainstay of my workflow longer than any agentic tool. The jj cli is the best vcs experience I’ve seen. I abandoned my own git worktree plugin a couple of years ago for jj. I also don’t trust the llm to manage versioning… maybe I will one day
@thdxr@martin_casado@pvncher@leerob From what I've seen in the next generation of students entering the space, they are less scared and more motivated than a few years ago. Thanks for sharing this list