DEV Community

Discussion on: Write clean code and avoid the distractions of emerging technology

Collapse
 
stefandorresteijn profile image
Stefan Dorresteijn

I think this entirely depends on your job title.

If you're just an engineer, don't fall for every trend. Don't even look at every trend until they're big enough to have impact on your work. When the trend is young, documentation will suck and the tech might be useless. When the trend grows, support grows, documentation becomes better and the tech will have time to prove itself.

If you're a CTO, look at every trend, evaluate them and implement them if necessary. You don't necessarily have to care about the future of these tech projects because you're moving quickly enough to phase them in/out at the right time. If a new language, framework or concept allows me to build my MVP or new functionality a tad quicker or more efficiently, I apply it (after a little due diligence.) This does require a relatively modular approach. All our functionality runs off their own applications so I could use 12 different languages and still be fine. Just don't require that skillset in future hires (yet), because they're not going to know it yet.