5 ms·
Wow - is nobody else bothered by all the empty precision? 57.62% Comprehension, 23.96% Navigation... Even the piechart labeled "True effort required for ma
by CliffStoll 5y ago
Wow - is nobody else bothered by all the empty precision?
57.62% Comprehension, 23.96% Navigation...
Even the piechart labeled "True effort required for many large-scale systems" says 7% of "effort" is Integration Test, and 8% in Module testing...
Want to raise my hackles? Give me statements with lots of precision but lacking in documented (not to mention repeatable, reliable, or robust) accuracy.
Convolved on this numeric silliness are several cartoons of smiling faces with vapid captions like "The figuring out time is a decision making time" or "Assessment is the process of understanding a situation around a system enough to make a decision".
- GnomeSaiyan 5y agoCan you explain like I'm 5? I'll be honest I have no idea what you're even trying to say here.
- usefulcat 5y agoIt’s a red flag when you see very precise numbers for things that are inherently difficult to measure.
- tonyedgecombe 5y agoPrecision != Accuracy.
- tudorgirba 5y agoThose numbers come from a peer-reviewed paper and it refers to the data they found in their specific experiment. It is not argued that those specific numbers appear in all cases. However, that data happens to be consistent with several other similar experiments done over the past 20+ years. The rest of the short article builds an arguments based on the assumption that at least 50% of the development time is spent figuring the system out. If you find this assumption to be off base, please disregard the rest of it. In any case, I'd encourage you to ask peer developers if they find that they spend 50% or more of their time reading textual artifacts as a way to figure the system out (code, logs etc).