Adam Tornhill
where else to find them
website:https://adamtornhill.com
github:adamtornhill
linkedin:adam-tornhill-71759b48
speakerdeck:adamtornhill
instagram:gotocph
what they talk about
all 9 in the filters
where they keep going back
- Øredev4 editions2018–2025
- GOTO Copenhagen2 editions2015–2022
- Jfokus2 editions2019–2021
all 20 in the filters
on a stage with
- Markus Borgonce
who talks about the same things
- Michael Feathers23 talks
- Angie Jones54 talks
- Victor Rentea45 talks
- Sarah Mei24 talks
- PJ Hagerty26 talks
- Chelsea Troy9 talks
| title | conference | date |
|---|---|---|
| Agentic AI Coding Practices for Speed with Quality | AI-fokus 2026 | 2026-05-19 |
Claims that production work is fully agentic with 100% production code written by agents while measuring roughly 2–3x faster task completion. Independent… | ||
| Code Rot at Machine Speed: Preventing AI-Induced Technical Debt | Øredev 2025 | 2025-11-05 |
AI-generated code often arrives fast but fragile — a Copilot example adds ~20 lines in 40 seconds and shows deep nesting, missing exception handling and… | ||
| Transforming Software Evolution: Lessons from 10 Years of Clojure in Production | Øredev 2025 | 2025-11-05 |
Ten years of Clojure powering CodeScene produce concrete outcomes: Erlang prototype runs in two weeks vs two months in Java and uses 25% of the lines of code… | ||
| Accelerate Code Quality in the AI Age | Øredev 2024 | 2024-11-06 |
Data come from 100k AI refactorings and a benchmark that shows LLMs almost always produce syntactically valid code but only objectively improve code about one… | ||
| Treat Your Code as a Crime Scene | SREcon24 Europe/Middle East/Africa | 2024-10-29 |
Argues that version‑control data plus behavioral analysis (the CodeScene tool) reveal where to spend effort: hotspots are typically 1–3% of code but drive most… | ||
| The Code Quality Advantage How Empirical Data Shatters the Speed vs Quality Myth | Code Quality Conference 2024 | 2024-06-27 |
Empirical analysis ties a 25-factor code health (25 factors) metric to business outcomes: unhealthy files correlate with 42% waste of developer time, green… | ||
| The Code Quality Advantage: How Empirical Data Shatters the Speed vs Quality Myth | Voxxed Days Zürich 2024 | 2024-03-07 |
Empirical study of millions of files across 14 languages shows a file-level Code Health metric (green/yellow/red) derived from design, function and… | ||
| Code Red: The Business Impact of Code Quality | YOW! Perth 2023 | 2023-09-11 |
Claims that poor code causes measurable business harm with evidence: analysis across commercial repositories in 14 languages links a 25-factor code health… | ||
| Code Red: The Business Impact of Code Quality | Craft Conference 2023 | 2023-05-18 |
Code quality metrics map to business outcomes: empirical analysis of 39 companies and millions of lines across 14 languages shows developer time loss of 23–42%… | ||
| Code Red: The Business Impact of Code Quality | YOW! Melbourne 2022 | 2022-12-08 |
Large-scale measurements tie code quality to business outcomes: automated analysis of Git and Jira data across 39 companies and 14 languages uses CodeScene… | ||
| Code Red: The Business Impact of Code Quality | YOW! Melbourne 2022 | 2022-12-08 |
CodeScene-backed analysis shows organizations waste ~23–42% of developer time to poor code; red code modules are twice as slow to change, up to an order of… | ||
| Code Red: The Business Impact of Code Quality | GOTO Copenhagen 2022 | 2022-10-03 |
Research using CodeScene on 49 commercial codebases (14 languages) ties a concrete business impact to a green code is >2x faster claim: modules scored green… | ||
| Prioritizing Technical Debt as If Time & Money Matters | GOTO Amsterdam 2022 | 2022-06-12 |
Shows how version-control mining plus static probes turns vague technical debt into actionable priorities: uses hotspot analysis on Android’s ~3M LOC platform… | ||
| Code & Homicide: What Software Devs (..) from Offender Profiling | ElixirConf EU 2022 | 2022-06-09 |
Claims that 23–42% of developer time is wasted to technical debt and that static metrics alone are not actionable lead to a practical alternative: using… | ||
| Prioritizing Technical Debt as if Time and Money Matters | DevBreak 2021 | 2021-09-08 |
Argues technical debt becomes actionable by mining version control to find hotspots, combining change frequency with code health metrics to prioritize work… | ||
| Prioritizing Technical Debt as if Time and Money Matters | Jfokus 2021 | 2021-02-09 |
A methodical claim: version-control history plus simple complexity metrics expose where refactoring pays off. Uses a hotspot visualization on Android’s 3M‑LOC… | ||
| A Crystal Ball to Prioritize Technical Debt | Agile India 2020 | 2020-10-11 |
Claims that version‑control behavior pinpoints where technical debt matters, not raw static metrics; shows a static tool reporting “4,000 years” of debt on a… | ||
| Meet The Social Side of Your Architecture | Agile India 2020 | 2020-10-11 |
Argues that invisible organizational structure causes defects and delays and gives concrete ways to measure it: compute fractal figures from git by aggregating… | ||
| Prioritizing Technical Debt as if Time & Money Matters | GOTOpia Europe 2020 | 2020-09-15 |
This presentation was recorded at GOTOpia Europe 2020. #GOTOcon #GOTOpia
http://gotopia.eu
Adam Tornhill - This best-selling author and TEDx speaker will… | ||
| Arch. App: Prioritizing Technical Debt as if Time and Money Matters | 4Developers 2020 | 2020-09-14 |
Claims version-control data reveals where to spend effort, using a hotspot analysis that flags high-change, large modules and a hotspot x-ray that drills to… | ||
| Prioritizing Technical Debt as if Time and Money Matters | GOTO Chicago 2020 | 2020-04-27 |
Uses version-control mining and a hotspots visualization to prioritize real maintenance work rather than counting generic debt years. Applies Codesin and the… | ||
| Psychotherapy for Code | Øredev 2019 | 2019-11-06 |
Gives concrete techniques and data: version-control hotspots and change-frequency graphs that reveal a power-law distribution across ~250–300 codebases, a… | ||
| Meet the Social Side of Your Architecture | KanDDDinsky 2019 | 2019-10-17 |
Argues that version-control data reveals hidden organizational faults using fractal figures and a normalized 0–1 team-coupling metric to detect modules with… | ||
| Guide Refactorings With Behavioral Code Analysis | Jfokus 2019 | 2019-02-04 |
Uses version‑control history to find high‑impact refactor targets: hotspots where large modules change often (Android’s activity manager service is 20k LOC… | ||
| Beyond Conway's Law: Meet the Social Side of Your Code | Øredev 2018 | 2018-11-19 |
Software projects often mistake organizational problems for technical issues and treat the symptoms instead of the root cause. The main reason is that the… | ||
| Treat Your Code as a Crime Scene | GOTO Chicago 2016 | 2016-05-23 |
Uses version control as a behavioral log to map developer movement onto a CodeCity-style geography, then finds hotspots = complicated code worked on often by… | ||
| 7 Secrets of Maintainable Codebases | GOTO Stockholm 2016 | 2016-05-09 |
Argues that Version Control behavioral data surfaces the real maintenance targets: a power‑law of change concentrates most work in 3–6% of files, hotspot… | ||
| Treat Your Code as a Crime Scene | GOTO Copenhagen 2015 | 2015-10-05 |
Uses git commit history and CodeCity-style maps to find hotspots (complex + frequently changed) in a 400,000‑line codebase where 4% of files account for 72% of… | ||
| Beyond Code: Repository Mining with Clojure | EuroClojure 2015 | 2015-06-25 |
Shows a Clojure tool, codat, that mines VCS history with a pipes-and-filters pipeline to find actionable hotspots (one case: 4% of the code causes 72% of… | ||
| nothing matches | ||