32 ms·
A Checklist for Evaluating New Technology
- simonw 7y agoIf 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)
- lowdose 7y ago1st check: should start at Zapier integrations. No API integration with the other 600+ SAAS means the technology does not yet scale. 2nd check is there a link on the website for developers. 3th Are they hiring?
- pcmaffey 7y agoNote that this is most likely just filtering for whether or not said company has raised more money than they know what to do with.
- statictype 7y ago> No API integration with the other 600+ SAAS means the technology does not yet scale This is an extremely naive take. I’m curious about how many people actually approach technology evaluations with this mindset.
- sk5t 7y agoZapier will not support HIPAA requirements, sooo... they may as well not exist for businesses that touch healthcare data.
- Hokusai 7y ago> Sometimes there’s a technology that solves a problem really well in your particular project, but which is really hard to understand or learn. I have seen this problem too many times. Some team find a framework/language combination that makes their lives slightly easier in the short term and want to go for the new technology. But, they do not think about how we will scale that knowledge or what will happen if the code is moved to another team. A couple of times I have been in the situation to have to re-write an application to the company common language (in one case Java, the other Javascript) because the receiving teams did not liked the technology and did not wanted to spend personal time learning something that was not valuable to them. When a new framework is adopted, it is a commitment that we will train the developers and let them experiment, fail and learn until they take hold of the technology. It takes tame and the decision cannot be taken lightly.
- simonw 7y agoOne of my favourite observations about Python is that it's the second best language for basically everything - which makes it a fantastic default for an organization.
- bsder 7y agoNever thought about it that way, but it's an interesting observation. My biggest problem though isn't which scripting language someone should use for some task. It's getting them to the idea that they should use a scripting language for some task. People forget that HN is not the norm.
- m463 7y ago> the idea that they should use a scripting language for some task People like to do premature optimization, and choosing the language is one way.
- bcrosby95 7y agoLanguage choice isn't a premature optimization. People love to take that quote that was talking about a very specific thing and use it to justify not thinking about performance at all.
- rooam-dev 7y agoNo 1 on my list is "how testable is the new technology?".
- golover721 7y agoA big one for me is “What is the community like?”. Especially for open source technologies. Do the contributors spend time answering questions? What is the general tone in the community, welcoming? Confrontational? All the best technology decisions I have made have come with a strong friendly community.