1: Another way of saying what I'm saying: tech teams have an "architecture bias" that *overweights* expected benefits of arch improvements
-
-
4: materialize. Ironically, it's only by being very conservative with architecture changes can you get long enough time horizon for the
Show this thread -
5/5: expected exponential gains to arrive. So you need both a willingness to do big changes and the discipline to do it infrequently.
Show this thread
End of conversation
New conversation -
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.