#marcin wichary

Work made by me, Marcin Wichary (outside of this blog) / 18 posts

Newsletter
  • Get a newsletter digest every Friday:
Contact

Send me feedback, tips, bug reports, and anything else:

About me and the blog

My name is Marcin Wichary (he/him). I’ve worked as a UX designer, typographer, front-end person, and manager at Google, Medium, and Figma. I’ve also written a book about keyboards and typing, gave talks, and published essays about design, typography, and technology.

Unsung is my blog about software craft and quality.

More info about Unsung

Send me feedback, tips, bug reports, and anything else:

More info about Unsung

“A few keys worth knowing”

When I was redesigning Figma’s keyboard panel in 2018, I introduced a special first tab called Essential. It’s still there today, very similar to what it was back then:

The notion was for this panel to be a welcome committee for people who don’t use keyboard shortcuts at all, a nice onramp before the avalanche of all the other shortcuts. The panel tried to say “These are the best three shortcuts we have. You might find them useful, maybe rewarding, maybe fun. If we did our job well, they will make you feel awesome. Maybe you’ll get hooked on these, then the others.”

I didn’t invent this idea, although I do not remember where I stole it from. But I added – or, remixed – a few things. The panel was at the bottom so you could actually try these shortcuts when looking at them. There was also an animation that played whenever you pressed them, both feedback for you and light “gamification” so that perhaps you were more inclined to “complete” the entire the panel:

(Today, I’d steal this idea from Linear, too.)

Since then, it has always warmed my heart to see a version of “essential shortcuts” elsewhere. Here it is in Arc:

The first one teaches you that Arc’s “new tab” is a richer experience than you might expect, the next three are bona fide crowd (and motor memory) pleasers, and the last one is Arc’s unique invention.

(If I had one design note, it would be that the last two shortcuts feel kind of complicated – anything with two modifier keys starts getting tricky. I also believe ⌃⇧= could be presented as ⌃⇧+ for a better mnemonic.)

And, I also just spotted a similar thing in a new terminal app called Rex:

Both Arc’s and Rex’s panels are better than Figma’s in the sense that they show the shortcuts as part of first-run onboarding, without you having to even ask.

Needless to say, I like this “essential keyboard shortcuts” pattern a lot. Let me know if you see it elsewhere!

When fonts fall

…is an essay I wrote in 2020 about font fallback and all these mysterious “missing character” characters like �.

If you are curious, too, you might find it interesting! It was fun researching this, and I ended up going in unexpected directions, including emoji and “Unicode fonts.” The essay pairs nicely with text.makeup, as that’s the tool that can help you investigate a suspicious string to see what exactly happened.

(The writing is on Figma’s blog, but it doesn’t talk about Figma-specific typography – as a matter of fact, it’s deliberately kept universal, with Figma behaviour only mentioned in one sentence.)

Pac-Man’s siren call

It’s the last day of Halloween Week on Unsung, where we’re sharing scary, spooky, and creepy stories. This is a story of how my bug scared others.

In 2010, Google’s homepage celebrated various occasions with reimaginings of its own logo called doodles, but we wanted to do something extra special for Pac-Man’s upcoming 30th anniversary – and through a set of circumstances that began with me randomly sitting in the cubicle right next to the doodle team, I was asked to write the code.

It was, frankly, a terrifying proposition. The homepage was then a very important destination, and my job title was only adjacent to “software engineer.” But I started researching the game and recreating it all in HTML and CSS, not dissimilarly to the iPod Apple just put on their pages to celebrate a different anniversary.

(The research was tricky because we didn’t want to reach out to Namco for help too soon, instead planning to wow them with a close-to-finished doodle. Luckily, some nerds on the internet researched Pac-Man intensely, so I could stand on their pixellated shoulders.)

It was important for me to stay truthful to the original game, with only some very deliberate exceptions – the price of entry was the playfield having to resemble Google’s logo, and I also added a Ms. Pac-Man mode as an easter egg; the already-classic I’m Feeling Lucky button was reimagined as Insert Coin. I even added a few bugs that I learned existed in the original Pac-Man. But I also introduced at least one important bug of my own making, one that backfired on launch day.

