Good Old Code

Earlier today I was thinking about how little of the software I've written since 1994 is still in use today. The oldest application that I know to be running was written back in 2006 while the oldest bits of code that I personally use were written somewhere around 20001. Nothing that I wrote in the 90s exists today and, even if it did, nobody would want to use it. Heck, very little of the code that anybody wrote in the 90s continues to exist today outside of some very legacy systems used within governments, militaries, nuclear power plants, and banks2. There's a good reason for this, too: software in the 90s was rough.

When I think about software from 25 years ago, Windows95 springs to mind. The promise of Microsoft's ambitious operating environment was attractive, but the implementation was incomplete. Applications would crash all the time3 and, because everything had to be "multimedia", we would need to have large binders of CDs next to the computer for all the resources that couldn't fit on the internal hard drive4. There is little chance that anybody would willingly choose to use Windows95 and a myriad of compatible software from the same time period today.

Or so I initially thought. Then I remembered how my friends and I would use computers when there weren't any adults around: Doom and Doom II.

Operating systems, operating environments, and productivity software from 25 years ago are probably best forgotten. Games, however, can have a much longer lifespan. I can actually say that I've run Doom II on a 386, a 486, a Pentium, a Pentium II, a Pentium III, a Pentium 4, an AMD Athlon XP, a Core2Duo, a 4th Generation Core i7, a 5th Generation Core i5, and a 9th Generation Core i75. 35 years of computer development for a game that was released in the autumn of 1994.

Silly as it might seem, I find it fascinating that of all the software that was written before Y2K, Doom and other games from the same era are likely the only examples of applications made for general consumption that have seen more than a quarter century of use.

Is there any chance that I might write an application that people enjoy using for a quarter century or more without updates? Probably not. Modern software is often more dependent on its operating system than applications written in the past. That said, who knows what the future might have in store. A well-written, self-contained tool for a Linux-based system might enjoy a longer operational life than something written for Windows or macOS.


  1. An example would be the NoNull() function found in 10C's /lib/functions.php. It was rewritten for PHP a decade ago to replicate a very useful task that I had picked up from an earlier time while developing VB6 applications that would read from a SQL Server database. NoNull() — and it's integer variant nullInt() — are "old" pieces of code that have remained largely unchanged in 20 years despite being re-written in several programming languages.

  2. There are bound to be a good bit of code within Unix that hasn't been updated in quite some time, too. Anything that isn't dependent on dates or very large numbers would have avoided Y2K and 64-bit updates.

  3. I switched from WordPerfect to Word in the late 90s simply because WordPerfect would literally crash after every page. I would save my documents after every paragraph. Word95 didn't have this issue and, if that wasn't reason enough to switch, Microsoft's word processor was faster and easier to understand. Believe it or not, it had fewer buttons than any of the competition.

  4. Remember when a single CD could hold almost twice as much data as a hard drive? Those were rough days.

  5. It was after the Athlon XP that I stopped upgrading my systems every 6 ~ 8 months, hence the gaps in processor generations. And, yes … I've played Doom II on a 2019-era MacBook Pro.

All For Me

Every so often I find myself wondering why it is that I put so much effort in at the day job. A great deal of what I do is not specifically requested. Instead I see what needs to be done within the organisation and begin working to solve the problem. A lot of times this means doing something that will go completely unnoticed, because it's only when something is noticed that the issue is raised. This is particularly true with a little textbook delivery system that I started writing about nine months ago that is slowly gaining traction within the organisation outside of Japan. Whispers are observed through various communications channels about things not quite being right or how an older textbook that is only used by a handful of students can't be found anywhere, and I jump into action and fill the gaps. People don't really notice the changes; they just focus on doing their job to the best of their ability with a more complete set of tools.

For the better part of three years, this has defined a good chunk of my efforts at the day job and every small improvement makes these systems a little bit better for the people using them. But why do this? Why give myself work? Why stay up past midnight solving problems that nobody has complained too loudly about?

As anyone who has worked with me might expect, I do it primarily for me.

In a perfect world, software would be "invisible". People would learn how to use the tools to complete a task, then never think about the system in a critical way ever again. Building software like this is hard. Really, really hard. And it's this challenge that I look forward to.

