The pattern I notice more frequently at work now is:
"I'm working on X problem, I tried Y solution, AI thinks Z is wrong and W could be better, human opinion?"
This way there's never space for ambiguity, you showed you did your homework to the best of your extent, you already asked AI, all that's left is explicit request for human input.
It works quite well, and I appreciate it from both ends, as it saves everyone time.
I do this all the time in Emacs, which runs on an old computer and handles it quickly. None of the tasks on this list require significant CPU resources.
I actually think these constraints _help_ the average project as well. By enforcing remote builds and execution you completely remove the need for something like docker. You also get cloud backups for your code automatically.
Honestly the simplest option is sometimes the answer. Google docs...
It meets all your requirements. Markdown interop is very good. Always backed up and in sync. Supports offline access. Really easy to export everything if you really need to.
Google Docs doesn't do classic "wiki" things like bi-directional linking. Search, ironically, is also a bit of a mess.
Google Docs was built as a MS Word competitor and that's what it does best. I love Google Docs and I use it every day, but this is one thing I wouldn't use it for.
With JJ I sometimes make a 'jj new a b c' to work on top of multiple changes. Then as I tweak things 'jj absorb' to automatically patch the right changes.
reply