One post tagged with "documentation"

For a long time, I've been documenting learnings, experiments, and half-baked ideas in my GitHub markdown journal. It served its purpose - a quick place to dump thoughts, code snippets, and technical notes. But raw markdown has limitations: hard to share specific bits, no visual formatting, difficult to navigate.

Now I'm moving to this blog-like format. Same rough thoughts, but rendered nicely so bits can be shared easily.

What This Enables​

For example, I can now write attention mechanisms like this:

Or visualize concepts with diagrams:

Or create interactive components like this:

I'll be migrating key learnings from the old journal and adding new thoughts as they manifest. Topics will range from technical deep-dives to half-formed ideas that might never get finished.

Over the years, I've realised that not publishing unfinished thoughts leads to a loss of the trail uncovered. Even though you didn't reach a destination, share thoughts so you can collect peer feedback and open more pathways ~ which is much better than loss of entropy. Preserve the journey and open up possibilities for feedback and collaboration.

So, the goal isn't perfection. It's continuous documentation in a format that's pleasant to read and easy to share.