At 13:13 into the video, he mumbles:

"W-what I'm trying... I have a solve this... err... implement rigorously is this sort of 5 step process:

1. Your requirements are definitely dumb: everyone's wrong, no matter who they are [...] So try to make your requirements less dumb."

2. Then, try to delete the part or process.

The bias tends to be very strongly in favor of adding parts in case we need them... but you can basically make "in case" arguments for so many things! [...]

So, you gotta delete the parts or process steps that you don't need.

3. Whatever requirement or constraint you have, it must come with a name, not a department. Because you can't ask the departments, you have to ask a person

[...] otherwise you could have a requirement that basically an intern 2 years ago randomly came up with off the cuff... and they're not even at the company any more... but it came from the, let's say, Air Flow Department!

4 Only the third step is to simplify or optimize [he seems to be off-by-1].

Possibly the most common error of a smart engineer is to optimize the thing that should not exist. Everyone has been trained in school that you gotta answer the question -
convergent logic. So you can't tell a professor "your question is dumb" - you'll get a bad grade!

So everyone basically - without knowing it - they got a mental straight-jacket on: they'll work on optimizing the thing that should simply not exist!

@codewiz case in point; he started with 5 steps, but by the end of his talk, there were only 4 😂


@kai I also thought that he eliminated one step from "this sort of 5-step process which I implements rigorously"! 😂

But the boring truth is that he mentioned step 5 briefly at 21:56:

"And then the final step is Automate."

· · Web · 0 · 0 · 0
Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!