I love The Rise of Worse is better, and this sounds just like that:
https://www.dreamsongs.com/RiseOfWorseIsBetter.html
It doesn't explain _why_ simple implementation is more important than having a simple interface, but it just makes an observation that simple implementation usually wins.
In my experiments simple implementation won for velocity, because quite often I need to change small parts in all the implementation no matter how modular / reusable code I'm trying to write.
As my velocity increases testing becomes more important as well (especially integration testing), as there are more features interacting in a small amount of code.
Ironic that the article said:
> A wrong lesson is to take the parable literally and to conclude that C is the right vehicle for AI software. The 50%
Now we use Python to glue C code to train the best AIs of this time.
This really hinges on 'velocity':
> .. simple implementation won for velocity ..
How do you specifically define velocity in this context?
(I am asking because I tend to favor speedy velocity in quick iterations; which is another story, than say velocity for change...)
Kind regards