Tag: Ownership

By Their Fruits: Approaches to AI Creativity

By Their Fruits: Approaches to AI Creativity

In Light From Light I proposed several frameworks for understanding human-AI creative work: the Reversed Muse, Co-Creation, and Sub-Creation. Each offered a different account of who contributes what and how the pieces fit together. I leaned toward Sub-Creation as the most illuminating, borrowing from Tolkien the image of derived creativity, light passing from source to prism, then reflected further.

But there’s a problem with frameworks: they describe. They tell you what might be happening. They don’t tell you what to do.

The more I’ve sat with these ideas, the more I’ve come to think that what we’re really talking about isn’t models at all, but approaches. A model claims to capture reality; an approach is a choice about how to work. And different users, different projects, different moments within a single project might call for different approaches entirely.

This essay is about making that choice. Not which framework is theoretically correct, but which approach fits what you’re trying to do and who you’re trying to be while doing it.

The Questions Before the Choice

Before selecting an approach, you need to know what matters to you. This sounds obvious, but it’s easy to skip. Many people adopt whatever approach feels natural or default, without asking whether it serves their actual goals.

Here are the questions I think matter most:

Where must the ideas originate?

Some users feel strongly that the generative spark must be theirs. The concepts, the directions, the “what if we tried this” moments need to come from their own mind, or the work doesn’t feel like theirs. For these users, AI contribution at the idea level feels like contamination.

Others are delighted by AI-generated possibilities they wouldn’t have conceived. The surprise is part of the pleasure. They’re happy to receive ideas from anywhere, as long as they’re the ones deciding which ideas to pursue.

This is perhaps the most fundamental divide. Everything else follows from it.

How important is craft development?

Some users are trying to get better. They want the struggle of finding the right word, structuring the scene, solving the problem. The difficulty is formative; it’s how they grow. For them, AI that removes the struggle removes the point.

Others have already developed their craft through years of practice, or they’re working in a domain where craft development isn’t their goal. They’re not trying to become better writers; they’re trying to produce a specific piece of writing. The efficiency AI offers is welcome because the struggle would be merely obstructive, not formative.

What must the final product feel like?

Some users need to look at the finished work and feel, without reservation, “I made this.” Any significant AI contribution to the final form undermines that feeling. Even if readers can’t tell the difference, they would know, and knowing would diminish the achievement.

Others are comfortable with more distributed authorship. They might think of themselves as directors or curators rather than sole makers. What matters is that the work is good and that their vision governed its creation, not that every sentence passed through their fingers.

Are you optimizing for the work or for yourself?

This is a subtle one. Sometimes you’re trying to produce the best possible output: a deliverable, a gift, a story that needs to exist. Sometimes you’re trying to have a particular kind of creative experience, regardless of what it produces.

These can align, but they can also conflict. The approach that produces the most polished output might not be the approach that gives you the most satisfaction, or teaches you the most, or feels the most meaningful.

What’s your relationship to friction?

Some people find creative friction enlivening. The resistance of the material, the problem that won’t solve easily, the draft that isn’t working—these challenges engage them. Removing friction would flatten the experience.

Others find friction mostly exhausting. They have limited creative energy, and they’d rather spend it on the parts of the process they enjoy. Friction in the wrong places just depletes them before they get to the good stuff.

There’s no right answer here. But knowing which kind of person you are helps you choose an approach that fits.

The Landscape of Approaches

With those questions in mind, let me map out the approaches I see as genuinely distinct. Each is named for the role the human plays, since this essay is about your choice of creative identity. But the AI’s role is equally important, and I’ll name that too.

This isn’t exhaustive. People will invent new approaches as the technology evolves. But it covers the main territory.

The Author

In this approach, you do all the generative work. Every word, every idea, every creative choice is yours. The AI never generates content; it only responds to what you’ve created, serving as the critic: identifying weaknesses, suggesting directions for revision, calling out your habitual mistakes.

This is the familiar author/editor relationship, extended and accelerated. You give the AI strict boundaries: no suggestions, no alternatives, no creative contributions of any kind. Its sole function becomes diagnosis: identifying where sentences falter, where habits have calcified, where the prose has grown slack. Constraint becomes the source of development.

