5 ms·
If a technology is replacing an existing technology that a company is already using (Elasticsearch v.s Solr for example) the questions I ask are: 1. How much w
by simonw 7y ago
If a technology is replacing an existing technology that a company is already using (Elasticsearch v.s Solr for example) the questions I ask are:
1. How much work will it be to /completely/ replace old-tech with new-tech?
2. Does new-tech give us advantages that outweigh that switching cost?
My rule of thumb is that new-tech can't be an incremental improvement on old-tech - if it's going to have a decent ROI when it comes to switching cost (and re-skilling cost and so on) it needs to be a HUGE improvement - either a multiplier of developer productivity or enabling features that simply cannot be built with old-tech.
The worst result - which I've seen far too many times - is that new-tech only 50-80% replaces old-tech - and now you have to maintain both.
- simonw 7y agoThis rule of thumb comes from having personally made bad decisions around this issue far too many times.
- andrekandre 7y ago> The worst result - which I've seen far too many times - is that new-tech only 50-80% replaces old-tech - and now you have to maintain both. i’ve seen this too, (in apps) where there are 3 different “reactive” libraries in use that all do the same thing smh.. my feeling is, if you are going to change out the technology, then to avoid said problem of maintaining both, is the change needs to happen very very quickly to avoid having to maintain the old one while getting side-tracked to implementing new features and the transition gets sidelined... its very difficult to pull off
- tonyarkles 7y agoSigh... just yesterday I found code in a project I inherited where an Observable was returning Futures to the observer. It probably seemed like a good idea to whoever at the time but damn does it make it hard to follow what’s going on.
- gowld 7y agoIt's basically never worth replacing the old stuff. Only adopt new stuff if the future use cases are so huge (10x the old system) that the old stuff becomes a small afterthought that you can easily afford to throw it away (and lose its value) or pay the cost of rewriting it (which mostly cancels out it's value)