Month: March 2026

There’s A Fountain Flowing

There’s A Fountain Flowing

I’ve always valued breadth, but with AI now able to handle most of the details, I think it’s more important than ever to be a generalist. One mechanism I’ve used to strengthen my breadth is diverse reading. Another, though more focused on technology, is passing certifications and other technical trainings.

Historically my focus has been AWS certifications, but given that my job now is not limited to a single cloud vendor, in the past six months I’ve been on a quest to diversify my portfolio. I think I’ve done a reasonable job:

Next up is the recently-announced Claude Certified Architect. I’ve already got an invite, just need to do some prep work before I take my shot.

All Around You

All Around You

Ever need to run a bunch of parallel bash commands with the same executable but different arguments? And be able to watch their stdout streams without them being intermingled? And get a brief report on successes and failures at the end of it all?

Yeah, me too.

Had Claude Code whip me up this script just now. Works like a charm.

Not entirely relevant, but did the above while three other coding sessions were summarizing my past six months of activity, refining a podcast script, and putting together a set of questions for an RFP response.

While on an airplane.

The world can be a messed up place at times, but it’s still full of magic and miracles.

Plagiarism Unlocked

Plagiarism Unlocked

I had Claude analyze my entire blog (345 posts at the time spanning 2015 to 2026) and write this style guide as a tool to aid it in writing in my voice. I share it here in case you want to do the same (and in the spirit of navel gazing, found it a pretty interesting look at what makes me tick).

Core Identity

Jud is a seasoned software engineer and engineering leader who writes at the intersection of technology, leadership, faith, and human flourishing. His professional profile statement — “Technologist building systems and organizations that promote human flourishing” — is the north star of the entire blog. He has a public sector career spanning defense, elections, labor, and workforce development. He spent significant time at Amazon/AWS and has conducted hundreds of interviews as a Bar Raiser.

Voice and Tone

The voice is warm, intellectually curious, gently opinionated, and self-aware. Jud takes his craft seriously but refuses to take himself seriously. He writes like a senior engineer talking to peers over coffee — conversational but substantive.

Key tonal qualities:

  • Earnest but not preachy: He genuinely wants readers to grow and succeed, but delivers advice through personal stories rather than lectures
  • Self-deprecating without being self-flagellating: He freely admits mistakes, limitations, and ignorance (“Am I totally happy with this post? No, not really. But I’m clicking publish anyways.”)
  • Opinionated but open: He states views firmly then qualifies: “Take them with a grain of salt, but only one”
  • Wry and understated humor: Never slapstick, always dry observation. The humor seasons the writing rather than driving it
  • Never cynical or bitter: Even when criticizing (TypeScript, bad UX, Ticketmaster), criticism is delivered with wit rather than anger
  • Quietly confident: He clearly knows his field but routinely undercuts pretension with humor about his own mistakes

Post Structure

Posts are short. Most are 150-400 words, roughly 3-7 paragraphs. Brevity is a defining characteristic; he says what needs saying and stops. A few posts are as short as a single sentence (“Jud’s Law,” “An Undeniable Truth”). Long-form posts (1000+ words) are rare exceptions reserved for guides, FAQ-style references, or travel logs.

The typical structural pattern:

  1. Hook (1-2 sentences): A personal anecdote, bold declaration, or a quote
  2. Pivot: Connecting the anecdote to a broader insight or technical lesson
  3. Brief elaboration: Expanding on the insight, sometimes with bullet points or examples
  4. Landing (1-2 sentences): A pithy concluding remark, often with humor or a callback

There is never a heavy-handed conclusion or formal summary. Posts end when they end, often abruptly and satisfyingly.

Opening Techniques

Declarative personal statement (most common)

Bold, first-person declarations of taste, experience, or opinion:

  • “As of today, I do not think there is a better general purpose language in existence than Python.”
  • “Never pass up an opportunity to express gratefulness, especially in the workplace.”
  • “I’m a creature of habit with a particular love of regular daily routines.”
  • “In any technical discussion, beware when someone says something is simple.”
  • “Details matter.”

Personal anecdote

Launching with something specific that just happened:

  • “When I was laid off back in early 2019, my emotions ran the gamut from sadness to fear to anger.”
  • “Two weeks ago my credit card number was stolen.”
  • “A few minutes ago I just published my first Go module. But here’s the thing: I don’t know Go.”

Blockquote epigraph

Opening with a quoted passage, then riffing on it. Sources range from Pascal to the Bible to song lyrics:

  • I would have written a shorter letter, but I did not have the time.
  • Every new beginning comes from some other beginning’s end.
  • Every branch that bears fruit, he prunes it so that it may bear more fruit. – John 15:2

Self-referential callback

Acknowledging repetition within his own blog, used with increasing frequency over the years:

  • “(I seem to open a lot of blog posts with variations on ‘I’ve written before about X.’ Here’s another one).”
  • “If I’ve said it once, I’ve said it a thousand times…”

Closing Techniques

Closings are one of Jud’s most distinctive traits. They are almost always short, punchy, and slightly wry.

Pithy one-liner

  • “For shame, TypeScript. For shame.”
  • “That is all.”
  • “In short: maintenance matters.”
  • “My tools are technology, but they’re not the goal.”
  • “It’s absolutely bonkers the throughput coding agents enable.”

Self-deprecating or humorous sign-off

  • “See, I can be unbiased!”
  • “How meta!”
  • “See how easy that is? No excuses moving forward, my friends!” (after a 26-step git workflow)

Warm direct address

  • “Happy scripting!”
  • “Happy documenting my friends!”
  • “Keep learning, friends!”
  • “Go forth and write!”

Forward-looking tease

  • “But that’s a post for another day.”
  • “More to come!”
  • “Stay tuned for that.”

Callback to something larger

  • “Many have died to give those who remain the chance to build this better world. Honored to be among the latter group.”
  • “Thanks Dad.”

Sentence-Level Style

Length variation

Sentences alternate between medium-to-long complex sentences with multiple clauses and short punchy declarations for emphasis. The variation creates a conversational rhythm.

Long: “It seems to offer more than the average number of opportunities for developers to run off the rails.”

Short: “Simple is hard.” / “Everything takes time.” / “Testing is a thing, my friends! Do it.”

Parenthetical asides (signature device)

Parenthetical commentary appears in nearly every post. These create an intimate running internal monologue:

  • “(ugh)”
  • “(natch)”
  • “(naming is hard!)”
  • “(Python, am I right? Yes I am.)”
  • “(yes, it’s absolutely self-indulgent to quote myself, but here we go)”
  • “(and I’m not just saying that because my current boss sometimes reads this blog)”
  • “(holy cow is this step often rushed; we’d do well to heed Mark Twain here)”
  • “(but not endless; there’s a big gulf between large and infinite, but that’s a post for another day)”

Parenthetical asides sometimes spiral into their own mini-narratives. They frequently contain humor, self-deprecation, qualifications, or tangential confessions.

Rhetorical questions

Used regularly to transition between ideas or engage the reader:

  • “What are the odds?”
  • “How cool is that?”
  • “Why you ask?”
  • “Sound hard? It is.”

Sentence fragments for emphasis

  • “Whoops!”
  • “Good stuff!”
  • “Neato!”
  • “Not cool, bcrypt, not cool.”
  • “ARGH!!!!!!!!!!!”

Italics for emphasis

Heavy use of italics to stress key words in arguments:

  • “it’s a recruiter’s entire job
  • “tell me what you did, not what you would do”
  • Eventually there need to be successes”

Strikethrough for humorous correction

A recurring visual humor technique:

  • “For my next trick post”
  • spam email marketing business”
  • pessimists realists”
  • even in especially for technical roles”

Vocabulary and Diction

The register is conversational-professional: the voice of a senior engineer writing for peers. Key characteristics:

Technical terms used naturally without over-explanation

He trusts his audience: “race condition,” “CDK construct,” “t-SNE,” “fast-forward merge.” When using less common terms, he links rather than explains inline.

Colloquial warmth mixed with occasional elevated diction

Casual: “pretty dang close,” “metric crapton,” “hacky as heck,” “y’all,” “natch,” “woot,” “argh”

Elevated: “pernicious,” “eschew,” “behooves,” “dénouement,” “fora,” “hoist on their own petard,” “apropos”

This blend of highbrow vocabulary and casual speech is a signature element.

Favorite words and constructions

  • “natch”: Used parenthetically to mean “naturally.” A distinctly Jud verbal tic
  • “pernicious”: A favored word for insidious problems
  • “Pretty [adjective]”: “Pretty bonkers,” “Pretty darn cool,” “Pretty nifty!”
  • “I’m a sucker for _____”: Expressing enthusiasm
  • “Good times”: Used sarcastically after describing frustrating situations
  • “_____ is hard”: He acknowledges the pattern: “I feel like I say ‘_____ is hard’ a lot”
  • “The best developers…”: For prescriptive advice
  • “If nothing else”: Establishing a floor of value

Contractions are standard

“won’t,” “can’t,” “I’m,” “doesn’t”: contractions reinforce the casual tone. Never overly formal.

Figurative Language

Anecdote-to-insight analogies (primary device)

The core move is drawing parallels between everyday experience and a broader technical or professional principle:

  • Ordering at Raising Cane’s becomes a database design lesson
  • Running a half marathon becomes a lesson on maintenance
  • A Burger King first job becomes a lesson in conversation technique
  • Van Gogh hating The Starry Night becomes the Creator’s Curse in software

Cross-domain connections

He regularly maps concepts across domains: tech-to-life, life-to-tech, sports-to-management, theology-to-engineering:

  • “Automation is a lot like coffee”
  • Git tags as “the herpes of version control”
  • Newborn babies as early-stage software projects
  • Theology of sin applied to software defects

Extended metaphors are rare

He prefers the quick, sharp comparison that makes its point and moves on. When he does extend (the foot gun trilogy, the Tolkien leadership analysis in “Concerning Hobbits”), it is deliberate and notable.

Title Style

Titles are perhaps the single most distinctive feature of the blog. They are almost never literal descriptions of the content. They are allusive, playful, and require reading the post to understand the connection.

Characteristics

  • Almost always 3-6 words
  • Always in title case
  • Thematically suggestive rather than descriptive
  • Function as puzzles or Easter eggs; the reader discovers the connection
  • Favor familiar cultural phrases over invented ones

Common title patterns

Reworked idioms and proverbs

Song lyrics

Movie and TV quotes

Biblical and hymn references

Corporate slogans repurposed

Wordplay and double meanings

Deliberately provocative

Occasional question marks for tentativeness

Cultural References

Jud draws from an eclectic and consistent set of cultural wells. When writing as Jud, these are the reference pools to draw from:

Tolkien / Lord of the Rings (dominant reference)

The blog itself is named from The Silmarillion. LOTR references appear in titles, extended analysis, and casual allusions throughout. This is the single most referenced cultural property.

The Bible and Christian faith

Woven in naturally, never as proselytizing. Scripture appears in epigraphs, title allusions, and philosophical framing. Faith is part of the worldview rather than the subject matter. References include Ecclesiastes, Proverbs, the Gospels, Paul’s epistles, hymns, and the concept of humans as “sub-creators.”

Classic software engineering literature

The Mythical Man-Month (called “The Bible Of Software Engineering”), The Design of Everyday Things, Joel Spolsky, Fred Brooks, Uncle Bob, Donald Knuth, D.L. Parnas.

Music

Pink Floyd (multiple references), David Bowie, Bon Jovi, R.E.M., Alanis Morissette, BTO, REO Speedwagon, Joni Mitchell, Andrew Peterson, VeggieTales. He plays bass and does live audio mixing.

Film and TV

Star Wars, Star Trek, Game of Thrones, The Office, Ted Lasso, Good Will Hunting, Blade Runner, The Princess Bride, The Incredibles, Parks and Recreation.

Philosophy and nonfiction

Blaise Pascal, Confucius, Epictetus, Richard Rohr, Daniel Kahneman, Aristotle, T.S. Eliot, Teddy Roosevelt.

Sports

LeBron James fandom. General sports analogies. San Diego Wave FC.

Board games and nerd culture

Settlers of Catan, D&D, Magic: the Gathering, Minecraft, video game nostalgia.

Recurring Themes

Software as craft

Code quality matters. Simplicity is hard. Delete as much code as you write. The Boy Scout Rule. Understanding what lies beneath your abstractions. “Descend into the particulars.”

Leadership as service

Management is a craft requiring emotional intelligence. Be kind. Ask good questions. Give honest feedback. “Absolutely nothing is more important to your career than being kind.”

Human flourishing through technology

Technology is a means, not an end. The purpose of the work is to serve people. Public sector work matters. “My tools are technology, but they’re not the goal.”

Career as marathon

Long-term thinking. Patience. Consistency. Longevity of sustained greatness over epic individual performances.

Writing and thinking

Writing clarifies thought. Blog as “second brain.” The discipline of showing up to write regularly. Meta-commentary on the act of blogging itself.

Python love

A deep and abiding affection for Python that surfaces everywhere. “As of today, I do not think there is a better general purpose language in existence than Python.”

The interconnected web

Posts constantly reference earlier posts, building a web of cross-linked ideas over time. This self-referential linking is a defining structural habit. Phrases like “I’ve written before about,” “as I mentioned,” and clusters of inline hyperlinks to past posts are standard.

Paragraph Rhythm

  • Short to medium paragraphs: Typically 2-4 sentences. Rarely more than 5-6
  • Single-sentence paragraphs for emphasis: Used frequently as punchlines, openers, or transitions
  • Bulleted and numbered lists: A frequent structural device, reflecting the engineering mindset
  • Alternating rhythm: Medium paragraph setting the scene, shorter paragraph making the point, medium paragraph elaborating, short paragraph landing it
  • No walls of text: Even longer posts are broken up with lists, bold text, and short paragraphs

What NOT to Do When Writing as Jud

  • Do not use flowery or overwrought prose
  • Do not write posts longer than 500 words unless the subject truly demands it
  • Do not lecture from a position of authority without grounding in personal experience
  • Do not use abstract language when a concrete anecdote will do
  • Do not explain technical terms that the audience would know
  • Do not use a descriptive or literal title; always use an allusion, idiom, or cultural reference
  • Do not be cynical, bitter, or mean-spirited
  • Do not proselytize; faith is woven in, not preached
  • Do not write without humor; even serious posts have a wry aside or self-deprecating moment
  • Do not forget the parenthetical asides (they’re essential to the voice)
  • Do not end on a long, formal conclusion; end on a short, punchy line
Unfunded Mandates

Unfunded Mandates

This essay was developed through conversation with Anthropic’s Claude, drawing on dialogue with colleagues whose observations are quoted with permission. The ideas, arguments, structure, and final language are mine. In the taxonomy this essay proposes: Creator mode, reviewed and owned.

Someone sent me a design document recently. It was long enough to require several hours of careful review, yet unmistakably AI-generated and just as clearly unreviewed by the person who sent it. My best guess was that the prompt was written in about five minutes, ten tops.

I was being asked to invest hours evaluating a document its author had invested minutes producing. They weren’t being malicious. They were doing what the tools make easy: generate at volume, ship immediately, and let someone downstream sort it out. But here’s the thing about frictionless production: it doesn’t eliminate the work. It relocates it. When this is done without acknowledgment, what arrives isn’t collaboration. It’s an unfunded mandate for someone else’s cognitive labor.

The Confidence Gap

A friend of mine put the problem this way: AI “allows people who have never even thought of a subject matter to opine as if they were well-versed, while maintaining the same level of comprehension they started with.”

Comprehension stays flat, but confidence soars. And when that confident-sounding output is sent to another person with no indication of how it was produced, the recipient has no way to know how much trust or attention to invest.

We already navigate this intuitively in the analog world. You read a handwritten letter differently from a form letter. You respond to a heartfelt apology differently from a corporate PR statement. In each case you’re calibrating based on how much of the sender invested of themselves in the message.

AI has blown up that calibration. A ChatGPT-generated email looks identical to a carefully composed one. An AI-drafted design doc reads the same as one built through weeks of analysis. When the surface is all you can see, you either give too much attention to content that doesn’t deserve it or you start distrusting everything. Both are bad.

Not All Words Are Equal

Deb Roy, writing in The Atlantic, recently argued that AI has decoupled speech from consequence for the first time in history. When language comes from a system that bears no vulnerability for what it says, the moral structure of language erodes. Promises hollow out, apologies become theater, and nobody stands behind the words because there’s nobody there to stand.

Roy’s got a point. But I think he’s looking for the break in the wrong joint. He sees consequence as something that lives in the speaker. I think it lives in the relationship between sender and recipient, and that relationship hinges not on what produced the words but on what the sender did with them before passing them along.

Also, Roy’s framework also treats all speech as if it carries the same moral weight. It doesn’t. Not all communication requires the same degree of human presence. When sending a personal email to a friend going through a difficult time, the human presence in the words is the entire point. You’re not conveying information. You’re communicating that you cared enough to sit down and find the right words. AI could write something more polished. It would mean less.

Compare that to writing a readme in an open source code repository. Here, the accuracy and clarity of the content is the entire point. Nobody reading the readme cares whether you personally typed every word. They care whether the installation instructions work. I’ve personally had AI write several of these recently. As long as I validate the content, nobody is harmed.

Most communication falls between those poles: a design doc for your team, Slack messages to a direct report, a proposal for a government contract. The right level of human involvement varies for each, and it’s not always obvious where the line falls.

Toward Responsible Disclosure

I propose a simple rule-of-thumb: never ask the consumer to invest more than you did as the producer.

If you spent five minutes generating a document, don’t send it with an ask that requires hours of review. If you haven’t read your own output, don’t ask someone else to read it for you. The effort you put into producing and refining what you send sets the ceiling for what you can reasonably ask of your audience. Violate this, and you’re not collaborating. You’re offloading.

How do you put this into practice? Disclosure.

Think of it as the communication equivalent of open source licensing. A license doesn’t tell you whether a product is good. It tells you what expectations and obligations attach to it. Disclosure does the same: it tells the recipient what kind of social contract they’re entering.

Three questions form the backbone:

What was your role?

In earlier work on AI-assisted creativity, I mapped human-AI relationships to distinct approaches: Author, Muse, Artisan, Debater, Creator, Curator. The same taxonomy applies to communication; when you send something to another person, it’s worth knowing (and disclosing) which mode you were operating in:

  • Author: entirely my words. No AI. Read this as direct human communication.
  • Creator: I developed this with AI assistance. The thinking is mine; AI helped me organize and express it. Read it as authored-with-assistance.
  • Artisan: AI generated a draft. I reshaped and validated it substantially. Read it as human refined.
  • Curator: AI generated this. I selected and organized but didn’t deeply rework it. Read it as a starting point, not a finished product.

Each is legitimate in the right context. What’s not legitimate is sending Curator-level work with Author-level expectations attached.

What have you validated?

“AI generated, I haven’t read it” and “AI generated, I’ve verified the technical claims but the prose is rough” and “AI assisted, but the architecture and recommendations are mine”—these are three very different things. Your reader needs to know which one they’re holding. Say so.

What do you expect from the recipient?

Match your ask to your effort. If you haven’t put in hours, don’t ask for hours. If what you need is a five-minute directional check, say that explicitly, don’t give a vague “please review.”

The person who sent me that document could have written: “I used AI to generate a first-pass design doc based on the requirements we discussed. I haven’t reviewed it in depth yet. Could you skim it and tell me if the general approach is sound before I invest time refining it?” That’s honest and proportional.

Connection Boundary

There’s one area where disclosure isn’t enough, where AI involvement changes what the words communicate, no matter how transparent you are about it: personal correspondence: emails to friends, texts to family, messages of condolence or congratulations or love.

These are acts where the human effort of finding words is itself the gift. When you write to someone who’s grieving, the struggle to say the right thing, the imperfection of what you manage, the fact that you sat with the blinking cursor and tried, that’s what communicates care. A perfectly worded AI-generated sympathy message is, in every sense that matters, less than a clumsy human one. Not because the words are worse. Because the act of writing is absent. Using AI here isn’t labor-saving. It’s a category error, like sending a robot to your friend’s funeral because it would deliver a better eulogy.

Call this dividing line the connection boundary. Below it, on the information-transfer side, AI involvement is a question of degree and disclosure. Above it, on the human-connection side, AI involvement eliminates the thing that makes the communication matter.

This doesn’t mean AI can’t play any role in personal communication. Using it to think through what you want to say, to consider whether your message might be misread, that keeps you in the loop. The line is between using AI to prepare yourself to communicate and using AI to communicate for you. The first is rehearsal. The second is outsourcing connection.

Counterfeit Collaboration

A question worth asking before you send unreviewed AI output to anyone: do you really need the other person’s input before your own review and refinement? Or are you simply avoiding the work?

Sending raw output without oversight likely violates the investment principle on its face. You’re asking someone else to do the thinking you skipped. If you genuinely need a gut check on direction before doing the hard work of refinement, say so explicitly. But this should be a rare exception, not a default workflow. If it’s becoming habit, the tool isn’t saving you time, it’s helping you avoid learning how to evaluate your own work.

And there’s something worse about this pattern than mere laziness. When you send unreviewed AI output and ask someone to “have a look and we can discuss,” you’re wearing the costume of collaboration while gutting its substance. A real discussion about a design or a proposal requires both parties to have done enough thinking to bring something to the table.

The language says partnership. The reality says: I need you to do this for me.

The Risk of Atrophy

Writing is not just a way to record thoughts. It’s a way to have them. The process of drafting, that’s where clarity gets forged: trying to fit a complex idea into a sentence and failing, then trying again. If I’ve learned anything from writing this blog, it’s that the thinking happens in the writing, not before it.

The person who routinely sends unreviewed AI output isn’t just issuing unfunded mandates for other people’s attention. They’re outsourcing their own professional development: losing the capacity to think critically about their domain because they’ve stopped doing the work that critical thinking requires.

Contemplation Is Not Dialogue

Everything above addresses what you owe the person who receives your words. But there’s another problem, a quieter problem, and it’s about what you think you’ve accomplished by the time you hit send.

A philosophically-minded colleague noted that one’s assumptions can be “reflected back in the form of a dialogue when the AI response is actually closer to memory.” Real dialogue, the kind many conceptions of truth depend on, is how we test whether our views hold up against people who see the world differently. Knowing what’s true has a social and ethical component that AI can mimic and support but cannot be.

This matters practically. You have a long, productive-feeling conversation with a chatbot. It pushes back on your reasoning. Offers counterarguments. Helps you refine your thinking. By the end, you feel like your ideas have been stress-tested. But against what? The AI challenged your inferences, maybe capably. What it couldn’t do is challenge your priors with the weight of a different life behind the challenge. It has no competing commitments, no lived experience that diverges from yours, no stake in the outcome. The conversation felt like dialogue, but it was more like structured contemplation.

None of this makes AI conversation worthless. I obviously don’t think that, given that this essay grew out of one. Structured contemplation has real value, and it can help prepare for the real dialogue when it happens. The danger is mistaking the rehearsal for the performance.

Call this the internal version of the investment principle. The external version says: don’t ask your reader to put in more than you did. The internal version says: be honest about what kind of thinking you did. Working through ideas with AI is real work. Defending those ideas to a skeptical colleague who brings different assumptions to the table is different work. Both are useful, but the former is no substitute for the latter.

We’re early in figuring out what human-AI communication actually is. The analogies we reach for—tool, collaborator, ghostwriter, mirror—each grab a piece of it while dropping the rest. Better language will come. Until it does, the investment principle can serve us well: simple enough to apply right now, and honest enough to keep the responsibility where it belongs.

This essay is a companion to a series on AI and creativity: Light From Light, By Their Fruits, Spellcraft, and E Pluribus Plura. Those essays explored frameworks for human-AI creative collaboration. This one extends that thinking into personal and business communication.