This is my personal blog where I write about life, technology, and the Universe and all the things in between that pique my interest. All views are strictly my own. I started it in 2003 and it’s been more or less (mostly less) active since then. It also saw moving itself from WordPress to Tumblr, to Hugo backed by a static GitHub repository1 with posts written in good old Markdown2 and now Substack.
You can reach me at johann [at] mycvs.org. Content is licensed under a Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) license.
Why mycvs.org, you might wonder? As a student, I had, from an early time on, used LaTeX to typeset all my paperwork, including my diploma thesis. For the management of this code, I’d used what was the top-notch versioning system at that time: CVS, short for “Concurrent Versions System”. In fact, my whole (written) existence as a student depended on a functioning, stable revision control of these precious ‘LaTeX’ source files, and so did a project I worked on with Ölbaum during an internship where we developed software together. Unimaginative as I was, I thus settled to use “my CVS” as the theme and moniker. And a .org TLD was, at the time, the most affordable option besides the not appropriate .com. After an early attempt to find a new domain name failed miserably, my digital home was kind of settled. Henceforth, my online presence has mainly revolved around that domain. In a curious and ironic twist of life, my website now goes back to its roots, being hosted in a Git repository: “Take Concurrent Versions System (CVS) as an example of what not to do; if in doubt, make the exact opposite decision.” ( Tech Talk: Linus Torvalds on git - YouTube)
I’d always used some form of Markdown over the years, even in Tumblr, it could be used (Yet it was routinely messed-up with when the mobile client was used, or by transforming between one or the other platform). To move the site to Hugo, I used the excellent tumblr2markdown, pandoc as well as some cleaning-up with sed. For the move to Substack, I depended on the RSS Import feature, which worked surprisingly well for the posts but obviously failed miserably for the internal links.