This method preserves complete generative ownership. The ideas are yours; the craft is yours; the sentences are yours. AI accelerates your development without substituting for your effort. It’s the approach most compatible with a purist stance on creative authorship.

It’s also potentially the most demanding. You have to do all the generative work yourself. The blank page is still blank until you fill it.

The Muse

Here you are the sole source of creative content and AI is purely a vessel for execution. You know exactly what you want; you use AI to produce it efficiently. No dialogue, no curation, no friction, just translation of intent into output.

In this approach, AI serves as the instrument: a tool that channels your vision into form, contributing nothing of its own. This is the Reversed Muse concept in its purest expression. In the Greek model, the poet was a pass-through for divine inspiration; here, the AI is a pass-through for human vision. All the creative substance originates from you.

This method is probably most common in professional and commercial contexts where the creative decisions have already been made and what’s needed is execution at scale. It’s the approach most likely to produce what critics call “AI slop” when done poorly, but when done with clear intent, it’s simply efficient production.

The Artisan

With this approach you contribute the surface while AI contributes structure. You might use AI to outline, to work through plot logic, to identify what scenes are needed and in what order. But the actual prose, the final form, is entirely yours.

Here AI serves as the scaffolder: building the framework on which you craft the finished work. This separates the architectural and decorative elements of creative work. The blueprint might be collaborative; the building is yours.

For writers who find structure-work tedious but prose-work joyful, this lets them spend their energy where they want to spend it.

The risk is that structure isn’t neutral. The scaffold shapes what can be built on it. If AI determines your story’s architecture, it’s influencing the final work more than a surface-level read might suggest.

The Debater

This is the most confrontational method. You deliberately prompt for outputs that conflict with your instincts, then work with or against the tension. You strengthen your creative convictions through opposition.

In this approach, AI serves as the adversary: a source of productive friction rather than assistance. A writer might ask the AI to argue for a plot direction they’ve rejected, to see if there’s something in it they missed. Or prompt for a style completely unlike their own, then figure out what to steal from the contrast. The AI isn’t helping you do what you want; it’s challenging what you want, forcing you to defend or refine or abandon it.

Inviting opposition is demanding. You have to be secure enough in your vision to benefit from challenges rather than being derailed by them.

The Creator

I described this approach in Light From Light, now named for its central relationship. You provide vision, direction, and judgment. You shape, accept, reject, redirect. The final work emerges from dialogue, but you remain the governing intelligence throughout.

AI serves as the sub-creator: generating in response to your vision, doing genuine creative work that is nonetheless derivative of and subordinate to your intent. This naming completes the framework from the first essay. Just as humans are said to bear the imago Dei and sub-create in response to divine creativity, AI bears the image of humanity and sub-creates in response to human creativity. Creator and Sub-Creator, light passing down the chain.

The key distinction from pure generation is active shaping. You’re not accepting whatever the AI produces; you’re in constant conversation with it, treating its outputs as raw material for your vision.

This method allows for AI contribution at the generative level while preserving human authorship at the vision level. You might not have written every sentence, but you decided what the work would be and shaped it until it matched that decision.

The Curator

Finally, in this approach your primary role is selection rather than generation or shaping. You prompt for abundant options, then choose among them. Your authorship lies in judgment: knowing which outputs are good, which serve the project, which to keep and which to discard.

AI serves as the generator: producing abundance for you to sort through. This is more hands-off than creation. You’re not in constant dialogue, shaping each output; you’re evaluating a collection and picking what works.

Curation can be a legitimate creative act. Editors, DJs, and anthologists all create through selection. But it requires accepting that the generative work happened elsewhere, even if your judgment determined what survived.

A Final Approach

There is a seventh possibility that falls outside this framework: the human who initiates and walks away. You might call it the initiator: like a deist God who sets the universe in motion and then withdraws, the human provides a premise or brief, and the AI executes, producing a complete work. The human accepts whatever emerges.