We wanted the game to have sound, because so many of Pac-Man’s sounds are beyond iconic: the starting melody, the waka-wakas, the death jingle. This presented a little technical challenge, since I hoped for the doodle to be a showcase of what pure HTML and CSS could do, but sound still needed quiet (huh) support from Flash. However, Flash was, by then, installed in a lot of browsers, so that worked out okay.

The project was all was going really well. I had fun coding the game and we seemed to have fun playing it. Namco eventually got onboard, too, including greenlighting the Ms. Pac-Man addition that I only later learned had a pretty complex political story.

We felt so happy about the progress, as a matter of fact, that the leadership wanted the doodle to feel even bigger. And at some point, we thought about the game autoplaying on the homepage after 10 seconds of inactivity – just to let you know that you could have some fun in a place you might not have expected it.

I was happy with that – if there was anything scary about it at the time, it was only the thought of my code getting even more exposure – but I wasn’t worried about distraction, since the homepage was not a destination page you would ever linger on.

As you can piece together, Pac-Man would also, as a consequence of all these decisions, autoplay with sound. We knew that, I think, and in that moment it felt like… it would probably be okay. In hindsight, it wasn’t okay, but it also was not okay in a way that none of us expected.

The launch day came. A couple of people on the team and I pulled an all-nighter that included putting in some finishing touches, and preparing an internal tournament version of Pac-Man. Personally, I was petrified. I was but a designer on the user experience team. Sure, my code went through all the proper reviews – but I still couldn’t believe it would be allowed, verbatim, on one of Google’s most valuable properties.

We toggled the switch at 9am San Francisco time. Within hours, the world once again went wild for Pac-Man. Soon, I watched feedback arrive in torrents too huge for me to ever catch up with. I was asked to do press interviews. I saw Twitter crash. Most importantly, I witnessed reports from all over the world of people playing Pac-Man in all sorts of circumstances, on all sorts of devices (HTML!).

And indeed, we got a few reports of the “there is a really scary sound coming out of my computer” variety. But they didn’t come through the channels we expected. And when we suggested “the quick workaround is just to close the tab with Pac-Man,” invariably the answer would be:

“What Pac-Man?”

This is what we figured out over the next frantic few hours. Some people using the then-ultrapopular Firefox installed an extension called CoolPreviews, which allowed them to quickly preview pages by hovering over links. The extension would quietly start at the same time Firefox was opened. And it would immediately, in the background, invisibly and unbeknownst to the user, open a website. I am not sure if that decision was to prime the cache, or whether it was just a forgotten placeholder.

That website was Google’s homepage.

You probably already know what happened. On that particular Friday, google.com had an auto-playable Pac-Man doodle with the sound on. If you used Firefox with CoolPreviews installed, the plugin would quietly open Google’s homepage in the background whenever you launched the browser, and 10 seconds later…

Imagine this for a second. You sit down Friday morning and power up your computer. For you, there’s nothing unusual about this Friday. You don’t have to use, or even know about Google. You might not know what browser you use — or what a browser is. As a matter of fact, you might not even be using your browser; perhaps it has been minimized and sits unobtrusively in the toolbar at the bottom of your screen. You might not know about CoolPreviews, or even the concept of plugins or extensions. Perhaps you’re just checking your mail or warming up for today’s first round of Solitaire.

Then, out of a sudden, out of your speakers comes blasting a siren of an invisible Pac-Man game having infiltrated your computer in the most unusual manner.

On repeat.

I know Google feels different now, 16 years after this story took place. I know we are all tired of websites that autoplay sound and that decision we’ve made feels uncomfortably close to “growth hacking.” But the story takes place in that slightly more naïve era of 2010.

I pushed a patch within hours. It ended up being the same solution many browsers do by default today – we added a visible mute button, and you now had to first touch the game in some way (a keystroke, a click, multitouch, or the Insert Coin button) for the sound to activate. Since CoolPreviews didn’t do that, it fixed the “possessed computer” problem. Ironically, I don’t believe we ever heard of normal people being bothered by the autoplay – it seemed that indeed, few people stayed on the homepage for 10 seconds doing absolutely nothing.

