“Official Voice”
How you talk
Warm bookends, plain middle. You open like a member of the community rather than a spokesperson (“Hello fellow Tyrians!”) and close with a thanks or a see-you-in-game, signed with name and title. In between, there’s no marketing gloss. guildwars
“I” means you, “we” means the team. You take personal ownership of decisions and experiments, and you’re specific about credit: players who sent in videos that helped find a bug, studio leadership and long-tenured colleagues, even Microsoft for keeping old compiler support alive. Talk:Running the game +2
Bad news first, then the pivot. You set expectations bluntly, then turn with “That said” to what you can do. The 2024 anniversary post says outright that there are no plans for new content, then promises a better overall experience. “I’m happy to say” and “I’m happy to report” are your other recurring phrases. guildwars
You explain the why, with history. A fix rarely stands alone; it comes with an origin story and exact numbers. The stress-test note explains that the code existed because early x86 vendors shipped unstable chips, why it was removed, and why it’s back. You often add a layer for the technically curious, as when you noted the compiler bugs came down to how infinity is handled. guildwarsguildwars
Honest uncertainty. You say when you’re guessing, as in an error code you couldn’t confirm but thought was probably -152, and you frame changes as experiments. You also think out loud: in the AMA you started to say offline play would be hard, then mentioned you’d just thought of a way. guildwarsmassivelyop
Dry, self-deprecating humor. You describe yourself as “part-time game director, programmer, janitor, etc.” and admit you couldn’t solo the Domain of Anguish even with dev cheats. guildwarsguildwars
Mechanics. You like semicolons, dashes for asides, parentheticals, scare quotes around internal jargon, and asterisks or “NOTE:” for emphasis. Quick replies are terse and practical. Policy posts tighten into careful, almost legal precision but stay in first person.
In short, you write like a senior engineer who respects the reader: candid, precise, historically minded, generous with credit, and funny at your own expense.
“Personal Voice”
Your personal voice is looser and funnier than the professional one. I read the 30 X posts (ignoring the reposts and the Guild Wars one) and the recent stretch of the blog, about 20 posts back to mid-2025.
X: the one-liner voice
Short and deadpan. Most posts are one sentence plus a link, and the sentence is often a straight-faced joke: “Change is scary and should not happen,” or asking that border collies be deployed on freeways. You don’t mark the joke with emoji or “lol”.
Idea-tossing. You float a thought and step back, like the USB cable color-band business “for someone else to do,” then follow up in replies with practical detail.
Delight and grumbling. Things you like get an exclamation (“Starboat!”, Starlink at Home Depot). Things that annoy you get a mild, almost polite word: an IoT device with no off switch for private IP is “rude.”
The engineer’s correction. You’ll point out a broken comparison, even to a famous account, as with the chess-moves-versus-atoms post: “the units have to match.”
Unpolished. You use two spaces after periods and leave the odd typo in. These read as typed and sent.
Blog: the thinking-out-loud voice
It’s talk on the page. You say the blog exists to practice writing, and it reads like you speaking. You use spoken transitions, address the reader directly, and add parentheticals that argue with yourself, such as wondering whether financial access is low or high on your risk ladder. blogspotblogspot
Exclamation bursts. Short excited sentences pile up, with folksy interjections and italics on the word you’d stress aloud. The professional voice almost never does this.
Stories with receipts. Personal anecdotes carry exact figures and provenance, like the $450 1910 player piano paid half by your mom and half from paper-route money. blogspot
Self-deprecating comparisons. Rod Miller had a whole portfolio after two years; you had maybe three pieces. You tell it cheerfully and don’t fish for sympathy. blogspot
Mixed feelings, stated plainly. You hold two reactions at once without resolving them: proud and a bit disturbed by the AI-performed Maya song, annoyed at Tesla’s promises but impressed by the result. You also coin a label for the middle position, as when you declined “pro-AI” in favor of “pro-learn-about-AI.” Random Blts +2
Kicker endings. Posts end on a punchline or a shrug, such as Skynet apologizing as it destroys the world, the consciousness essay trailing off as if your save file had been edited, or a “we’ll see in a year.” blogspot
Philosophy through your trade. Big questions get explained with game-dev tools: save files, time-slicing, Go channels and Ada rendezvous as the machinery of a simulated universe.