For the digital textbook system, my ultimate objective is to have every material we have distribution rights for in the database along with every audio and video file for that book. I would love it if a colleague looked for a text we haven't used in the classroom since the 90s and found the resource plus all of the audio files that were once only on cassette tape, or to see someone try to share these resources with a student who forgot their book with a couple of taps. All without thinking about the complexities that lie under the surface.

The goal, as unrealistic as it might be, is to make something that meets the Apple stereotype of "It just works". Corporate software needn't be ugly and unwieldy. Educational software needn't be sluggish and half-baked. People expect more from technology, as they should. So I build the tools that people will hopefully want to use for their everyday work and pay attention to the online water-cooler banter that might reveal the next task to accomplish.

Hopefully one day it will be possible to stand back and see that the effort put into the work has bore some impeccable fruit.

Get It Done

There has been a recurring message in some of the movies I've watched recently and it has me wondering if this is something I've subconsciously picked up on as a result of recent distractions at the day job. Over the past two weeks I've caught myself wondering whether the tasks being performed, while important, were the most important things that needed to be done. With schools across the globe shutting down on account of the COVID-19 issue, thousands of my colleagues are struggling to make the transition from working in a classroom to working in front of a camera. The tools are sub-optimal. The training was rushed. The hardware consistency has devolved to an unchecked BYOD1 mess. People are doing the best they can with what they have, but the tools! The tools ….

So I've been working on some of those issues in an effort to reduce some of the friction teachers are having when delivering their lessons over a video call. Based on the feedback, there's still a long way to go. However, despite the urgency that exists for this matter, there are other things of similar priority that have been sitting to the side for weeks while teams coordinate and confirm requirements for what is arguably one of the next "big" things for the company. Even without specific marching orders, there is nothing stopping me from jumping on some of the low-hanging fruit that needs to be done before the big tasks begin.

Would this be the better place to put my energy? On "the next thing" rather than "the current thing"? It's because of questions like this that we have managers who we can ask for guidance and clarity. Perhaps I should have done so.

Instead a full five days of work were used to resolve some issue that were preventing teachers across Japan and in some parts of Europe from delivering their classes online effectively and efficiently. In my mind, this was the higher priority; get teachers teaching and students practicing. The next thing officially kicks off its tight-deadline schedule this coming Wednesday, after all. Make sure the basic needs of the team are met, then use the rest of the time to fix things.

Sometimes I think this makes me a "poor member of the team" as I'm not seen worrying as much about something as others. Other times I think the lack of anxiety over some things2 is better for the people in the company who might not otherwise get a timely solution.


  1. Bring Your Own Device

  2. I have a lot of anxiety to begin with. I try to minimise taking on more.

Cabinets

Two years have passed since the family and I moved into our current home, meaning we’re now 1/15th of the way through paying the mortgage. One of the many things I’ve learned over these last 24 months is that a house is never “done”. There’s always something that needs attention. Whether it’s the yard or the cleaning or new appliances or some unexpected thing, there’s yet to be a time where I’ve been able to stand back and say “The house is done! … which has me wondering about the future as the house begins to deteriorate due to ageing and a teenaged boy being rough on everything.

One item that I’ve been considering as a near-future project is building a proper space for some servers. At the moment there are three servers in this house in three locations to reduce heat and sound. Ideally these would all be in the same cool location sharing a UPS1. To accomplish this, I’ve been considering a half-rack that could handle some mounted machines in the future. Given their size, it would need to be in my workspace — where Nozomi sleeps — and that means there will be fur to contend with. To handle the fur, some filters could be mounted to the sides of the rack, but this would also trap heat; a serious problem that results in the servers running incredibly hot without load during the summer months.

A first-world problem, for sure.

Another part of me wonders if it would be better to just get a bookshelf, like I have now, and have all the machines in there down in the workspace. A bookshelf would be much nicer to look at than a metal cage full of computers. More than this, the bookshelf would be cheaper, easier to repurpose in the future, and could hold some of the many, many, many notebooks I’ve written in and filled over the years. There would still be the matter of dog fur to contend with, but perhaps some filter sheets would look better on a piece of furniture than a brick-like metal cage.

The overarching goal is to have all the technology in a single, easy to reach location so that fewer wires are seen and fewer fingers can create problems. Maybe I’m just overthinking the issue.


  1. Uninterruptible Power Supply. This is basically a backup battery in the event of a power failure. There is one connected to the network equipment and the main web server, but it would be nice to have everything properly surge protected with enough juice to go four or five hours without main power. Right now everything is good for up to six thanks to an APC UPS in the closet.

