I've built a couple for myself so far; the most recent is in zig (sqlite extension that treats markdown files / frontmatter as virtual tables) and it's lasted me. I plan to rewrite it soon to adapt to how I've been using it :)
This was the first time I bought a font, and -- surprisingly -- I haven't regretted it at all. Every time I look at my terminal there's always a little bit of happiness at how elegant the font looks.
Heh, definitely depends on the software itself but I generally find the contents /schema of tables used to save the data very illuminating: you can see the UX, whatever form it takes -- and then what is saved to the backend so it makes things slightly more understandable for me.
I've been writing here sporadically for more than 10 years at this point, at ~1 post a year. The more recent posts took months to write, and tend to cover things I find myself repeating frequently while working with other engineers.
> "you don't have to code all parts of your design".
That's an excellent articulation of what I think as "invisible seams" when I write code: they're soft points of extensions that don't need a separate interface/function/class _yet_. Sometimes I just mark them for myself with an extra newline within a function.
As much as I enjoy writing to think, simply writing doesn't lead to reality testing -- I've found even greater clarity by trying to add numbers or simulations and trying to program around what I'm writing. Writing with real data intertwined and numbers applied is much better.
- kinopio (web/mobile) kinopio.club
Works well, but has a strong, quirky personality which sometimes gets annoying for me; I prefer the minimalism of scapple.
- draw.io / diagrams.net
You can configure it to hide most of the toolbars and then just use it as mind mapping software, this is what I'm trying at the moment.
I haven't yet cleaned up the slipbox code enough to publish it, but I do have my site generation code public: https://explog.in/config.html -- which does something similar but doesn't generate the cross links.
The slipbox code is just a bunch of python to pre-process the org files and "fix" links, which then passes them on to emacs subprocesses to generate html.
I use logseq to take study notes in org mode, which are then published to my public slipbox by post-processing with emacs in a github action. The consistent part of this has been plain text notes -- the slipbox has stuck for the past year, and hopefully will continue.
I built https://github.com/kunalb/panopticon to export perfetto/chrome compatible traces and also draw arrows between async functions. (I think the arrows are only supported in about://tracing though).
The readme at https://github.com/kunalb/termdex/tree/main/markdown_files is probably the best bit.