The funny thing is that emergency live-patching internet’s at the time most valuable homepage was perhaps the scariest part of that day for me, but that completely went over my sleep-deprived head.

And eventually, my job title changed. How close it felt to a “software engineer” is up to you to decide:

I wrote a story with the same title in 2015, but it got mangled online, and I’m unhappy with the writing now – so this is basically a complete rewrite of that essay. You can still play Google Pac-Man doodle, with the sound now reimplemented sans Flash.

November 22, 1963

It’s Halloween Week on Unsung, where we’re sharing scary, spooky, and creepy stories. This is a real story, and an excerpt from chapter 12 of my book Shift Happens.

The keyboards of the first teletypes looked as if the Shift Wars had happened in an alternate timeline won by typewriters with two Shifts, a century before the arrival of the iPhone. The first teletypes were, too, built with only three banks of keys, the digits sharing the top row of QWERTY. Among the most common was the striking green keyboard of Teletype Model 15, made by a company that – like many – renamed itself after its most popular product. The 15s were robust, heavy, and almost indestructible; 200,000 were made between 1930 and 1954, their production prolonged by World War II.

But the comparison to typewriters with two Shifts broke down as soon as you sat down to a teletype. There was one key called Figs and another called Ltrs, but there was no actual shifting. The two keys were meant to be used alone – pressing one would affect the meaning of all the keys used after it. Figs switched the teletype into digits and punctuation mode; Ltrs made all the keys once again behave as letters. The digits and punctuation covered all the common cases, but the letters were available only in uppercase, and remained so for a long, long time.

The reason for switching instead of shifting went back to Baudôt and his five keys. Five keys give thirty-one possibilities – not enough for the letters of the alphabet, digits, and common punctuation. So Baudôt added two non-printing combinations. Pressing just the leftmost key would switch the machine to think of letters; pressing just the second key from the left would make it focus on digits. Every chord’s character depended on what mode the machine was in: right index finger was A or 1, the middle index finger E or 2, four leftmost fingers meant L or the equals sign. Thirty-one possible combinations became fifty-eight. And even when teletypes switched to a QWERTY keyboard, under the hood they still relied on a modernized version of Baudôt’s code, switching and all.

There were more differences from typewriter keyboards. The keys had an unusual, cushioned feel: each key had a small spring inside for more comfortable typing. For the first time in history, the tops of the keys were held to the base magnetically and could be removed, making it easy to swap them for different uses. And the common mechanical gesture of the carriage return had been decoupled into two separate keys – Car Ret and Line Feed. Carriage return moved the carriage back to the beginning of the line; line feed advanced to the next line. This was done to give the teletype a bit more time for a carriage return to complete. The split was manual, however; the operator had to press the two keys one at a time, in the correct order, with every new line.

Look at post-World War II teletypes, and you’ll find other interesting keys. One common one was labeled Who Are You? Pressing it would generate a special invisible code and ask the other machine to introduce itself. It was sometimes done automatically; other times it required the interlocutor to press a key labeled Here Is, which mechanically output a pre-recorded sequence of letters identifying the location, like DE G3PPD HARROW.

You might also stumble upon another ingenious physical-world backspace. Did you press a key by mistake, creating the wrong set of holes in the paper tape? You could rewind one spot and punch out all the other holes. It was kind of like backspacing on a typewriter and typing x over a typo, but it was invisible – no one was meant to read the tape itself, and the teletypes were programmed to ignore the five-hole position when printing the text on regular paper. And since paper tape was effectively infinite, a message with many corrected typos would have only one side effect – it would arrive marginally slower than one typed neatly.

The Who Are You?, Here Is, and Backspace keys were enhancements that came after the Model 15. But even the earlier model sported one unique key: S/Bell. In letters mode, Bell would do as expected and print a letter S. Switch to digits and punctuation mode, however, and the teletype would ring a bell. It would do so not just on the machine you used, but also on the teletype on the other side.

It wasn’t a gentle typewriter bell alerting you to the end of the line, either. The teletype bell harkened back to an idea in an 1837 telegraph by Cooke and Wheatstone, its ringing meant to alert someone that a message was coming. And sometimes, it was an important message.