An Indulgence I Could Do Without

Every day we spend a large portion of our time unconscious in bed. With a little practice I’ve managed to get down to a little over five hours a day during the week and about seven on weekends. However, even with 130 hours of active time per week, I feel I’m being lazy. There’s a great deal that can be done in the 38-odd hours that I’m asleep. Friends and family have suggested time and again that this “isn’t normal”, that people generally want — and should get — seven or eight hours of rest per day but, when the bulk of my time is spent in my head, why does the body need so much rest?

Sleep is quite enjoyable at times, of course. I rarely have issues falling asleep anymore, as the polyphasic sleep patterns have all but eliminated the insomnia that I have regularly struggled with. Waking up, however, is a terrible chore. The mind is foggy. Muscles are stiff. People are shouting. What an awful way to re-enter the world. If it were possible to go without sleep for days at a time and still be useful, then I’d give up the nightly block of rest in order to have a little more personal time and maybe relax a bit. So much of my waking day is spent doing things for others. Every so often I can do things for me, but not often enough. Being awake all night would also make it possible to escape the house for a proper walk through the neighbourhood while avoiding anyone that might be carrying a virus.

But this is almost impossible. While I can generally remain awake for 36~40 hours in a row and remain productive, the mental cost of doing so is excessive; I’m pretty much useless the following day, stuck in a perpetual mental fog.

Perhaps a better-tweaked sleep schedule would solve the problem of wanting more time while giving the mind enough unconscious time to stave off the insanity that arises with a lack of sleep.

Imprecision

Over the last couple of months I've noticed that my dexterity has become a lot less accurate when using the keyboard on the newer notebook from work. When the task is simply typing words, much like I'm doing right now, then everything is just fine. I can type at almost 200 words a minute1 with a minimal number of mistakes and everything keeps up just as it's expected to. However, as soon as I need to switch the hands up to start using the arrow keys or many of the special characters, things begin to go downhill. The cursor moves in the wrong direction or an @ appears where I expected a [, which is frustrating to say the least. While some of this could be attributed to stress-induced errors, the problem seems to be with the keyboard itself as the problem vanishes almost instantly when I grab my personal notebook, a 13" 2015-era MacBook Pro.

A first-world problem for sure, but one that can be solved relatively easily by using the older hardware which is still perfectly good for 95% of the tasks I ask of it.

Of course, being an inquisitive sort of person, I've tried to understand the why behind the problem. Answering this question might provide a workable solution, after all. So, having given it some thought, there are three main issues that I have when working with last year's MacBook Pro:

  1. The arrow keys are not an "upside-down T"
  2. The palm rejection on the oversized touchpad prevents characters from appearing on the screen
  3. The TouchBar is more a novelty than a productivity helper

Each of these issues have likely been covered ad nauseam by the tech bloggers of the world since 2016, so there's little point getting too deep into any of them, but it's important (for me) to consider how it is that an older machine can be more conducive to productivity despite the slower hardware, limited storage capacity, and cracked screen.

Pointers Need Not Apply

Mice are awful little peripherals. They force a person to take one hand off the keyboard and many are about as ergonomic as a cinderblock, which results in lost productivity at best and carpel tunnel at worst. I've seen a lot of people with white collar jobs become unable to use their computers after a decade or more at their desk because one hand is bent into the shape of their mouse and no longer has the dexterity required for hours of typing and clicking. This was something that I noticed back in the 90s and have abstained from using the things unless absolutely necessary. If the pointer is needed, then Lenovo's keyboard pointer — often referred to as "the nipple" — or Apple's touchpad are the only way to go2. Because there's no need to use a mouse, the hands can generally stay on the notebook at all times, allowing for keyboard shortcuts and quick pointer actions without losing focus or looking away from the screen. This is one of the reasons why the keyboard is a make-or-break decision for me when it comes time to research a new device. If the keyboard is illogical, then it doesn't matter how great the rest of the machine is, I won't want to use it.

