1: Another way of saying what I'm saying: tech teams have an "architecture bias" that *overweights* expected benefits of arch improvements
-
-
I couldn't really relate to your previous thread. But can to this one :-). Architecture should be "good enough" & provide escape hatches
-
Then I'm glad I tried to restate it :)
-
If you follow me on Twitter you're seeing me write blog posts live, with all the gory editing mistakes ;)
End of conversation
New conversation -
-
-
Agree on all counts. Other big problem is that new architecture benefits are almost always overestimated and drawbacks underestimated.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
As an app dev, I box myself into frameworks; I forget that I'm not limited by their constraints if I think like an engineer instead.
-
This means that early choices feel important. And if I get boxed in, the only way out is a big change / rewrite.
-
Which is ironically antithetical to being an app developer, heh.
End of conversation
New conversation -
-
-
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.
