My name is Mike Lockhart, and this is my web log. I am a senior support sysadmin and larval web hacker for a well known Australian Open Source web content management company. I do mainly Linux and Matrix work, and dabble in some other languages and projects in my Copious Free Time.
I'm also married for 19 years and we are parents to three boys aged between 5 and 12 years. We live in Tasmania, where we grew up, returning here from New South Wales, in late 2013. We all feel very lucky to be living here, with family close at hand and an awesome, friendly and welcoming community around us.
On the Net, I go by the handle sinewalker, and while after 20 years I think I've outgrown it, it's still a unique username in most places. A newer handle I'm adopting is milohax.
My ACIC background check is held at CVCheck.
What am I into?
A quick summary should give you a bit of an idea:
- Open Source Software
- Open Data Formats
- Open Architecture Computers
- Open Crown hats
- chili, coffee, whisky
- opera (well, arias)
(what? I have 3 kids...)
- hacking (old school)
- robotics, electronics, quad copters
- dad stuff
- emacs vs vi → emacs
- tabs vs spaces → spaces
- pirates vs ninjas → pirates
- manual vs automatic transmission → manual
- corded vs cordless power tools → corded
- Star Trek vs Star Wars → Star Wars
- BSG vs Bab5 → BSG (re-imagined)
- Windows vs macOS → macOS
- Linux vs macOS → Linux (openSUSE)
- iOS vs Android → droid
- Oreos Dunk vs Tim Tam Slam → Tim Tams
- Hershy Bar Cookies `N' Creme vs Nestlé Milkybar → Milkybar
- Coffee → black
- Tea → Earl Grey, hot
On this web site you will find posts, pages, pictures and code that are in connection with my interests. I try to keep the stuff here as general as possible — any work-specific writings live behind a company firewall. This means that what you see and read here is (or was ) my own opinion and does not necessarily reflect the opinions or directions of my employers (past, present or future).
A major reason for building my blog with a static web page generator is so that
I can have fine control over type-setting. While this site is mainly a personal
blog (and so informal), I use notational conventions throughout. These are
common enough in online technical writings for the computer field but weirdly
not well supported by systems such as Blogger or Wordpress (or Matrix) which you
must fight against to use. Computer keywords are typed inline
like this, terms
and variables are italicised like that and code blocks use Colour Syntax
Highlightng. At least for the newer posts since late 2015. I may go back and
tidy old migrated posts.
You will notice that the English on this site follows Commonwealth conventions of grammar and spelling. That's a natural consequence of where I live. You will also notice frequent spelling errors which are not attributable to Commonwealth English -- that's a consequence of Rule 9. I've also recently adopted the Oxford Comma for its clarity and consistency.
This is not a "web 2.0" site: there are no comments enabled here. No-one comments anyway, and it adds a lot to the site load time and bandwidth. There's not much point in costing visitors that overhead for something that isn't used.
Sensitive data may be emailed to me using my public key with fingerprint 3CCA2E6EBCBE8795 (keybase.io).
How this web site is made
Posts are typed using the Dvorak keyboard layout into Emacs on either an Apple PowerBook Mac, or a home made computer running openSUSE, usually on a Truly Ergonomic Computer Keyboard or a Sun Type 6 keyboard (grey version, with rearranged key caps).
Posts are generated from a mix of markup languages (typically
using the Nikola static web site and blog generator, and
published to GitHub Pages (via Nikola's
github_deploy command). The site is reachable via my own DNS, or the GitHub
Prose and image content of all articles are copyright, licensed under a Creative Commons Attribution-ShareAlike 4.0 License, unless otherwise specified. Code content are a mixture of Open Source-compatible licenses depending where it ultimately originates or is intended to be used. If it's inline then I usually consider it to be "prose", and if it's original to me then readers may infer that it is copyrighted and licensed in a spirit that is intended to be shared publicly with attribution.