On the 2019-era notebook from work, I find the keys are laid out just wrong enough that I'm often needing to take my eyes off the screen to look at where the fingers are resting, then correcting their position and getting back to work. This might not sound like a very serious issue and, in the grand scheme of things, maybe it's not. When you're taking your eyes off the screen to look at a keyboard several hundred times a day, though, frustrations can mount. Imagine a pianist having to look at their fingers every so often because the maker of their piano slightly tweaked the size and position of the keys to look a little nicer from a distance. It's illogical. The 2015-era notebook does not have this issue and I do not believe it's just because I've used that keyboard layout for the better part of 7 years.

Not Pointing

Palm rejection on the MacBooks I've used has generally been pretty good. We can have a good amount of our hand sitting on the touchpad without the pointer jumping all over the place and taking focus away from the application window we're working in. However, it seems that with the newer MacBook, if you have more than 5% of your palm on the oversized touchpad, anything you type will not appear on the screen until your hand is repositioned, which dumps the last sentence or two that you typed before recognising the problem onto the screen as though the system were lagging behind your typing speed.

This never happened on any previous MacBook I've used. Given that the vast majority of my day is working in text editors with code that refuses to compile if there's just one character out of place, having a keyboard appear non-responsive simply because the palm-rejection software is acting up isn't cool.

Hey, Siri? Go away, please.

The final item that bugs me about the newer keyboard is it's WatchOS-powered TouchBar. The fingerprint reader doesn't recognise my fingerprints for more than 3 days3, I hit the Siri button at times when quickly hitting backspace, and the escape key in the upper left corner isn't left enough. I can live with the little nuisances of not being able to quickly pause music or skip to the next track without at least three taps, but not having the intended keys operate in an expected manner is not at all conducive to efficiency.

So, with all this in mind, I'll try something odd next week. Rather than use the newer, incredibly powerful notebook, I'll switch back to the 2015-era 13" MacBook Pro and see if the keyboard itself makes up for the slower hardware. If so, then it may be time to investigate either buying an external keyboard for the newer machine or repurposing it.

Time will tell ….


  1. The fastest I've been able to measure myself is 193 words per minute on a 2019-era 15" MacBook Pro, which is pretty astounding given that "I type wrong".

  2. HP's notebooks had some pretty going touchpads when the Synaptics software was not installed, but they'd quickly discolour and look awful.

  3. This isn't necessarily a bad thing, though. Biometrics can be circumvented though coercion or severing of body parts. Passwords … well … they can be given up as a result of coercion or severing of body parts. If someone wants in to a computer bad enough, bad things might take place.

True Quiet

When the family and I moved to our current home almost two years ago one of the most noticeable differences between here and the previous neighbourhood was a distinct lack of noise. The sounds from traffic were distant and the thrum from industry was absent. After seven years at the relatively convenient apartment in Kasugai, we were now wholly ensconced in a suburban location complete with natural sound dampening in the form of hills, parks, and an ageing local population. Over time we started to notice a distinct lack of other forms of pollution as well. The air is cleaner most of the year1 and, because there are no pachinko parlours nearby, the night sky is often incredibly alluring with its hundreds of visible stars. I had wrongly believed that this sort of quiet calm would not be possible while living in a densely populated part of the country.

However, quite a bit has changed over the past month — and this week in particular — as people across the country have started to isolate themselves from neighbours.

It wasn't too long ago that when Nozomi and I would go out for our evening walk that we'd see dozens of planes flying overhead. Their running lights would signal their terrestrial origin and, if the aircraft was on a domestic flight plan, we'd hear the distant roar of the engines as the jets moved an incredible amount of air. The same, too, for cars. Our evening jaunts typically take place as people who work in the nearby cities are coming home. Every few minutes there would be a rush of five or six vehicles racing past the park to get home before dinner cooled. A pair of community busses would often pass by. Two or three delivery trucks would be seen performing their rounds. Each one of these vehicles creates a noticeable amount of noise, albeit not nearly as much as we learned to tune out with the previous home. However, with the government request that we practice "social distancing" and work from home if at all possible, public transit is forever running on their Sunday schedules and most vehicles are conspicuously absent from the roads. The last two days have seen more vehicles taken off the road as several prefectures across the country have declared a state of emergency, further reducing the need for people to travel to any of these locations. Today the governor of Aichi prefecture, where I live, also declared a state of emergency. While there is no legal requirement for people to stay in their homes, many people will abide by the government guidelines that we go outside only when it is necessary; a hard sell during the few weeks of gorgeous spring weather before the crushing humidity of summer sets in.

Now here we are. In a place that is utterly silent from the hustle and bustle that once constituted daily, suburban life.

