You sort of have to create organizational incentives for "brilliantly boring" because, left to their own devices, people often optimize for not-boring systems therefore deliver the combination of not-boring and not-brilliant.
-
-
Show this thread
-
I mean "implementation choices" substantially broader than the commentary on software that it would probably otherwise be read at, because capitalism is a repeatable engine to suggest "That problem: have you considered paying an expert money to solve it for you. Several, maybe?"
Show this thread
End of conversation
New conversation -
-
-
Did one of those recently. Threw out a bunch of code, *twice*, because...OK, someone else can carry this load. You have to integrate the pain of code over time, and then it becomes much less painful to lose the maintenance expense. Of course, if it's another team...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Totally agree with the brilliantly boring sentiment as a positive compliment. We need to use that more often for implementation/execution efforts.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Something I learnt when I was a mechanical engineer applies to software as well: "it's easy to design a complicated solution that doesn't *obviously* fail; it's hard to design a simple solution that obviously *doesn't* fail"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.