HN Debrief

Taste Is All That's Left

  • AI
  • Programming
  • Developer Tools
  • Design
  • Product Strategy

The post says AI has crushed the cost of producing software and prose, so the scarce skill is no longer making things but deciding what deserves to exist and recognizing when a result is wrong even if it is superficially acceptable. In the author’s framing, “taste” is that fast, hard-to-formalize judgment built through friction, repetition, and failed attempts. The strongest discussion signal was that many readers accepted the core premise but rejected the word. They translated “taste” into judgment, discipline, tacit knowledge, architecture sense, or maintainability, and argued that the real bottleneck is still not keystrokes but steering, pruning, and enforcing standards over time. Several commenters grounded this in practice. LLMs are useful for throwaway code, small scoped work, search, classification, and fast iteration, but they still tend to over-explain, over-comment, generate bloated tests, and lose coherence across larger systems. The recurring fear was not that models are useless, but that they make it too easy to converge on average choices and to ship code that works today while quietly raising tomorrow’s maintenance bill.

If you use AI in product or engineering work, treat judgment as an explicit part of the workflow instead of assuming speed is the whole game. Also expect style-level AI suspicion to become a real reputational and communication problem, even for human-written work, so teams need clearer quality standards than “this feels off.”

Discussion mood

Mixed but mostly negative on the essay’s writing style and positive on the underlying concern. People broadly agreed that AI shifts value toward human judgment, but many thought the post itself was verbose, slippery, or suspiciously AI-like, and that fight about authenticity drowned out the thesis.

Key insights

  1. 01

    Average taste is the bigger risk

    The sharper concern is not that models have uniquely bad judgment. It is that they make it effortless to converge on median choices. That flattens implementation style, architecture decisions, and design language toward whatever the training distribution rewards. A few commenters pushed this further and noted that this may be an acceptable trade in routine work, because it frees people to experiment at a higher level. The loss is novelty in how systems are built. The gain is access for people who have ideas but lack a programming background.

    Use AI hardest where standardization is a feature, not a bug. If your advantage depends on unusual architecture, interaction design, or technical style, you need deliberate review points that force non-default choices.

      Attribution:
    • dcow #1
    • base698 #1
    • altmanaltman #1
    • ulrikrasmussen #1
    • jmbwell #1
    • ipsod #1
  2. 02

    Good enough persists because incentives reward it

    LLMs do not need to be good in the abstract to stick around. They only need to be good enough for someone’s incentives. That means throwaway tools, brute-force attempts, quick prototypes, or any environment where cost and speed beat maintainability. The useful analogy was not that the code is excellent. It was that low-quality mass production often wins anyway because it opens new use cases and shifts who can participate. That explains adoption better than claims about superior craft.

    When evaluating AI in your org, separate capability from incentive fit. Ask which work actually benefits from cheap mediocre output and which work becomes more expensive later if you accept it.

      Attribution:
    • pornel #1 #2
    • dwedge #1
    • boron1006 #1
    • nunez #1
  3. 03

    Verbosity is a concrete failure mode

    Several experienced developers named the same operational problem. LLM-generated code tends to over-justify itself. It repeats bug explanations in comments, writes sprawling docstrings, and produces absurdly heavy test fixtures. One commenter argued this comes from weak long-term project memory, so the model keeps restating context that a team would normally compress into shared shorthand. This is not just aesthetic annoyance. It makes codebases slower to read and harder to maintain.

    Put hard limits on comments, docstrings, and test scaffolding in AI-assisted repos. If you do not aggressively compress and prune generated text, the readability tax compounds fast.

      Attribution:
    • datsci_est_2015 #1
    • thinkharderdev #1
    • neerajsi #1
  4. 04

    Markets choose for incentives, not merit

    The author’s suggestion that heavy investment proves LLMs are “good enough” got a strong correction. Commenters pointed out that adoption often reflects capital pressure, labor substitution hopes, and convenience seeking more than technical excellence. Cars versus public transit was the recurring analogy. The winning product is often the one that fits incentives and externalizes costs, not the one that is best for users or society. Applied to AI, that means bad code can spread long before it proves itself durable.

    Do not read market adoption as validation of quality. Build internal measures for reliability, maintenance cost, and security instead of using popularity as a proxy.

      Attribution:
    • notashelf #1
    • agentultra #1
    • KurSix #1
    • pornel #1
    • assimpleaspossi #1
  5. 05

    The scarce skill is saying no repeatedly

    The most grounded version of the “taste” thesis came from people who already use agents heavily. They described the work as repeated refusal. You keep rejecting generic choices, forcing better defaults, and steering toward software that actually works rather than merely demos well. That reframes taste as an active editing loop, not a mystical gift. The important human contribution is not typing faster. It is deciding when an acceptable-looking answer still fails the bar.

    Design AI workflows around review and rejection, not just generation. Make “no, again” a visible step in product, code, and writing processes so quality does not disappear behind speed.

      Attribution:
    • mdwelsh #1
    • devin #1
    • mshafir #1
    • notashelf #1
  6. 06

    Maintenance is still where bad AI shows up

    A repeated point from practitioners was that cheap first drafts do not reduce the cost of understanding, debugging, operating, and evolving software. Vibecoded projects still need constant refinement. Some commenters were blunt that AI codebases fall apart over time, especially when incentives favor token-heavy complexity over simple architecture. The first version may be nearly free. The six-month bill is not.

    Track downstream costs on AI-assisted work over months, not days. If you only measure time to first output, you will overestimate gains and miss the maintenance cliff.

      Attribution:
    • KurSix #1
    • matheusmoreira #1
    • sgt #1
    • socketcluster #1
  7. 07

    The post recycled older aesthetics debates

    A number of readers noted that the essay’s core argument is not new to AI. It sits in a long line of writing on taste, judgment, quality, and aesthetics from Susan Sontag, David Hume, Immanuel Kant, Pierre Bourdieu, Robert Pirsig, and others. That does not make the post wrong. It does make the framing less novel than the headline suggests. The more useful move is to connect AI-era concerns to existing thinking about tacit judgment, social formation of taste, and the gap between rules and sensibility.

    If this topic matters to your team, borrow vocabulary from aesthetics and design theory instead of reinventing it in AI-only terms. You will get clearer distinctions between taste, judgment, consensus, status, and craft.

      Attribution:
    • manlymuppet #1
    • hellojomp #1
    • kimjune01 #1
    • p0nce #1