This is where sub-creation breaks down. In all six approaches above, the human remains present as creative intelligence: shaping, selecting, critiquing, defending, or at minimum dictating with precision. The relationship persists. But here, the relationship ends at the prompt. The AI isn’t sub-creating in response to ongoing human vision; it’s simply executing a commission unsupervised.

This has legitimate uses. Professional contexts sometimes call for acceptable output at speed, and not every piece of writing needs a human soul behind it. But it’s also the source of what critics call “AI slop”: generic, undistinguished content that feels like it came from nowhere and is going nowhere. The difference between the initiator done well and done poorly is the quality of the initial brief and the human’s willingness to reject output that doesn’t meet the standard. But even at its best, it’s delegation rather than creation.

If you find yourself working this way, it’s worth asking: is this a choice, or a drift? The six approaches above all require presence and intentionality. The initiator approach requires only a prompt and acceptance. Sometimes that’s appropriate. But if you started out wanting to make something that feels like yours, this probably isn’t the path.

Mapping Your Answers to Approaches

Let me offer a rough mapping, based on how you might answer the questions I posed earlier:

If ideas must originate from you: The Author approach is your clearest fit. The Debater might also work, since it uses AI to test your ideas rather than generate them. Avoid The Curator, which depends on AI generation.

If craft development is paramount: The Author approach again, or The Creator with deliberate constraints (e.g., “give me feedback on this passage, then let me rewrite it myself” rather than “rewrite this passage”). The Artisan could work if you consider prose-craft the real skill you’re developing. Avoid The Muse, which prioritizes output over formation.

If the work must feel completely yours: The Author or The Artisan, depending on whether structure feels like “yours” to you. Some writers consider the prose the real work and don’t mind AI-assisted structure; others feel the opposite.

If you’re optimizing for output quality: The Creator or The Curator might serve you best, depending on your taste and judgment. Both leverage AI generation while applying human quality control.

If you have high friction tolerance: The Author, The Creator, or The Debater. These approaches maintain difficulty and demand active engagement.

If you have low friction tolerance: The Curator, The Artisan, or The Muse. These approaches reduce the parts of creative work that might deplete you, letting you focus energy where it matters most to you.

Approaches Can Change

Nothing says you must pick one approach and stick with it.

Within a single project, you might start as The Artisan (letting AI help you figure out structure), move to The Creator (working through the draft in conversation), and finish as The Author (getting feedback on your polished version). Different phases call for different relationships.

Across projects, you might use different approaches for different purposes. A personal creative work might demand The Author approach because ownership matters to you. A professional deliverable might warrant The Muse for efficiency because what matters is the output, not your creative development.

Over time, your approach might evolve as you do. A novice might benefit from more AI involvement while learning; a master might use AI more sparingly, or in more targeted ways. Or the reverse: someone might start dependent on AI and gradually wean themselves toward greater independence as their skills develop.

The key is intentionality. Know which approach you’re using and why. The worst outcomes come from unconscious defaults, drifting into whatever the technology makes easy without asking whether easy is what you want.

What This Doesn’t Resolve

This framework for choosing approaches helps clarify options, but it doesn’t resolve all the hard questions.

It doesn’t tell you whether the different approaches produce work of different quality. Maybe The Author produces more distinctive work and The Muse more generic, on average. Or maybe the difference is illusory and only the individual work matters. I don’t think we have enough evidence yet to say.

It doesn’t tell you what obligations you might have to disclose your approach. If a reader would care whether a book was Author-assisted versus AI-generated, do you owe them that information? The answer might depend on context, genre, and evolving social norms.

It doesn’t tell you how AI-assisted work should be received by literary culture. Will there be separate categories, separate prizes, separate canons? Or will everything blend together once the technology becomes ubiquitous enough?

And it doesn’t tell you how to execute on your chosen approach: what specific practices, prompts, and disciplines make each approach actually work. That’s the territory for the next essay.

The Maker’s Choice

What I can say is that the choice is real and it’s yours.

The technology doesn’t determine how you use it. You can use a generative AI to never generate. You can use an obedient tool to create productive friction. You can use a limitless content engine to make something that’s irreducibly yours.

