Yes, I ask him about that. All other things equal, a project without a constraint will move faster than a project with a constraint (though 37Signals would say otherwise.)
But on the other hand, this post does ask about the converse, namely that SI’s implementation approach will have a dev-speed advantage. That does not make sense to me, but I have heard it from SI-ers, and so asked about it here.
I may have been nitpicking to no purpose, since the chance of someone’s bad idea working exceeds that of any given bad idea working. But I would certainly expect the strategy of ‘understanding the problem’ to produce Event-Horizon-level results faster than ‘do stuff that seems like it might work’. And while we can imagine someone understanding intelligence but not Friendliness, that looks easier to solve through outreach and education.
But I would certainly expect the strategy of ‘understanding the problem’ to produce Event-Horizon-level results faster than ‘do stuff that seems like it might work’.
The two are not mutually exclusive. The smarter non-SI teams will most likely try to ‘understand the problem ’ as best they can, experimenting and plugging gaps with ‘stuff that seems that it might work’, for which they will likely have some degree of understanding as well.
Yes, I ask him about that. All other things equal, a project without a constraint will move faster than a project with a constraint (though 37Signals would say otherwise.)
But on the other hand, this post does ask about the converse, namely that SI’s implementation approach will have a dev-speed advantage. That does not make sense to me, but I have heard it from SI-ers, and so asked about it here.
I may have been nitpicking to no purpose, since the chance of someone’s bad idea working exceeds that of any given bad idea working. But I would certainly expect the strategy of ‘understanding the problem’ to produce Event-Horizon-level results faster than ‘do stuff that seems like it might work’. And while we can imagine someone understanding intelligence but not Friendliness, that looks easier to solve through outreach and education.
The two are not mutually exclusive. The smarter non-SI teams will most likely try to ‘understand the problem ’ as best they can, experimenting and plugging gaps with ‘stuff that seems that it might work’, for which they will likely have some degree of understanding as well.