in reply to daniel:// stenberg://

That's an interesting metaphor and it raises so many questions:

1. Wouldn't it have been smarter to torque them correctly from the start ?

2. How does one even determine the correct torque for any one bolt ?

3. When somebody starts a FOSS project today, where do they acquire a torque-wrench ?

And no, I'm not teasing you (this time 🙂 ) those are some of the questions I tried to find answers to with #varnishcache's "dial it to 11" code quality rule.

in reply to daniel:// stenberg://

@bsdphk I would argue that knowing how much torque to put in or even where the bolt have to go is... a process that can only be done after already having built the project, multiple times.

There is a reason any big engineering project (yes even road and bridges) build a lot of simulations and prototypes and even to scale models.

In software, we have a chance that we can *change the product itself* once it is running for no more cost. As an engineer in any other field, I would kill for that ability, as it would makes the iterative process of designing far faster and efficient.

Said otherwise... doing it the way we do in software is more advanced and "good" engineering than doing it "in the real world".

This is ofc only one lens to look at it, but it does have some support. It is just one map to look at things, maps are not the territory.