Munro and Associates is the firm that does this kind of analysis in the automotive industry.
It's really fascinating. For the record, it would be hard to produce a design that Munro couldn't find something to talk about, good or bad. They employ extremely gifted engineers with a ridiculously large amount of experience at doing this exact task.
As a software engineer, I wish there were an equivalent firm in the industry that did teardowns like this so that we could, as an industry, improve over time the way that the automotive industry does.
I feel like it may be one of the factors holding software engineering back from achieving true professional engineering standardization.
> As a software engineer, I wish there were an equivalent firm in the industry that did teardowns like this so that we could, as an industry, improve over time the way that the automotive industry does.
I think this thread is a good indicator of why that might never happen. People in software will argue with whatever stuff they can and try to refute a review/teardown - reviewer doesn't understand the design consideration, reviewer don't have numbers, the stuff is revolutionary etc etc.
>As a software engineer, I wish there were an equivalent firm in the industry that did teardowns like this so that we could, as an industry, improve over time the way that the automotive industry does.
There are quite a lot of security companies that reverse engineer other software products and publish their findings. It would be good to see that for non-security stuff too.
I feel like you get a flavor of this for software by reading the mailing lists in the more mature open source project, you can basically get a continuous flow of analysis and build or rebuild. It's not packaged in a nice episodic report form, but you can get a little of that too with some projects.
For the software industry as a whole, the closest thing might be the SEI[1], but that body of work takes some effort to work through, perhaps suffering a bit from a more adademic roots vs a more industry engineering info exchange approach like M&A. For that you might have specialist areas, for example, the Jepsen tests and blog[2].
The comment below has some questions for you. This is all information you would have provided if you actually knew what you were talking about. The fact that you didn't leads me to think you are a troller who just likes to say things that make people angry.
I don't know if you're trolling or what, but the truth is interesting. None of the US domestic automakers buy reports from Munro. They sell information to Japanese, Korean, Chinese and European automakers.
It's really fascinating. For the record, it would be hard to produce a design that Munro couldn't find something to talk about, good or bad. They employ extremely gifted engineers with a ridiculously large amount of experience at doing this exact task.
As a software engineer, I wish there were an equivalent firm in the industry that did teardowns like this so that we could, as an industry, improve over time the way that the automotive industry does.
I feel like it may be one of the factors holding software engineering back from achieving true professional engineering standardization.