On usefulness over accuracy in dev – the broken clock conundrum.
Here is a thought experiment. Imagine two clocks; both analogue.
The first clock is broken. But in terms of accuracy its exactly correct twice a day.
The second clock is a minute off; technically, it’s the most useful one; but it’s never exactly correct. But it’s the one thats useful.
I see coding and the technologies we use to be of a similar fashion – and that too the religiosity of “standards” and “best practices”.
I think its far better to be more frequently useful, even if we may not yet be doing what is seen as the correct or right wayβ¦
Be useful is more important than being right and problematic.
Get it done, then on to the next and do that better.