Sep 6, 2026 · 27 min · 9 segments
Andy recently wrote that product quality is proportional to attention and code quality is inversely proportional to pressure. Is he right?…
But anyway, what happened was I'd had a conversation with the boss at my company, and we'd had a wide-ranging conversation around all the little things that are wrong in our product and just want to get them fixed.
Plus, they're like, are we spending too much time kind of gilding the lily on the core library thing? when actually we've got a load of work to do.
That was the kind of flavor of the conversation.
And it just struck me that you get what you attend to in a product.
If you're making a software product, the way you get it to really feel smooth and right is attention.
You notice it's not quite right, and you fix it.
And then you notice it's not quite right, and you do that like a thousand times, and then it feels smooth and nice, and it works well.
That attention, I would almost say it's care for the product that leads to attention.
And I've heard this a long time ago, many, many years ago, I went to a conference.
Yes, it happened to be a Rust-related conference.
But I went to this conference and they were talking about there's various little Rust crates that someone created and...
They took like a niche idea and just poured the absolute maximum care and attention into this one niche little idea and fleshed it out to be everything that that could possibly be like to the absolute maximum.
And their hypothesis was that throughout the Rust ecosystem, there's lots of examples of this.
And that's one of the reasons it's nice to work.
in the Rust ecosystem is because there's people that have taken the absolute care with the absolute most niche thing and put that attention into it.
And so like, this is a part of that I very much agree with that the more attention and care you put into something, the better that like sort of fit and finish or polish layer will be.
However, I also think that there is probably a point of diminishing returns.
So that might be just because like I'm thinking more in like a business context, because that's what I've been working in lately, but...
In my opinion, there is like that definite diminishing returns level where like you have to ask yourself or at least ask your like your department or whatever it is that should we stop? At what point do we stop? And that I don't think is such an easy answer.
I've been having thoughts about quality more generally and thinking about successful companies, not just Apple when it was doing high quality stuff, but a lot of companies that make a lot of money do it because they're really good at something.
They really, really pay attention, that's that word again, to doing an excellent job, a high quality job of managing inventory, and that makes them profitable.
And so maybe there's no limit on quality.
Maybe you should take quality as far as you can.
Maybe, but I would say like for a supermarket that is, you know, a much larger scope than some little niche offering or let's say in the same vein, like some tiny little store that offers, you know, one particular product.
But anyway, what happened was I'd had a conversation with the boss at my company, and we'd had a wide-ranging conversation around all the little things that are wrong in our product and just want to get them fixed.
Plus, they're like, are we spending too much time kind of gilding the lily on the core library thing? when actually we've got a load of work to do.
That was the kind of flavor of the conversation.
And it just struck me that you get what you attend to in a product.
If you're making a software product, the way you get it to really feel smooth and right is attention.
You notice it's not quite right, and you fix it.
And then you notice it's not quite right, and you do that like a thousand times, and then it feels smooth and nice, and it works well.
That attention, I would almost say it's care for the product that leads to attention.
And I've heard this a long time ago, many, many years ago, I went to a conference.
Yes, it happened to be a Rust-related conference.
But I went to this conference and they were talking about there's various little Rust crates that someone created and...
They took like a niche idea and just poured the absolute maximum care and attention into this one niche little idea and fleshed it out to be everything that that could possibly be like to the absolute maximum.
And their hypothesis was that throughout the Rust ecosystem, there's lots of examples of this.
And that's one of the reasons it's nice to work.
in the Rust ecosystem is because there's people that have taken the absolute care with the absolute most niche thing and put that attention into it.
And so like, this is a part of that I very much agree with that the more attention and care you put into something, the better that like sort of fit and finish or polish layer will be.
However, I also think that there is probably a point of diminishing returns.
So that might be just because like I'm thinking more in like a business context, because that's what I've been working in lately, but...
In my opinion, there is like that definite diminishing returns level where like you have to ask yourself or at least ask your like your department or whatever it is that should we stop? At what point do we stop? And that I don't think is such an easy answer.
I've been having thoughts about quality more generally and thinking about successful companies, not just Apple when it was doing high quality stuff, but a lot of companies that make a lot of money do it because they're really good at something.
They really, really pay attention, that's that word again, to doing an excellent job, a high quality job of managing inventory, and that makes them profitable.
And so maybe there's no limit on quality.
Maybe you should take quality as far as you can.
Maybe, but I would say like for a supermarket that is, you know, a much larger scope than some little niche offering or let's say in the same vein, like some tiny little store that offers, you know, one particular product.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.