The Morse code-powered telegraph network gave us a taste of what an internet could be. Teletypes added automation. In the late 1920s, the next step was Telex, a global network that connected business teletypes.

Elsewhere, post offices in many countries brought telegraphy to the masses by introducing telegrams, a way to send a written message to someone via telegraph or teletype. No knowledge of Morse code or typing was necessary. The message would be typed in at the post office by a teletype clerk, travel through the wires, the resulting printout cut into pieces at the receiving station, and eventually be delivered by a clerk to the recipient’s doorstep as if it were a regular letter. Telegrams were much faster than letters, as they traveled mostly through wires; were much cheaper than long-distance phone calls; and didn’t require your recipient to have any technology in their house. (They also introduced the now-forgotten tradition of saying STOP in between sentences, and they begot the art of making messages as short as possible, later perfected in texting and on Twitter.)

But what was most commonly associated with the telegraph first and teletypes later was the instant broadcast of world events. The Associated Press (AP), Reuters, and United Press International (UPI) took Morse’s “Have you any news?” to heart, and established competing networks of teletypes clacking impatiently with the latest bulletins. Their correspondents would dictate by phone to their offices. The transcribed reports were typed in on one of the agency’s teletypes and sent within seconds to receiving teletypes in the subscribing newspapers. Since most of it happened over wires, it was often called “the wire service.” One UPI employer remembered:

Nothing was true in those days unless the wire services said it was. Confirmation was on the yellow paper rolling out of Teletypes. There was no 24/7 cable TV news. No emailing. No tweeting.

The teletypes were a common fixture in newspapers, “as common as a bathroom, although the machines probably were kept in better repair,” as one reporter recalled. “There was something about the throbbing of teletypes that made reporters and editors feel alive,” an article noted in the Philadelphia Inquirer in 1986.

They used electromechanical technologies similar to those in electric typewriters. They were, however, driven by paper tape, and so their typing was distinctively machine-like, always at the constant speed of about 60wpm. “They made a low, guttural engine noise – rugrugrugrugrug – punctuated by that loud da dacka-dacka dak-dak, and they were as constant and pokey as a pair of plowmules. They. Yielded. Their. Secrets. One. Word. At. A. Time,” wrote the seasoned Philadelphia Inquirer reporter David O’Reilly. Just as many newspapers put the word Telegraph in their titles in the nineteenth century to align themselves with the high tech of that time, the next century witnessed many TV or radio news programs adding the distinctive cacophony of multiple clattering teletypes to their opening titles.

One surprising but important component in the sharing of news was the S/Bell key. Its use evolved over time. It was no longer just about catching attention – the number of bells grew to signify the importance of upcoming news. On UPI teletypes, three bells meant “Urgent,” five bells indicated a “Bulletin,” and ten bells was a “Flash” – a story so rare and significant that it changed the world’s trajectory.

Flash stories were reserved for earth-shattering events: a declaration of war, a president’s resignation, the death of the Pope. They would cause a newspaper printing plant foreman to yell “stop the presses” and a TV station manager to interrupt shows with breaking news. “Guys had worked in newsrooms for years and never heard ten bells,” wrote the Philadelphia Enquirer. Another columnist put it more bluntly: “when [a teletype’s] bells chimed out a Bulletin or Flash, it was like God clearing His throat.”


God cleared their throat on November 22, 1963, when Lee Harvey Oswald shot President John F. Kennedy in Dallas, Texas, at 12:30 local time. UPI reporter Merriman Smith, riding in the motorcade just behind the president, got ahold of the press car’s radiophone and called UPI with the news. Soon, a few thousand UPI subscriber teletypes across the world started printing in unison. One inside the U. S. government cabinet plane reported:

HANDSOME DR. ALEL DOHRN. %% WAS N IDEALIST BUT BROKE
THE LAW IN AT LEAST IP OF THE QNEPP STERILIZATION
OPERATIONS HE HAS PERFORME ON LOCAL WOMEN
MORE
HS137PEST
RV
SSSSSSSS
FLASH
KENNEDY SERIOSTY WOUNDED PESTSSSSSSSSSS
HS 138/
SSSSSSSSSSS
MAKE THAT PERHAPS PERHAPS SERIOUSLY WOUNDED
HSQEOPEST
SSSSSSSSSSSSSS
GJ OWHL W WOUNDED BY
HQ139PESTXXXXXXXXXXXXXXXXXXXXXXXX
KENNEDY WOUNDED PERHAPS FATALLY BY VASSASSINS BULLET
HS139PESTSSSSSSSSSSSSSSSS

The chaos of the garbled transmission seems to capture the magnitude of the news. Knowing how teletypes – and their keyboards – worked, we can decipher most of it, starting with a few lines from a message from Hanover, West Germany: an update in the trial of a local doctor.

Then the Dallas messages start taking over, although not without trouble. Typos likely happened in a hurry to get the message out, and the unusual spacing came from not giving enough time for Car Ret and Line Feed actions to finish their job. (Either could also have been the result of the Hanover and Dallas teletypes talking over each other on the same line at the same moment.)

HS137PEST and others like it were standard signatures following each transmission: two letters for the initials of the operator, and seven to indicate 1:37pm Eastern time. How about HSQEOPEST? It’s the operator forgetting to press the Figs key, or the signal being lost in transmission – the keystrokes 1 3 9, meaning 1:39pm, come out as QEO, as the receiving teletype never switched to speaking in digits.

This is the reason we see a repeated line of X, meant to be slashes separating one message from another. That also explains the long lines of confused letters S, and makes them more harrowing – those were meant to be bells, ringing to alert everyone of an event that shook the nation like few did in the twentieth century. But the switch to digits mode never happens or is lost in transmission, and the machines, obedient and clueless, interpret the transmitted data blindly. Counting the letters betrays the urgency, the desperation, or the despair felt by the teletype operator typing in the message. In a break with protocol, the early eight and ten bells grow to eleven, and then to an unprecedented sixteen bells.

This wasn’t God clearing their throat – this was God caught surprised. The president was dying. Just a few minutes after seeing the UPI’s messages, CBS interrupted its mid-day soap opera to put on air a distraught Walter Cronkite, and soon the other two networks followed, suspending their usual programming for the subsequent three days and nights.

On the wire, the uncanny intersection of human emotions and machine coldness continued, as transmissions of people oblivious to the tragic events in Dallas interleaved with frantic shouting from others:

STAY OFF ALL OF YOU STAY OFF AND KEEP OFF GET OFF
WILL U U P L E A S E STAY OFF THIS WIRE
STAY OFF STAY OFF

But in time, everyone understood and the day’s other events surrendered. An hour after the shooting, another teletype operator, Alice Guenther, started a new shift at the UPI offices. Four minutes later, the White House sent out the feared message of President Kennedy’s death. The broadcast news editor asked Alice to key it into the teletype, but her reaction reminded us that despite all the mechanization and the rhythmic ticking of teletype machines, sitting behind keyboards were still people. Guenther could not make herself finish the task. She took her hands from the keyboard, covered her face, collapsed, and cried “Oh, my God.” The operator supervisor, Jimmy Darr, walked over to her, lifted her out of the chair, let her sit gently on the floor, and leaned over the keyboard. Thirty-nine keystrokes later, at 1:35 Dallas time, thousands of UPI teletypes rang ten bells for one more time that day, and then printed, at a measured pace:

FLASH

PRESIDENT KENNEDY DEAD

JT135PCS

The beautiful, quiet power of motor memory

My favourite piece of writing I’ve done about motor memory remains “Shift + Shift” from 2018. I have linked to it over the years, but if you haven’t checked it out yet, you might find it interesting.

Just this week, I have had another similar moment, and amazing in a slightly new way.

How many of you tap ⌘1, ⌘2, ⌘3 to switch between tabs? This convention has been there for as long as I remember, and so has been my fingers’s embrace of it. The system works in Chrome and Safari, in the Terminal (and Ghostty, which even shows the shortcuts on tabs themselves), in Nova, in Figma, and presumably tons of other places:

