[baq]

it isn't gospel, it's perspective. if you care about the code, it's obviously bonkers. if you care about the product... code doesn't matter - it's just a means to an end. there's an intersection of both views in places where code actually is the product - the foundational building blocks of today's computing software infrastructure like kernels, low level libraries, cryptography, etc. - but your typical 'uber for cat pictures' saas business cares about none of this.

[Alex_L_Wood]

If you care about the product, you double-so-much care about code correctness and the alignment with the expectations of the stakeholders.

[hvb2]

So you're an auto maker, you say you can care about your product but not care how is built?

If you're building for the cheapest segment of the market, just maybe. Anything else is a hard no imho

[baq]

Yes? If you’re an auto factory, you might care, but an auto maker cares about minimizing cost and maximizing revenue within the regulatory constraints. Nowhere is there a requirement to care about how the car is built, there are requirements on what the car can and cannot do.

[slopinthebag]

Caring about the requirements on what the car can and cannot do sounds suspiciously like caring about how it's built when you consider how it's built directly impacts what it can and cannot do.

[baq]

Not al all, it’s what vs how, completely different beasts. How is for engineers to solve, but the business sells the what.

[hvb2]

Branding is a thing, you know. Especially if you want to sell the high margin cars.