Articles in Git

The Problem#

One thing blogs are bad at is storing posts that evolve over time. For example, if an article or manual is being written and developed, readers only see the first publication — further edits don’t make it into RSS feeds and no emails are sent.

But there is a solution!

GitHub as a Solution#

I wouldn’t call myself a prolific writer of useful manuals, but I am a big fan of conceptual solutions to small problems. So I invite the small audience of this microblog to test the “living posts” publishing feature with me on GitHub. We’re all tech people here, right?

An Example of an Article for “Lifelong” Additions#

At some point I caught myself thinking that not all people — even those with a substantial shared background (such as work, education, and common interests) — actually share a large common context. Simply put, not everyone knows what you know. At the everyday level that’s not such a big deal — so someone hasn’t read The Golden Calf, fine — but at the work level you expect engineers to be aware of certain significant, noteworthy notes/publications/know-how, and it turns out they’re not. That’s why I started a simple (and still very short) list called “Must Read”, and I want to collect genuinely worthwhile pieces of information there. If you have time and know how to make pull requests — join in — I’d love to hear your recommendations. And if you don’t know how or just can’t be bothered — join in the comments (:

### The must-read article has moved Links updated in 2024

Credits#

Inspired by an old discussion with Tivasyk.

Update from 2024#

Unfortunately, Tivasyk’s blog has since been abandoned by its author, and the domain has been taken over by some Belarusian casino; even the local hosting is unreachable.

comments powered by Disqus