(Just about the only place where it doesn’t work is the Finder, and that’s only because ⌘1/2/3 keys there were first assigned to switching the view style – icons, list, column view – some time in the early 2000s, some years before the tabs came. Hard to change a shortcut people are already used to; luckily, I personally don’t use tabs in Finder.)

At this point, I press ⌘1 and ⌘2 and ⌘3 without thinking, just as instinctively as I would ⌘Z for undo, or ⌘C for copy.

So instinctively, in fact, that last week I was looking at Messages, I wanted to switch to the group chat, and my fingers just reached for ⌘1:

I have never done it before. I have not heard this was possible, nor seen it announced in the menu, or a tooltip, or via onboarding. I didn’t even think about it. My fingers just… did it. Completely on their own.

And it worked.

I was just there, looking at my hand amazed, piecing together what just happened as if I were watching someone else’s actions.

It’s funny to pause and think about such a seemingly tiny thing. After all, this happens all the time. Every time I slam Esc to dismiss a dialog I never closed before, every time I press ⌘V to paste something in a new location, every time I tab from one field to another in an app I just installed – sure, these might be system defaults in various places, but I see them break once in a while; when they do work someone might deserve credit for wiring them properly, even if I take it for granted.

In these moments, you only notice things going badly; as a matter of fact on the same day I pasted some bolded text into the very same Messages app, and tried to press ⌘B to undo the bolding – and that didn’t work.

And I think that’s why that ⌘1 in Messages is worth a little celebration. Over the years, enough apps and websites and operating systems quietly decided to spend extra effort to participate in the ⌘123 convention, together building a dependable interaction system that more and more people’s motor memories could learn to trust over time.

That included mine, including one extra thing that separates it from the story I linked in the first paragraph – and one you probably already noticed.

The Messages app doesn’t have tabs. My motor memory kicking in wasn’t just a recall of something that I’ve already done before. Somehow, in my brain, this convention felt so great that it quietly extended from “⌘1 = first tab” to “⌘1 = first content thingy,” without me even realizing.

And that’s so amazing, right? It’s stuff like this why I keep harping on Safari’s problematic tabs and other compromised interaction systems, and that’s why today I raise a small toast to the designer at Apple who thought about ⌘1 in such a clever way.

GUIdebook and other GUI stories

I started GUIdebook in 2003, and last updated it exactly twenty years ago.

It’s an interesting time capsule itself now, incompatible with mobile reading and sporting an aged design. I have kept it up because it’s apparently used as a reference in various user interface courses, and if you haven’t seen it, it could be a fun browse.

I walked away from it by accident, distracted by a new job, but I always wanted to evolve it into something better as my storytelling skills and my interactive skills grew.

Unsung is GUIdebook’s cousin, of course, especially in pieces like Lisa’s copy (and cut, and paste), Were Touch Bar’s problems software rather than hardware?, and even little things like Anachronisms.

But the direct preview of what I dreamt GUIdebook of becoming was in my last year’s interactive piece Frame of preference. It’s a history of the first twenty years of Mac interfaces told through its settings, it has a proper narrative (I never got to it with GUIdebook), and instead of screenshots, it uses Infinite Mac’s technology to tell the stories via emulation. I’m pretty proud of how it turned out, and you might enjoy it if you haven’t seen it yet.

I would love to try a few more things like it.

But, back to GUIdebook. Keeping it alive for 20 years required multiple updates as PHP evolved, and a more recent rewrite that ditched easily-hackable PHP altogether. (Don’t ask me how I know it’s easily hackable.) None of these were particularly noticeable on the surface, but I recently added one tiny user-visible change – the screenshots are now properly pixellated:

It was fun – and slightly eerie – to update the site’s history page two decades after I touched it last.

A hacker’s guide to bending the universe

Continuing the theme of software fixes for hardware problems, here’s an essay I wrote in 2016 about a broken computer display that I “fixed” as a teenager, just because I wanted to play Civilization.

It remains one of my favourite things I’ve ever written.

My design bookshelves

Inspired by a conversation with a friend, I made a mini site that’s an interactive representation of my design bookshelves:

I am hoping it becomes a fun reference to browse, or something just enjoyable to play with. I made the interface feel very differently on desktop and mobile, and I hope both are fun. (There’s also a simple list if not.)

I wish, just like with a regular bookshelf, you could open any book and check it out – but that’s tricky for many reasons. (I did at least scan some of the covers that weren’t available on the web.)

Medium’s writerly favicons

One of the small things I added to Medium in early 2016 was a change to the favicon:

It came from an observation about the writing process. When writing on Medium, you are likely to have a bunch of Medium tabs open with other posts, yours or otherwise, for reference… but you usually only have one tab you’re writing in. Why not make it extra visible so that you can easily come back to it?

But there was a second, more emotional reason. Writing is hard. Many people never touch the “New story” button, on Medium or otherwise. I wanted the writers to feel extra amazing, with the interface itself giving them a nod of recognition. (Visually, the hollow draft icon was also meant to be a “scaffolding” of the published story icon.)

I’d love to hear more about websites or web apps that are using favicons in a particularly useful or delightful fashion. If you have examples, I would appreciate a note!

Arno Beck’s art

I am generally not a fan of typewritten art, because at some point it all starts to feel a bit same’y, and the gimmick of using a typewriter as a paintbrush wears off pretty quickly.

But these drawings by German artist Arno Beck caught my attention, because it feels like they playfully remix three eras:

  • overtyping keyboard art (early 1900s),
  • the sort of photorealistic smooth shading I most associate with ASCII/​ANSI art (1990s),
  • big pixels from early home videogames (1980s).

In case this interests you, in 2018 I gave a 46-minute talk called “The abridged history of having fun with keyboards” that’s a (hopefully fun) walkthrough of this whole space:

The monkey lives again

Speaking of computers that used to stop running if you looked at them funny, a few years ago I wrote about the Monkey app that was there on the original Mac. Many software engineers will recognize the premise – Monkey was just a chaos script randomly pressing mouse buttons and keys during the night hours, and if the computer crashed because of Monkey’s random actions, the team would be able to reproduce it and try to fix it.

I was also inspired to try a Monkey-like approach for something creative. In hindsight, it’s a very Unsung post, so you might enjoy it!

Also, in the post, I showed this boring version of Monkey:

Since then, I discovered a different version with its own icon, perhaps designed by Susan Kare:

(If creative use of randomness rings a bell, here’s also an earlier Unsung post about a different take.)

text.makeup

I am generally not someone who cares much for easter eggs (unless they come with interesting stories), but John Gruber’s one-liner made me pause for an unexpected reason:

Joanna Stern explains why this emoji is correct today: 📅. (This one too: 📆)

I thought the two different calendars was some trickery, but the answer is simpler than that. I did not realize that, inexplicably, there are two distinct calendar emoji: one for calendar, and one for a tear-off calendar.

The way I learned about it was to use a tool I made a few years ago called text.makeup:

I thought this would be a nice opportunity to share it with you. If you’re debugging a string you don’t understand, or are just interested in learning about various Unicode or encoding secrets through playing (see the left sidebar!), it might be a fun thing to use.

I just updated it with the most recent emoji (and Unicode goodies) that will drop after September this year.

My one (1) Medium secret

When I was at Medium, over a decade ago, I really enjoyed going deep on typography.

People seemed to generally enjoy what we did. Writers really loved automatic em dashes and range dashes, discovered the beauty of hanging punctuation, and as funny as it might sound today, the smart quotes were a huge hit, too. I was proud of the tight drop caps, the underlines brought me some notoriety, and we even supported ligatures at a time when not only this wasn’t the default, but it also had some mildly scary performance consequences.

But for every two things that worked well, there was also something that in retrospect proved to be me trying too hard, and had to be quickly undone.

I was really excited about resurrecting pilcrows, but many users saw them as rendering or escaping errors.

I briefly added vulgar fractions to all the places where Medium rounded numbers, but that made those numbers confusing and weird in practice.

(And I already mentioned the strange, rare bug with system fonts, although I suppose there are always bugs.)

It was an interesting calibration process. And somewhere in between successes and failures was one thing that I have never mentioned before, and one nobody ever brought up.

