Skip to main content

It's pronounced JIF. The Open and Async audiobook is out.

8 min read
TL;DR: The Open and Async audiobook is out, and the narrator says 'jif,' correctly. Since the internet will never drop the hard-G thing, I recorded a chapter both ways and posted them free. You get one chapter the wrong way, or eleven and a half hours the right way.
Table of contents

The Open and Async audiobook is out. It’s read by a synthetic voice, which means that at some point a machine had to decide how to say GIF, with no help from me. It picked “jif.” Correctly. I have never been prouder of a robot.

In a bit, you’ll hear the audiobook both ways, the same line read by the same robot, and you can settle the argument yourself. Headphones on.

The fight only exists out loud#

GIF-versus-JIF is the one internet argument that text is structurally incapable of settling. You can go your whole career typing “GIF” and never once reveal which side you’re on, because the letters look identical in both camps. Type “actually, it’s pronounced jif” into a thread until your keyboard wears out, and nobody hears a thing. The fight only exists in sound. Record audio and it comes for you, wanting an answer before the next sentence. That’s how the audiobook became the first version of this book that could even have the argument. It took my side without being asked.

For the record: soft G. It’s “jif,” like the peanut butter.1 Reasonable, thoughtful, wrong people say it with a hard G. We work together anyway.

Case in point. A paragraph can't do this.

There’s a chapter in the book about using chat well, and a section in it about emoji and animated GIFs being a kind of body language for text. A well-placed “that escalated quickly” carries something a paragraph can’t. The book already argues, in print, that GIFs matter. It just never had to say the word out loud. Then I made an audiobook, and it did, eleven times, in one chapter.

I recorded it wrong on purpose#

I wrote a whole book about working in the open, though, and the open-and-async answer to a disagreement is not to win the thread. It’s to ship the artifact and let people decide. I built the most literal version of that I could think of. I re-recorded the entire chapter with the narrator forced to say hard-G “gif,” beginning to end, and posted it, free, right next to the correct one. An entire edition in the wrong pronunciation, rendered for the heretics to enjoy their own wrongness. Same words, same narrator, one phoneme of difference. Pick your fighter. Mine already won.

The cat in question, for the record.

Ten seconds each, the same line both ways: “an urgent message from your manager gets the same screen space as a GIF of a cat playing the piano.”

Team JIF (the correct one)
Team hard-G (for the heretics)

The pronunciation was never the point. The GIF is. (share this quote)

That’s the point hiding inside the bit. The whole reason the chapter defends GIFs is that the shared reference does the work. Nobody who gets the joke has ever cared how you say the three letters. Arguing about the phoneme is bikeshedding the one part of the thing that carries no meaning at all. It’s impact over input, applied to a debate about peanut butter.

Both cuts live on the book’s feedback repository, which is where readers tell me what’s broken, what’s missing, and what actually landed.

Consider the hard-G edition a bug I shipped on purpose, a public service to the people who need to hear it. (share this quote)

About the robot narrator#

People kept asking for an audiobook, to listen at the gym or on a commute, and I’m a big audiobook fan myself. I did some of my best listening on parental leave, one hand on a stroller. I wanted the book to reach people that way too. What I didn’t have was a way to pay for it. A human narration doesn’t pencil out for me right now, not a professional’s four-figure, months-long project, and not the fifty-plus hours it would take me to read a hundred thousand words myself, badly. That left a synthetic narrator, and I’d rather say so straight than have you notice it later. No human voice actor, no studio.

Synthetic is the shortcut, and I’m not going to pretend it’s anything else. (share this quote)

Something real is lost with it. A good narrator doesn’t just say the words, they perform them: the timing, the dry aside, the breath before a hard sentence. My robot reads cleanly. It isn’t an actor, and if you’ve heard a great human narration, you’ll feel the difference. The bigger cost lands past my one book. Synthetic narration takes work from the people who do this for a living, and “it was cheaper for me” is exactly the logic that adds up to their livelihoods shrinking. I don’t have a clean answer to that.

A human narrator for this book is the goal, not a synthetic stand-in forever. If it earns its way there, it’ll get one. Until then, imperfect and shipped beats perfect and imaginary. Ship early, ship often.