While Nozomi and I were in the park for her evening walk we2 counted fewer than 3 cars and 2 aircraft in twenty minutes. The night sky has the same number of stars as before, but they seem less hurried without the visual distraction that comes from blinking attention-seekers. The mail hasn't come all week. Deliveries in the area are generally finished before sunset. More people are working from home and, oddly enough, kids are at home taking their school courses online. The people we do see outside keep to themselves for the most part, wear a mask, and seem to be walking more to stave off cabin fever than for the exercise. The neighbourhood is truly quiet. So much so, that conversations can be heard across hundreds of meters.

The last time I could appreciate this level of background noise was when I travelled to New Jersey for business two years ago. The time before that I was the morning after 3/11. Before that? I lived in an ocean-side apartment I could barely afford in Steveston, BC … right on the edge of Lulu Island. That was in 2004.

As more of the country isolates itself in order to reduce the risk of contracting the Wuhan Virus, COVID-19, I wonder how much quieter the area will become and for how long. This will not be "the new normal" by any stretch of the imagination.


  1. We do still get the "yellow dust" from the Gobi Desert every spring. Gone is the black dust from factories and highway traffic, though.

  2. By "we" I mean "I", as Nozomi cannot count … to the best of my knowledge.

Seven Hundred Episodes

Paul van Dyk has recently put out his 700th episode of his Vonyc Sessions show and, as with the 699 episodes that came before, it's an enjoyable compilation of uplifting house and trance music. Earlier today, while out walking with the headphones on, I was trying to remember when I started listening to these shows. Oddly enough, the memory escapes me.

The first time I remember listening to something from Paul van Dyk was in Vancouver while playing Need for Speed: Underground 2, racing a souped up Mazda MX-5 around the track. This would have been somewhere around 2004 or 2005 when I had the time to spend an entire afternoon playing video games. Nothing But You was on the soundtrack and it was just an excellent piece of music to enjoy while driving well above the speed limit down crowded highways while racing the clock. A little while later I bought his Reflections album and have been hooked ever since.

The Vonyc Sessions radio program, however, has not always been available as a podcast. Initially this was made available as a 30-minute sampler on iTunes for $5 every month, and I picked up every album as they came out until they suddenly stopped during the summer of 2010. A quick search online let me know that the iTunes releases were dropped in favour of a 30-minute weekly podcast. Not only could I listen to new shows more often, but I could listen to them for free! Who could argue with a deal like this?

Over time the show expanded to be an hour long every week with special episodes every so often that could be two, three, or four hours in length. As time went on and he released new albums, I'd pick them up on or very close to release day not only because I wanted to support his efforts, but because his music has a genuinely positive feel to it that (almost) always brings a smile to my face no matter how hard the day might be.

It's not often that a subscription to a music podcast exceeds three years for me but I've yet to unsubscribe from Vonyc Sessions in the decade that it's been online. Hopefully it keeps going until the day that Paul chooses to hang up the headphones one last time.

Here's Something Cool

