# soto-developer-taste-ai-slop-strategizeyourcareer-2026-04

## Veille

Developer Taste Versus Mediocre AI Code — Judgment and Discipline — Hiring for Taste — Software Quality — Substack

## Titre Article

Developer Taste: Separating Good Code from AI Slop

## Date

2026-04

## URL

https://strategizeyourcareer.com/p/developer-taste-ai-slop

## Keywords

developer taste, AI slop, technical judgment, discipline, code quality, mediocre code, hiring, engineer evaluation, AI tools, augmented coding, code review, engineering decisions, critical skills, differentiator, code generation

## Authors

Fran Soto

## Ton

**Profile**: Career-strategy newsletter for software engineers, pedagogical-analytical register, intermediate level.

**Description**: Fran Soto, a software engineer at Amazon, adopts a direct and pragmatic tone, blending field observation with actionable advice. The style is structured, accessible, with punchy phrasing aimed at prompting awareness. Authority comes from his experience at a major tech company and his widely-read Substack newsletter. The target audience is developers and tech managers seeking to understand what distinguishes good engineers in a world where AI generates code on demand.

## Pense-betes

- **Note**: Fiche reconstructed from secondary sources — the site strategizeyourcareer.com blocks automated access (403 error). The points below are drawn from quotes and cross-references found in other articles
- Soto defines « developer taste » as « the judgment to know what the right solution looks like before writing a single line of code — and the discipline to pursue it rather than the first output that compiles »
- « AI slop » refers to code that compiles, passes tests, appears correct on the surface, but makes everyone's next six months harder
- The problem is not broken code, it's broken judgment — the fundamental distinction Soto draws
- Taste reveals itself in what people refused, not in what they built — a reversal of perspective for evaluating engineers
- To detect taste in a developer: ask what they would do differently, what they pushed back on, what they killed early in the process
- When anyone can generate code, the ability to know which code deserves trust becomes the differentiating skill
- The gap between mediocre and excellent is taste — not raw productivity, not coding speed
- AI is a tool that can be used well or poorly; zero effort in directing AI's work = poor work
- This article « kicked off the conversation on taste » in the developer community and was widely cited and reshared
- Paradox identified: no one knows how to hire for « taste », even though it has become the most critical skill

## RésuméDe400mots

In this newsletter article from « Strategize Your Career », Fran Soto, a software engineer at Amazon, introduces the concept of « developer taste » as a foundational skill in the age of AI-assisted coding. His central thesis: the problem is no longer broken code, but broken judgment.

Soto defines developer taste as « the judgment to know what the right solution looks like before writing a single line of code — and the discipline to pursue it rather than the first output that compiles ». This definition articulates two complementary dimensions: discernment (recognizing quality) and personal rigor (refusing the path of least resistance).

The phenomenon he calls « AI slop » — code that compiles, passes tests, appears correct on the surface, but « makes everyone's next six months harder » — represents, in his view, the real danger of the augmented-coding era. This is not a tool problem but a process problem: AI is a tool that can be used well or poorly, and investing zero effort in directing AI's work inevitably leads to poor work.

Soto proposes a reversal of perspective in evaluating engineers. Rather than looking at what a developer built, one should examine what they refused. Taste reveals itself in negative decisions: what was declined, what was pushed back on, what was killed early in the development process. To identify taste in a candidate or colleague, he recommends asking about what they would do differently, the trade-offs they refused, and the solutions they abandoned despite their technical feasibility.

His conclusion is both simple and unsettling: when anyone can generate code, the ability to know which code deserves trust becomes the differentiating skill. The gap between mediocre and excellent is not raw productivity or coding speed, but taste. Yet no one really knows how to hire for this quality — a paradox Soto identifies without claiming to resolve it.

The article had a significant impact within the developer community, « kicking off the conversation on taste » and being widely cited in subsequent discussions on code quality in the AI era, notably in academic articles on « AI slop » as a tragedy of the commons in software development.

## GrapheDeConnaissance

- Fran Soto —a_créé→ goût développeur (CONCEPT, 0.95)
- Goût développeur —est_instance_de→ jugement + discipline face au code (CONCEPT, 0.95)
- AI slop —est_instance_de→ code compilable mais dégradant à long terme (CONCEPT, 0.95)
- Goût développeur —observé_dans→ décisions de refus (CONCEPT, 0.9)
- Fran Soto —recommande→ évaluer ce que les ingénieurs ont refusé (AFFIRMATION, 0.88)
- Fran Soto —affirme_que→ l'écart entre médiocre et excellent est le goût, pas la productivité brute (AFFIRMATION, 0.9)
- Fran Soto —affirme_que→ l'IA générative sans direction humaine produit de l'AI slop (AFFIRMATION, 0.88)
- Goût développeur —est_instance_de→ compétence différenciante à l'ère IA (CONCEPT, 0.92)
- Fran Soto —travaille_chez→ Amazon (ORGANISATION, 0.95)
- Article developer taste —a_créé→ conversation sur le goût dans la communauté dev (CONCEPT, 0.82)
- Fran Soto —affirme_que→ personne ne sait recruter pour le goût développeur (AFFIRMATION, 0.85)

---
Canonical: https://www.thekb.eu/en/fiches/soto-developer-taste-ai-slop-strategizeyourcareer-2026-04/