Here’s where that leaves me: the voice is disclosed, it isn’t cloned from a real person, and a human (me) listened to all eleven and a half hours before it shipped.2 Machine-narrated, human-checked. If a synthetic voice is a hard pass for you, I get it, and the ebook and paperback let you hear “jif” in your own head, at your own pace.

Get the audiobook#

That free chapter is a free sample, and I mean that literally. If you want the same synthetic narrator to read you the whole book, saying “jif” correctly the entire time, the full audiobook is out now. Eleven and a half hours of it, and not one hard G.

I am not going to win this argument. Nobody wins this argument. That’s exactly why you hand people the choice instead of typing one more reply, then go build the next thing. Even if one of the choices is objectively incorrect.

The right edition is the whole audiobook. The other one is just me being generous to the wrong ones.

So, which are you? Choose carefully. My narrator already did.

Footnotes#

  1. Steve Wilhite created the format at CompuServe in 1987, and when he accepted a lifetime achievement award he stood on a stage and said “it’s pronounced JIF.” The man who invented the thing gets to name it, and the hard-G crowd is out here overruling him. “But graphics has a hard G” is not the counterargument they think it is. It’s an acronym, not a word, and the inventor already ruled. Yes, there’s the peanut butter. Yes, I’m on that side too. I have made my peace with being right.

  2. The audiobook has its own QA suite. It transcribes the generated narration back to text, diffs that against the script, and flags mispronunciations, so a stray hard-G “gif” can’t slip into the correct edition. The machine reads. I still get the last ear.

Open & Async book cover

Out now

Open&Async

The collaborative software development playbook for remote and distributed teams. Drawing on a decade at GitHub — on Kindle, Apple Books, Kobo & more.

Buy it — $9.99
Originally published September 8, 2026 View revision history
Share

More to explore

Accessible by default: writing a book like software

9 min read

The ebook meets the Web Content Accessibility Guidelines (WCAG 2.1 Level AA) because the format wouldn't let me fake a heading and a browser audits every build, not because anyone scheduled a week for it. The parts Markdown can't check, like color contrast, axe-core catches under Playwright.

Open and Async: the remote-work playbook is out

3 min read

Open and Async is the practical playbook for making remote and distributed work actually work—two habits, working in the open and communicating asynchronously, drawn from a decade of remote-first lessons at GitHub.

Open and async on the Overcommitted podcast

1 min read

What makes a remote engineering team work isn't where people sit. It's how they communicate. A conversation on the Overcommitted podcast about async-first culture, decision durability, and the ideas behind Open and Async.

AI-first program management

11 min read

AI-augmented program management is the natural evolution of async-first and engineering-inspired workflows — amplifying human judgment, not replacing it.

Work loudly

6 min read

In an office, some of your visibility is free. Go remote and it drops to zero. Working loudly makes your impact visible as you do it—not after the fact in a status update nobody reads.

15 rules for communicating at GitHub

16 min read

How GitHub uses issues and chat for async communication: fifteen rules that eliminate the 'you had to be there' problem in corporate workflows.

How to one-on-one

5 min read

Most 1:1s waste your team's only protected synchronous time on status updates. Here's how to run ones worth showing up for.

Eight tips for working remotely

10 min read

Tools alone won't make remote work succeed. Eight cultural rules for effective async communication, regardless of your industry or role.

We've Been Selling Open Source Wrong

4 min read

Demanding agencies release code misses the point. Open source is a culture and workflow, not a deliverable. Fix the process and the code follows.

Ben Balter

I'm Ben Balter — I write here about engineering leadership, open source, and showing your work. I wrote Open & Async, the playbook for remote and distributed teams. My open source projects have hundreds of millions of downloads. I was the Director of Hubber Enablement at GitHub, where I helped thousands of GitHubbers do their best remote work. Before this role: Chief of Staff for Security, enterprise PM, and GitHub's first Government Evangelist. Before GitHub: attorney, Presidential Innovation Fellow, and member of the White House's first agile development team. More about the author →

Follow along: Bluesky LinkedIn

This page is open source Help improve this article on GitHub