I recently shared the story of 2015’s typographical redesign of Medium. As we were exploring the candidate typefaces, we fell in love with one in particular: Charter, a font designed by the industry legend Matthew Carter – and no, this is not a bug, Google Search switches to using Carter’s own Verdana to honor him.

Charter had this perfect balance of “casual” and “refined” we wanted for Medium at the time. Unsurprisingly, it also came with a bunch of typographical niceties – among them lowercase (old-style) digits, which I really wanted:

But there was a problem. Those lowercase numerals came with a “medieval 1,” a particular style of a lowercase digit 1 that resembled an uppercase I. People hated it and were confused by it, thinking indeed that a bug caused a letter I to make its way to the numbers.

No amount of pleading would get us to push that digit through. The backup plan was going with uppercase numerals, but I hated the idea; those digits felt so ugly and pedestrian to me – they were not just uppercase, but also monospace! It was a frustrating situation, being so close and yet separated from a warm Charter embrace by one glyph that it didn’t happen to have.

And so… I drew one.

I, someone who has never ever designed a typeface, decided to vandalize Matthew “The Most Widely Read Man In The World” Carter’s typeface and plop in a new digit 1 of my own creation.

The internal complaints stopped. Weeks later, we launched the new fonts, Charter front and center, my fresh non-medieval 1 attached. I don’t remember the exact details, but we found a way to do this that was compatible with the font’s licensing – and yet I never talked about it because… well, I think you can understand why.

I believe my rogue 1 lasted until a subsequent redesign in 2022, long after I left the company. A decade in, I still don’t know how to feel about it. Did I save Charter as a candidate for Medium by mutilating it a bit, am I writing this post just to launder my own ego, or is this the equivalent of a perp coming back to the scene of the crime? Was I ambitious (laudatory) or ambitious (derogatory)? Maybe you can tell me. But I hope either way it makes for a fun story.

The curious case of the disappearing Polish S

Speaking of remastering (and diacritics), I grabbed my older Medium deep dive called The curious case of the disappearing Polish S, and put it on the new site.

It looks so much better than on Medium and while I was at it, I’ve redone all the visuals, and updated it a little bit.)

It’s still probably one of my favourite bugs to encounter. I hope you enjoy!

Show your hands honor for the strange power they bring you

Here’s a big interactive essay I just finished.

The theme: What does it take to build interfaces that truly allow for fast operation – and why that matters.

If you like the interactive details posts here on Unsung, the essay is kind of a concentrated dose of all that. You can technically read it on the phone, but it’s so much better on a computer (or a big tablet). It has ~40 interactive playgrounds, and sounds, and a glossary, and all sorts of fun stuff I’m doing for the first time.

I wanted to share some things I learned over the years, and nod toward mostly anonymous creators of UX inventions I’ve long admired. I also thought it could be interesting to make interfaces appear as machinery – you’ll see what I mean.

Let me know if I succeeded!

System shock

I occasionally move older writing that still feels interesting to my new site, and today I republished the 2015 story about a strange bug that brought back an old pixel font from beyond the grave:

Some of the technical details inside are obsolete, but the story might still be fun. (Plus, it seems like at every job I have, I eventually stumble upon a bug that brings back something from the annals of history. Here’s one from 2019.)

My essay about the Fn key

I just published a new photoessay about the history of the Fn key, and particularly what Apple has been doing with it recently.

Do we need yet another person crashing out about Apple’s design decisions? Am I doing it only because it’s fashionable to be on Apple Design Hate Train these days? I’ll be honest: I don’t know.

But I have been bothered by Apple’s approach to this aspect of its keyboard design for a while, because it starts breaking what I think is really important in using a computer well: keyboard shortcuts.

I hope it’s also a fun visual history of the most tricky of modern modifier keys.

(And if you like it, I linked to a few of my other keyboard essays in the footer.)

Fitts’s Law at 20

Just kidding. But it’s a happy 20th annivesary to the little interactive explainer I made of Fitts’ Law back in 2005!

It’s charming in a sort of early-web kinda way, but still holds up – at least on bigger screens. I even ran it on my iPad and it worked.