Against the grain

  1. 01

    Taste is not much of a moat

    A strong minority argued that if competitors can copy your features, UX patterns, and visual language within days, taste is not a durable advantage. At best it gives you a temporary lead and a target for others to clone. Copying is reactive, but reactive may be good enough in commodity markets. This changes the strategic question from “who has better taste” to “what stays defensible once taste diffuses instantly.”

    Do not assume design sensibility alone will protect a product. Pair it with distribution, trust, operational excellence, or domain depth that cannot be copied from screenshots.

      Attribution:
    • madrox #1
    • phito #1
    • dingaling #1
  2. 02

    Taste is too vague to govern systems

    One pointed objection was that “taste” becomes a refuge for claims that cannot be tested. In this view, robust organizations should translate judgment into written tolerances, specs, and governance rather than elevating an unfalsifiable human sense. The criticism lands because AI makes this gap obvious. If a standard cannot be encoded well enough to survive the person who holds it, it may be less a craft insight than an unexamined preference.

    Wherever possible, convert recurring quality judgments into explicit review criteria. If your team keeps saying something is wrong but cannot explain why, you may be missing a spec.

      Attribution:
    • arionhardison #1
  3. 03

    The article had human rhythm, not model rhythm

    Against the dominant suspicion, some readers argued the essay did not have the repetitive sweetness or empty déjà vu of typical model prose. They pointed instead to cadence, paragraph structure, and a rhythm of thought that felt authored. The useful point was not that humans are easy to spot. It was that superficial markers like em dashes are training people to detect the wrong thing.

    If you need to judge AI-written communication, focus on redundancy, semantic drift, and structural sameness rather than punctuation shibboleths. Crude style heuristics will burn both your trust and your signal.

      Attribution:
    • qwery #1
    • kuschku #1
    • HeartStrings #1
  4. 04

    The next scarcity may be embodiment

    One brief but genuinely different pushback rejected the whole premise that judgment is the final human moat. The claim was that the harder-to-replace layer may be embodied experience rather than taste. Even if software generation becomes cheap and evaluative judgment becomes automatable, humans still occupy physical and social contexts that models only simulate.

    Keep an eye on workflows where physical presence, direct observation, or lived context still shape decisions. Those may stay defensible longer than purely cognitive “taste” work.

      Attribution:
    • visarga #1

In plain english

AI
Artificial intelligence, here mainly meaning software models that can generate code, text, or answers from prompts.
Claude
A family of AI models from Anthropic.
LLM
Large Language Model, an AI model trained on large text datasets to generate and analyze language.
Pangram
A commercial tool that claims to detect whether a piece of text was written by AI.
UX
User experience, the overall feel and usability of a product for the people using it.

Reference links

AI detection and authenticity debate

Philosophy and aesthetics references

Books and essays on quality and craft

Software and product examples

  • Pull-to-refresh
    Used as an example in the argument that design ideas diffuse quickly once discovered
  • Filestash
    Shared as a real Dropbox-like project in response to skepticism about building such products
  • fdrive
    Companion desktop sync tool shared in the same Dropbox-clone exchange

AI adoption in major products

Related social posts and analogies