Developers should embrace creative coding again

Original Article ↗ Hacker News Discussion ↗

Business pressure, utilization, and lost creativity

  • Several comments argue that high “utilization” targets and distrust of employees have squeezed out slack time, which used to support experimentation, quality improvements, and creativity.
  • Queueing theory is cited: maximizing resource utilization (keeping devs 90–100% busy) increases wait times and harms throughput, even ignoring creativity.
  • Many see “Agile” as having degenerated into Taylorism plus dashboards, despite formal agile frameworks warning against overloading teams.

Is programming inherently creative?

  • Some say businesses treat creativity as belonging to UI/UX or “creative roles,” while engineering is seen as mere implementation to be optimized.
  • Others push back: engineering itself is described as deeply creative problem-solving, often more like a craft or trade than pure “execution.”
  • There’s frustration at interview practices focused on algorithms over craft, which reinforces a non-creative view of software work.

Figma, AI, and replacing workers

  • Several comments note the irony of a Figma “developer advocate” urging creativity while working for a company many see as automating away jobs (including developers via AI).
  • Broader point: most developers already build automation that replaces non-developers; some see it as hypocritical to object when automation targets developers.
  • A long tangent debates socialism vs capitalism as responses to job-displacing automation and who benefits from productivity gains.

What “creative coding” the article is actually about

  • Multiple readers initially find the article’s thesis unclear; others summarize it as: “do more digital art/expressive web work using HTML/CSS/SVG and modern browser features, instead of template-driven sameness.”
  • It’s framed as a reaction to the dominance of Wix/Squarespace/Bootstrap/Tailwind-like sameness despite powerful browser capabilities.
  • Critics say the post focuses on “unique design” and shiny CSS features rather than the deeper math/graphics/algorithmic side of creative coding (e.g., Processing, p5.js, demoscene-style work).
  • Some see it as corporate, sanitized “career advice” and subtle marketing for Figma, not a serious exploration of creative coding.

Native desktop vs web apps (big subthread)

  • Many lament the dominance of Electron/web apps and wish for fast, native desktop software that fully uses modern hardware. Examples of snappy native apps are contrasted with sluggish chat/music Electron clients.
  • Others argue the browser is effectively a cross-platform app runtime with good abstractions and sandboxing; rebuilding that natively is costly, especially for multi-platform support and updates.
  • There’s broad agreement that web UI primitives are too limited for rich “full-fat” desktop-style apps; lack of built-in, high-quality widgets leads to many buggy, custom reimplementations and a perception of bloat.
  • Supporters of web apps highlight: centralized updates, better default sandboxing, easy syncing and multi-device access, and organizational simplicity when managing many users.
  • Critics counter that native apps can be sandboxed, synced and tabbed as well, and that web-based distribution shifts control to cloud providers and weakens user control over data.

Tooling, AI, and the creative process

  • One thread argues that to “creatively code” you must genuinely code: relying heavily on AI/IDE assistance can drown out the reflective, exploratory thinking that sparks creativity.
  • Some developers intentionally use simpler editors and minimize AI/docs to “wrestle with the code” and treat programming as a way of thinking out loud.

Crypto, NFTs, and contemporary creative coding

  • Commenters point out that generative-art NFT communities (especially on Tezos) were vibrant centers of creative coding from about 2019–2022.
  • Others admit the scene produced interesting work but say the surrounding greed and hype made them dismissive of it, and question how much of it was real “art.”

UI creativity vs usability and business needs

  • Several participants stress the tension between surprising, delightful interfaces and predictable, learnable ones.
  • For portfolios and personal experiments, “wild” creative sites are celebrated; for corporate or productivity tools, predictability and efficiency usually win, or clients will reject the work.
  • Some frame the author’s call as really about “unconstrained, personal play” with technology—projects that don’t need to justify themselves with business cases.

Template cultures and Tailwind

  • Tailwind is cited as both an enabler of uniqueness (after the Bootstrap era) and an example of convergence: over time a recognizable “Tailwind style” emerged around influential examples.
  • Broader point: tools that can support creativity don’t guarantee creative outcomes; social imitation and familiarity pull designs back toward common patterns.

Fatigue with “you should…” culture

  • One commenter voices exhaustion at constant pressure to learn new frameworks, do side projects, study AI, and treat every hobby as a startup opportunity.
  • This is linked back to the article: the same industry that pushes relentless productivity and careerism is now telling developers to “be more creative” in their off-hours.