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!

@codewiz I believe he says Aeronautics Department 😋

it's windy and he is dancing around

@codewiz I listened to it again and I'm not quite sure what he says. Maybe it's Aeroflows Department.

Follow

@kai He probably meant to say FAA 😉

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

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