𐑩𐑮𐑤𐑰𐑩𐑮 𐑑𐑩𐑛e 𐑭𐑘 𐑢𐑩𐑟 𐑦𐑯𐑑𐑮𐑩𐑛𐑵𐑕𐑑 — 𐑷𐑮 𐑐𐑩𐑮𐑣𐑨𐑐𐑕 𐑮𐑰𐑦𐑯𐑑𐑮𐑩𐑛𐑵𐑕𐑑 — 𐑑𐑵 𐑞𐑩 𐑖𐑪𐑝𐑾𐑯 𐑨𐑤𐑓𐑩𐑚𐑧𐑑 𐑢𐑦𐑑𐑖 𐑦𐑟 𐑨𐑯 𐑪𐑤𐑑𐑩𐑮𐑯𐑩𐑑𐑦𐑝 𐑑𐑵 𐑞𐑩 𐑕𐑑𐑨𐑯𐑛𐑩𐑮𐑛 𐑦𐑙𐑜𐑤𐑦𐑖 𐑨𐑤𐑓𐑩𐑚𐑧𐑑 𐑞𐑨𐑑 𐑣𐑨𐑟 𐑚𐑦𐑯 𐑦𐑯 𐑘𐑵𐑕 𐑓𐑷𐑮 𐑒𐑢𐑭𐑘𐑑 𐑕𐑩𐑥 𐑑𐑭𐑘𐑥 𐑞𐑩 𐑒𐑧𐑮𐑦𐑒𐑑𐑩𐑮 𐑕𐑧𐑑 𐑢𐑩𐑟 𐑒𐑮𐑰𐑱𐑑𐑩𐑛 𐑚𐑭𐑘 𐑒𐑦𐑙𐑟𐑤𐑰 𐑮𐑧𐑛 𐑦𐑯 𐑞𐑩 𐑥𐑦𐑛 20th 𐑕𐑧𐑯𐑑𐑖𐑩𐑮𐑰 𐑨𐑯𐑛 𐑦𐑟 phonemic 𐑦𐑯 𐑯𐑱𐑑𐑖𐑩𐑮 𐑥𐑰𐑯𐑦𐑙 𐑞𐑨𐑑 𐑤𐑧𐑑𐑩𐑮𐑟 𐑮𐑧𐑐𐑮𐑩𐑟𐑧𐑯𐑑 𐑩 𐑒𐑤𐑨𐑕 𐑩𐑝 𐑕𐑭𐑢𐑯𐑛𐑟 𐑞𐑦𐑕 𐑦𐑟 𐑒𐑢𐑭𐑘𐑑 𐑩 𐑚𐑦𐑑 𐑛𐑦𐑓𐑩𐑮𐑩𐑯𐑑 𐑓𐑮𐑩𐑥 𐑣𐑭𐑢 𐑞𐑩 𐑨𐑤𐑓𐑩𐑚𐑧𐑑 𐑦𐑟 𐑘𐑵𐑟𐑛 𐑓𐑷𐑮 𐑦𐑙𐑜𐑤𐑦𐑖 𐑨𐑯𐑛 𐑦𐑟 𐑒𐑤𐑴𐑕𐑩𐑮 𐑑𐑵 𐑣𐑭𐑢 𐑞𐑩 𐑛𐑠𐑨𐑐𐑩𐑯𐑰𐑟 hiragana 𐑨𐑯𐑛 katakana 𐑒𐑧𐑮𐑦𐑒𐑑𐑩𐑮 𐑕𐑧𐑑𐑕 𐑢𐑩𐑮𐑒 𐑞𐑴 𐑞𐑴𐑟 𐑭𐑮 𐑒𐑤𐑦𐑮𐑤𐑰 𐑓𐑩𐑯𐑧𐑑𐑦𐑒 𐑦𐑯 𐑯𐑱𐑑𐑖𐑩𐑮 𐑨𐑓𐑑𐑩𐑮 𐑮𐑧𐑛𐑦𐑙 𐑔𐑮𐑵 𐑕𐑩𐑥 𐑩𐑝 𐑞𐑩 𐑤𐑦𐑑𐑩𐑮𐑩𐑑𐑖𐑩𐑮 𐑭𐑯 𐑞𐑩 𐑖𐑪𐑝𐑾𐑯 𐑨𐑤𐑓𐑩𐑚𐑧𐑑 𐑭𐑘 𐑥𐑩𐑕𐑑 𐑩𐑛𐑥𐑦𐑑 𐑞𐑨𐑑 𐑦𐑑 𐑢𐑫𐑛 𐑚𐑰 𐑨𐑯 𐑦𐑯𐑑𐑮𐑩𐑕𐑑𐑦𐑙 𐑔𐑦𐑙 𐑑𐑵 𐑤𐑩𐑮𐑯 𐑢𐑦𐑑𐑖 𐑦𐑟 𐑢𐑭𐑘 𐑭𐑘 𐑐𐑤𐑨𐑯 𐑭𐑯 𐑦𐑯𐑝𐑧𐑕𐑑𐑦𐑙 𐑕𐑩𐑥 𐑑𐑭𐑘𐑥 𐑑𐑵 𐑛𐑵 𐑛𐑠𐑩𐑕𐑑 𐑞𐑨𐑑.

