What Gergely Orosz thinks about software quality
Writes The Pragmatic Engineer, the software-engineering newsletter, and wrote The Software Engineer's Guidebook. Formerly an engineering manager at Uber, and at Microsoft/Skype and Skyscanner before that.
Everything they publish, on ppll ↗
Gergely Orosz did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
3 dated positions, 2026, in their own words. Our reading of what Gergely Orosz has said — not written or endorsed by them.
The line under a date shows how recently it was said: empty within a month, full after three years.
-
Their wordsThis is why everyone is rethinking code reviews, deploys, possibly even o11y
- 5 days earlier
-
Their wordsAll of these are things that power users IMMEDIATELY notice and get annoyed. But there's no good way to report them, and the eng teams clearly are flying blind, patting themselves on the back how everything is up velocity-wise... but product quality got degraded! And they don't even know
- 3 days earlier
-
Their wordsOne very interesting thing about code reviews starting to fade in many places
The line under a date fills as the words age, a quarter at a time: past a month, six months, a year, and three years. Empty means said within the last month; full, more than three years ago. It says when, not whether it still holds — a change of mind is marked on the claim itself.
Dashed means we only know the words existed by that date; they may be older.