The frameworks from Light From Light matter because they help you understand what might be happening in different approaches. But understanding isn’t the same as choosing. And choosing isn’t the same as doing.

If you’re a creator working with AI, or considering working with AI, my suggestion is this: sit with the questions in this essay before you sit with the technology. Know what you’re trying to protect, develop, or achieve. Know what kind of creative experience you want to have, not just what output you want to produce. Know what would make the work feel like yours, and what would make it feel like something else.

Then choose an approach that serves those answers. And if it stops serving them, choose differently.

The light refracts onwards. What it becomes depends on you.


This is the second essay in a series on AI and creativity. The first, Light From Light, examined theoretical frameworks. The next will explore practical implementation: how to actually execute on the approaches described here.

They Who Pass The Sentence

They Who Pass The Sentence

That feeling when I run terraform apply in production:

Thankfully I’ve never had an outcome quite this dire, but I’ve seen databases go up in smoke, amongst other infrastructure-as-code disasters. Tread lightly!

Headquarters (Part 3)

Headquarters (Part 3)

Just when you thought there couldn’t be more (oh trust me, there’s more), here’s comes another round of my series on computer setups (earlier posts are here and here).

Years: 2005-2010
Machine: The box in the closet from my last post but with a snazzy new LCD monitor (my first flat panel), wireless peripherals, and my wife’s great-grandmother’s writing desk.
What I was doing: writing daily on Xanga; applying to family camp; traveling to Tennessee to watch Revenge of the Sith with a high school friend; hosting LAN parties for Age of Empires III; traveling a lot for work.

Years: 2006-2007
Machines: A plethora of cast-off parts coalesced into a couple functional boxes in the garage.
What I was doing: running a NAS for storing all my media; trying to get Gentoo Linux to compile; realizing that running a bare web server on the Internet is asking for trouble.

Years: 2008-2010
Machines: A beefed up HTPC rig in a rackmount case with a whole bunch of amps to power my Magnepan speaker system, plus the plethora of beige boxes from before, but better arranged.
What I was doing: shivering in the garage when using this desk in the winter, listening to Comfortably Numb at peak volume, hosting movie-watching parties.

Year: 2011
Machines: Same rack mounted setup, but relocated from our old garage in Ohio to a closet in our new garage in San Diego, plus a random beige box (those just won’t go away).
What I was doing: Playing with some audio recording gear; streaming Game of Thrones; stocking up on printer paper, apparently.

Years: 2012-2014
Machines: Moved inside, and rebuilt the guts from the rack mount case into a traditional one (albeit black and silenced), also got my first Mac laptop (from which I’ve never looked back).
What I was doing: writing election software; creating hand-made guitar effect pedals (that were terrible); developing back problems thanks to a crummy chair.

Headquarters (Part 1)

Headquarters (Part 1)

Here begins my catalog of all the computer setups I’ve had to date (hopefully more visually appealing than this overview I wrote in 2017). Today’s installment: childhood and teens.

Years: 1983-1987
Machines: TI-99/4A
What I was doing: playing cartridge games like Parsec and Munch Man; writing BASIC programs that could test your knowledge of addition and print ASCII art.

Years: 1988-1995
Machines: Three successive Tandy computers: 1000 TL/2 (the only picture I could find from this time), a 386, and a 486
What I was doing: Writing small QuickBasic, C, and Pascal programs; memorizing powers of 2 and digits of Pi; playing Battle Chess and Where in the World is Carmen Sandiego.

Years: 1996-1997
Machines: Custom-built Pentium 2 bought from a computer-fest convention type thing
What I was doing: Discovering online stuff like a local BBS and then the Internet; learning how to assemble computers from parts (shoutout to NewEgg); optimizing my AUTOEXEC.BAT and CONFIG.SYS files so I could play Doom.

(Unfortunately I don’t have any pictures I could find of my college dorm room setups but they were suitably epic, especially junior year which had 3 full workstations and a console game station)