𐑴𐑝𐑩𐑮 𐑞𐑩 𐑘𐑦𐑮𐑟 𐑭𐑘 𐑣𐑨𐑝 𐑤𐑩𐑮𐑯𐑛 𐑑𐑵 𐑮𐑧𐑛 𐑮𐑩𐑖𐑩𐑯 𐑒𐑪𐑮𐑰𐑩𐑯 𐑛𐑠𐑨𐑐𐑩𐑯𐑰𐑟 𐑨𐑮𐑩𐑚𐑦𐑒 𐑨𐑯𐑛 𐑰𐑝𐑩𐑯 𐑕𐑩𐑥 𐑩𐑝 𐑞𐑩 𐑣𐑰𐑚𐑮𐑵 𐑒𐑧𐑮𐑦𐑒𐑑𐑩𐑮 𐑕𐑧𐑑𐑕 𐑮𐑭𐑘𐑑𐑦𐑙 𐑕𐑦𐑕𐑑𐑩𐑥𐑟 𐑭𐑮 𐑦𐑯𐑒𐑮𐑧𐑛𐑩𐑚𐑤𐑰 𐑦𐑯𐑑𐑮𐑩𐑕𐑑𐑦𐑙 𐑨𐑯𐑛 𐑪𐑓𐑩𐑯 𐑣𐑨𐑝 𐑣𐑦𐑕𐑑𐑩𐑮𐑰𐑟 𐑞𐑨𐑑 𐑭𐑮 𐑨𐑟 𐑮𐑦𐑑𐑖 𐑨𐑟 𐑞𐑩 𐑤𐑨𐑙𐑜𐑢𐑩𐑛𐑠 𐑞e 𐑮𐑧𐑐𐑮𐑩𐑟𐑧𐑯𐑑 𐑖𐑪𐑝𐑾𐑯 𐑢𐑩𐑟 𐑒𐑮𐑰𐑱𐑑𐑩𐑛 𐑨𐑟 𐑩 𐑥𐑰𐑯𐑟 𐑑𐑵 𐑐𐑮𐑩𐑝𐑭𐑘𐑛 𐑩 𐑕𐑦𐑥𐑐𐑩𐑤 𐑓𐑩𐑯𐑧𐑑𐑦𐑒 𐑪𐑮𐑔𐑭𐑜𐑮𐑩𐑓𐑰 𐑓𐑷𐑮 𐑞𐑩 𐑦𐑙𐑜𐑤𐑦𐑖 𐑤𐑨𐑙𐑜𐑢𐑩𐑛𐑠 𐑢𐑦𐑔 𐑞𐑩 𐑜𐑴𐑤 𐑩𐑝 𐑩𐑤𐑦𐑥𐑩𐑯𐑱𐑑𐑦𐑙 𐑞𐑩 𐑑𐑖𐑨𐑤𐑩𐑯𐑛𐑠𐑩𐑟 𐑩𐑝 𐑒𐑩𐑯𐑝𐑧𐑯𐑖𐑩𐑯𐑩𐑤 𐑕𐑐𐑧𐑤𐑦𐑙 𐑨𐑟 𐑧𐑯𐑰𐑢𐑩𐑯 𐑣𐑵 𐑣𐑨𐑟 𐑕𐑐𐑧𐑯𐑑 𐑩 𐑒𐑩𐑐𐑩𐑤 𐑩𐑝 𐑥𐑩𐑯𐑔𐑕 𐑪𐑯𐑤𐑭𐑘𐑯 𐑢𐑦𐑤 𐑩𐑑𐑧𐑕𐑑 𐑒𐑩𐑮𐑧𐑒𐑑 𐑕𐑐𐑧𐑤𐑦𐑙 𐑦𐑟 𐑒𐑤𐑦𐑮𐑤𐑰 𐑩 𐑑𐑖𐑨𐑤𐑩𐑯𐑛𐑠 𐑓𐑷𐑮 𐑥𐑧𐑯𐑰 𐑐𐑰𐑐𐑩𐑤.

𐑢𐑭𐑘𐑤 𐑓𐑭𐑯𐑑 𐑕𐑩𐑐𐑷𐑮𐑑 𐑓𐑷𐑮 𐑞𐑩 𐑖𐑪𐑝𐑾𐑯 𐑨𐑤𐑓𐑩𐑚𐑧𐑑 𐑦𐑟 𐑤𐑦𐑥𐑩𐑑𐑩𐑛 𐑦𐑑 𐑣𐑨𐑟 𐑚𐑦𐑯 𐑐𐑭𐑮𐑑 𐑩𐑝 𐑘𐑵𐑯𐑩𐑒𐑴𐑛 𐑕𐑦𐑯𐑕 2003 𐑞𐑦𐑕 𐑥𐑰𐑯𐑟 𐑞𐑨𐑑 𐑕𐑩𐑥 𐑩𐑝 𐑞𐑩 𐑥𐑷𐑮 𐑒𐑩𐑥𐑐𐑤𐑰𐑑 𐑓𐑭𐑯𐑑𐑕 𐑘𐑵𐑟𐑛 𐑚𐑭𐑘 𐑭𐑐𐑩𐑮𐑱𐑑𐑦𐑙 𐑕𐑦𐑕𐑑𐑩𐑥𐑟 𐑢𐑦𐑤 𐑖𐑴 𐑞𐑩 𐑒𐑨𐑮𐑦𐑒𐑑𐑩𐑮𐑟 𐑦𐑯 𐑩 𐑮𐑰𐑛𐑩𐑚𐑩𐑤 𐑥𐑨𐑯𐑩𐑮 𐑐𐑩𐑮𐑣𐑨𐑐𐑕 𐑢𐑩𐑯 𐑛𐑱 𐑦𐑑 𐑢𐑦𐑤 𐑕𐑰 𐑩 𐑤𐑦𐑑𐑩𐑤 𐑥𐑷𐑮 𐑩𐑛𐑭𐑐𐑖𐑩𐑯 𐑨𐑟 𐑢𐑰 𐑒𐑩𐑯𐑑𐑦𐑯𐑘𐑵 𐑑𐑵 𐑥𐑵𐑝 𐑥𐑷𐑮 𐑩𐑝 𐑭𐑢𐑩𐑮 𐑒𐑩𐑥𐑘𐑵𐑯𐑩𐑒𐑱𐑖𐑩𐑯 𐑪𐑯𐑤𐑭𐑘𐑯 𐑢𐑧𐑮 𐑕𐑐𐑧𐑤𐑦𐑙 𐑒𐑩𐑯𐑑𐑦𐑯𐑘𐑵𐑟 𐑑𐑵 𐑐𐑤𐑱 𐑨𐑯 𐑦𐑥𐑐𐑷𐑮𐑑𐑩𐑯𐑑 𐑮𐑴𐑤.

Standard English Version

Earlier today I was introduced — or perhaps reintroduced — to the Shavian alphabet, which is an alternative to the standard English alphabet that has been in use for quite some time. The character set was created by Kingsley Read in the mid-20th century and is phonemic in nature, meaning that letters represent a class of sounds. This is quite a bit different from how the alphabet is used for English and is closer to how the Japanese Hiragana and Katakana character sets work, though those are clearly phonetic in nature. After reading through some of the literature on the Shavian alphabet, I must admit that it would be an interesting thing to learn … which is why I plan on investing some time to do just that.

Over the years I have learned to read Russian, Korean, Japanese, Arabic, and even some of the Hebrew character sets. Writing systems are incredibly interesting and often have histories that are as rich as the language they represent. Shavian was created as a means to provide a simple, phonetic orthography for the English language with the goal of eliminating the challenges of conventional spelling. As anyone who has spent a couple of months online will attest, correct spelling is clearly a challenge for many people.

While font support for the Shavian alphabet is limited, it has been part of Unicode since 2003. This means that some of the more complete fonts used by operating systems will show the characters in a readable manner. Perhaps one day it will see a little more adoption as we continue to move more of our communication online, where spelling continues to play an important role.

Finger-Waggers

A lot of people seem to have put the time once spent on commuting to the day job to new use in finding things to finger-wag about. Websites that were once fun places to visit to read about current events or technology news have devolved into editorials where authors stand on soap boxes to point out every fault and failure made by someone else, as though their sense of moral superiority and tunnel-visioned hindsight provides the necessary shield to deflect any examination of any decisions they've made over the course of their lifetime. Nobody and nothing is safe from these public admonitions and heaven forbid the author has more than a few hundred fellow finger-waggers to propagate the message in the hopes of "going viral" during this COVID-tainted year.

The implication contained in many of these rushed soliloquies is clear: despite all the good that has been witnessed over the course of 2020, everything is bad.

While it's incredibly unlikely, I do hope that people quickly tire of spending their days finding fault in the efforts of others and instead aim to improve things through cooperation and collaboration. Anyone can point out what's wrong with something, but this is rarely useful. Offering potential solutions, however, can sometimes lead to a world-changing transformation.