Brandon Rohrer on Nostr: Rule Of Three for avoiding over-engineering (not standard and recommended by no one ...

Rule Of Three for avoiding over-engineering
(not standard and recommended by no one but me):

Don’t implement a fix for something until the third time it has bit you.

Save type hints for after your third type-related bug.

Don’t optimize your code until the third time it has times out.

Don’t create that tracking dashboard until the third time you’ve wished for it.

Don’t automate that deployment step until the third time it’s been forgotten.