3. Familiarity with complex solution ecosystem & tradeoffs of different approaches starts to be thought of as "essential knowledge."
-
-
Replying to @sarahmei
4. Somebody automates one of the solutions in a way that eliminates some possibilities, but works well enough in most cases.
1 reply 0 retweets 33 likes -
Replying to @sarahmei
5. Automated solution takes off; developers who use it don't have to know anything about the complex ecosystem that gave rise to it.
1 reply 2 retweets 52 likes -
Replying to @sarahmei
6. Much Gnashing of Teeth at developers who don't have this "essential knowledge."
1 reply 0 retweets 45 likes -
Replying to @sarahmei
7. The automated solution turns out to let developers focus on a different problem that they hadn't had brainspace for before.
3 replies 1 retweet 57 likes -
Replying to @sarahmei
(Owing to brainsoace being occupied by complex ecosystem of solutions & tradeoffs, that automation obviated for most projects.)
1 reply 0 retweets 33 likes -
Replying to @sarahmei
8. Semi-permanent factions form: folks who insist "essential knowledge" is still essential; & folks who don't find it useful anymore.
5 replies 2 retweets 60 likes -
Replying to @sarahmei
100% true, but a nuance: some developers are working in the space where the knowledge is still important and see other devs in the ...
1 reply 0 retweets 0 likes -
same space using the new tool and introducing bad bugs for users. Old time developers act like this damns the entire new solution.
1 reply 0 retweets 1 like -
Also, old time developers spend more and more time on the "bad performance" of the new soln as other excuses fade away.
1 reply 0 retweets 5 likes
You can be pretty sure that if the old timers in an ecosystem are suddenly obsessed with perf and berating new tools, this is in play.
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.