Joel Auterson "Fuck it, make it anyway" – Reflections on Generative AI and Creative Coding

TL;DR

Joel Auterson’s essay argues that even as generative AI erodes the perceived value of handcrafted code, developers should keep building software and games because the intrinsic joy of creation outweighs market pressures.


The Core Argument

  • Auterson describes a personal “crashout” triggered by the rise of generative AI, which he sees as devaluing the work of programmers and artists.
  • He rejects the notion that using AI assistants is enjoyable; the output feels alien and offers no pride.
  • Auterson outlines three perceived paths for creators:
    1. Adopt AI to stay competitive – but sacrifice enjoyment.
    2. Quit making things – an untenable option for most creators.
    3. Continue the hard way – build tools, engines, and games for the love of the craft.
  • He concludes that the third path is the only one that preserves the spirit of why we make games and software.

Why This Matters to Developers

  • Identity & Motivation – Many developers tie their self‑esteem to the act of writing code. When AI produces the same results with less effort, that identity is threatened.
  • Economic Pressure – AI lowers the barrier to entry, making simple tools and utilities commoditized. Auterson notes that his beloved git‑branch switcher is now a “prompt‑able” product.
  • Skill Erosion – Relying on AI for code generation can reduce deep understanding of language internals, architecture, and problem‑solving.
  • Creative Fulfilment – The essay emphasizes that the process of building (learning, iterating, failing) is the reward, not merely the final artifact.

Community Reactions – Key Themes

“The output doesn’t feel like mine, and I take no pride in what it produces.”obviousdev

This sentiment echoed across the thread, highlighting a loss of ownership when code is AI‑generated.

“I like building apps even more now; AI lets me implement ideas in half an hour.”user43928

A contrasting view: some developers experience a productivity boost and renewed excitement.

“AI is a mean‑reverting tool; it will never create truly novel algorithms.”Aeolun

Reinforces the belief that AI excels at interpolation, not innovation.

“If you love cycling, you won’t ride an e‑bike; similarly, I won’t let AI replace my coding.”sicktriple

Uses an analogy to argue that personal enjoyment trumps efficiency gains.

“The false trichotomy: there’s a fourth option – find joy in a hybrid workflow.”pmarreck

Points out that mixing AI assistance with manual coding can preserve craftsmanship while leveraging speed.

“AI saves tedium, letting me focus on problem‑domain understanding.”abstractcontrol

Suggests that AI can offload boilerplate, freeing developers for higher‑level design.

“The market will shift; we must redefine the intersection of what we enjoy, what we’re good at, and what’s valued.”GMoromisato

Calls for a re‑evaluation of personal value propositions in an AI‑augmented world.


Practical Takeaways for Indie Developers

  1. Define Your Motivation – Ask whether you code for learning, recognition, or problem‑solving. Align your workflow accordingly.
  2. Use AI as a Tool, Not a Crutch – Employ LLMs for repetitive boilerplate (tests, docs) while retaining ownership of core architecture.
  3. Document the Journey – Keeping a personal log (e.g., a blog or repo README) preserves the narrative of how you built something, which remains valuable even if the final product could be generated.
  4. Leverage Community Feedback – Auterson’s experience shows that peer validation (“head pats”) fuels fulfillment; share prototypes early to maintain that feedback loop.
  5. Consider Hybrid Projects – Build a small utility manually, then experiment with AI‑generated extensions to compare quality, speed, and satisfaction.

The Broader Landscape

  • Creative Fields – Auterson notes that visual artists already view AI as “anti‑art,” whereas programmers are still grappling with its impact.
  • Tooling Ecosystem – Engines like Unity/Unreal already encapsulate decades of expertise; AI may accelerate adoption but does not replace the need for design insight.
  • Economic Realities – For solo indie studios, AI can lower development costs, yet the uniqueness of a product often still hinges on human creativity.

Conclusion

Joel Auterson’s essay serves as a rallying cry for developers who feel their craft is being devalued by generative AI. While some community members find AI liberating, many share his concern that the process—the learning, the struggle, the pride—remains essential. The pragmatic path forward is a balanced approach: use AI to eliminate drudgery, but keep the core creative work in human hands. In doing so, developers can preserve both their personal fulfillment and the distinctive quality that only a human mind can impart.

Sources

Related