Years: 1998-2000
Machines: Whatever Cedarville supplied (but it was cool that they supplied desktop PCs!); a home-cooked box I cobbled together with parts scrounged from my job at The Hackery.
What I was doing: Breezing through college programming classes in C++, Java, and VisualBasic; optimizing programs that generate interesting integer sequences; playing Diablo and Age of Empires II.

Ticking Away The Moments

Ticking Away The Moments

Nine years ago today I started this blog with a post that laid out my intentions in creating it. It’s cliché, but true, that a lot has changed in the intervening (near) decade, but for the most part, I think I’ve hewn pretty closely to the original idea, even if my underlying motivations have shifted.

Like many things worth doing, it took some time to find a good rhythm. After two initial posts I went almost 2 years without writing anything. Had a great streak going in 2017, but sputtered out in 2018 and didn’t get going again until early 2020. Since then, though, I’ve been on a roll. Maybe it was turning 40? Maybe it was COVID? Can’t say for sure, but I’ve been happy with my consistency since then (and a growing readership is nice too).

In other wistful, “how time flies!” type subject matter, my youngest kid left for college this past weekend and my oldest starts her junior year with a new location and major. They’re both gonna crush it, I have no doubt.

Time Traveling

Time Traveling

A common rhythm of my career is to catch-up on emails over the weekend. I’ve been appreciative of scheduled send, so that folks don’t get an email from me during non-working hours and assume they need to respond immediately.

However, this might be a new record: 14 emails queued up to go out first thing Monday.

That total may go up depending on how much progress I make on one additional task, which subsequently depends on what Olympic events are on TV this afternoon.

I get that weekend work isn’t for everyone, but I don’t mind it. It’s quiet. Usually no new tasks come up, so I can meaningfully shorten the queue. And finally, it helps alleviate pressure during the week. I’m much more comfortable signing off for the day come Friday afternoon knowing I can knock out a few lingering tasks before Monday ramps up.

Not An Option

Not An Option

A big oops happened this weekend, and it has me thinking about failure. It’s a topic I’ve talked about before, but there’s plenty more that can be said.

Common leadership advice is to avoid making failure out to be a bad thing. “Failure is good,” well meaning folks will say. They’re not completely wrong, but they’re not absolutely right either.

Failure can only be good in moderation. Of course repeated failure of the same kind is bad. Absolutely learn from mistakes so they’re not repeated. But continually making new kinds of failure isn’t great either. No endeavor, professional or personal, can sustain that.

Eventually there need to be successes to offset the setbacks. So I’m not keen on over-celebrating failures, or treating failure as something that ought not have consequences. Maybe in the case of this CrowdStrike fiasco no one deserves to take the blame? But I doubt it.

Confessional

Confessional

What they say: “I want to be respectful of your time.”

What they mean: “I’m tired of this conversation and want it to end.”

And by “they” I mean “me”.

One Day Closer

One Day Closer

My dad died ten years ago today. Hard to believe it’s been a decade, but time marches on no matter our feelings.

I’ve written about him before: how his early investment in a home computer forever altered the course of my future, how his prodding to my shy teenage self got me my first job (and a wealth of early life lessons), and how his constant encouragement became the bedrock of my sense of self.

But today I was reminded of something else he modeled: the value of just showing up. The man bent over backwards to be at every little league game, every band concert, every academic awards banquet, and so much more, usually with video camera in hand.

I’m not as good at it as he was, if I’m honest. But it’s an ideal I strive for, both personally and professionally. Do what you say you’ll do, be where you say you’ll be, pay attention, be engaged. There are no small things.

(Oh, and yes, I am wearing a Star Wars tie at my high school graduation, thanks for noticing!)

Artifactory

Artifactory

The other day I scanned and posted a gift I’d gotten from some co-workers. When leafing through the folder it was in, I found a few other fun artifacts I thought I’d share:

First, a certificate I got from my fourth grade teacher. It’s an objective I still aim for:

And second, an invite I got for helping support the underlying voting platform:

I’ve tried to do a better job recently of documenting my career experiences, not just the work-related items, but the fun stuff too. This week wasn’t so bad, even if the town isn’t my favorite: