4 ms·
I disagree. Any statement about a piece of engineering without having seen the schematics, diagrams, and tests involved is at best, speculation.
by zalzane 14y ago
I disagree. Any statement about a piece of engineering without having seen the schematics, diagrams, and tests involved is at best, speculation.
- fnordfnordfnord 14y agoI might call it an informed opinion.
- Eliezer 14y agoHe was right on this occasion. I always wait to criticize other people's methods until an occasion when they're actually wrong.
- InclinedPlane 14y agoIf it's a fundamental design aspect such as the size and spacing of cells in a battery I don't think detailed schematics are necessary. If I saw a sketch of a car design which called for the fuel tank to be an open top 5 gallon plastic bucket sitting in the passenger's seat with a hose going into it I wouldn't need any additional or more finely grained details to be able to definitively say that it's an inherently unsafe system. If I saw a sketch of a bridge with a 50 meter gap in the bridge deck I shouldn't think to myself "oh, maybe it's just for hovercars, or maybe they've invented something revolutionary" I should think "that's a fundamentally broken bridge design". Sometimes the finer details of a design matter, and sometimes there's no possible way for them to correct for a fundamental design error. Unless Boeing's subcontractors have made ground breaking advances in the design of lithium-ion cells then these criticisms are enormously well founded. And as we've seen those subcontractors have not, in fact, found a magical escape from the fundamental problems of thermal runaway and chain-reaction in lithium-ion cells.
- fleitz 14y agoYup, or as we call it in our industry: code smell. A good engineer doesn't need to see detailed diagrams, etc, pop open a couple files and you've got a pretty good idea of whether a project is good, or is fucked.