Removing stuff is never obvious yet often better

Re:Removing stuff is never obvious yet often better by QuantumGood on Monday August 26, 2024 @03:35AM (#41354841)

Either accepting or dismissing the number without understanding its purpose or source can also be arrogance, but I agree that throwing a number out without any additional data is of limited, but not zero, usefulness.

When I want to know more about a number, I sometimes seek to test the assumption that an order of magnitude more or less (1.5%, 150%) is well outside the bounds of usefulness—trying to get a sense of what range the number exists within

[ Parent | on HN ]

Re:Removing stuff is never obvious yet often better by lucianbr on Monday August 26, 2024 @07:26AM (#41356110)

No, dismissing something that is claimed without evidence is not arrogance, but common sense.

[ Parent | on HN ]

Re:Removing stuff is never obvious yet often better by QuantumGood on Monday August 26, 2024 @11:08AM (#41357886)

I think we're getting hung up on the concept of dismissing. To question skeptically to learn more is different than to dismiss.

The 5 Step Design Process emphasizes making requirements "less dumb," deleting unnecessary parts or processes, simplifying and optimizing design, accelerating cycle time, and automating only when necessary.

Musk suggests that if you're not adding requirements back at least 10%-15% of the time, you're not deleting enough initially. The percentage is an estimate initially based on experience, and now for several years based on estimates from manufacturing practice.

[ Parent | on HN ]