4 ms·
I am a proponent of "choosing boring technologies", but I don't see how it relates to building innovative products and services. You can create an innovative pr
by ngrilly 3y ago
I am a proponent of "choosing boring technologies", but I don't see how it relates to building innovative products and services. You can create an innovative product or service using boring technologies under the hood. I really like the post otherwise.
- mattgreenrocks 3y agoYounger devs conflate tech choices with innovation. They’ll believe that a computer vision company is a dinosaur because they’re using C++ and a glorified CRUD startup is hip and relevant because it uses Rust. It doesn’t help that the anemic-ness of some domains doesn’t set in until 1-2 years later.
- kritr 3y agoUsing newer technologies sometimes buys development velocity, which is a good indication of innovation.
- BlackFly 3y agoI agree that novel technical choices are often conflated with innovation over eagerly. My experience is that in learning the lesson that these things are different many people over correct and assume that novel technical choices are only ever resume padding or useless hype. There are no silver bullets and the only way to get an order of magnitude improvement is iterated marginal improvements. That something is at best a marginal improvement shouldn't be taken for a lack of innovation.
- feoren 3y agoI think the article is a good response to the question the student asked, though: > "As a principal engineer, how do you make sure your company stays at the forefront of innovation?" This is most likely about using all the shiny new technologies in a rapidly changing "forefront of innovation". The article simply isn't about building innovative products and services. Of course, choosing boring technologies is one of the ways that you can help save engineering brain-cycles for the actual innovative core product or service you're building.
- js8 3y agoYeah, I favor a slightly different rule. Choose a conservative technology in places which are not a core competency of your new product. Building a new product is risky, and you should minimize the additional risk coming from a technology choice, except the parts where you're actually trying to beat the competition. That should be the focal point of innovation.
- bdcravens 3y agoAs most companies aren't pure tech, usually the core competency isn't the software itself. Sometimes when it is, it's hidden away (for instance, background processing of data) and the best thing you can do is keep as easy to reason about as possible.
- ngrilly 3y agoTotally agree. That's why I like the notion of "innovation tokens", also mentioned in the seminal post "Choose Boring Technologies" [1]. You choose boring technologies for everything, except for a few topics that will differentiate your solution, where you get to spend your "innovation tokens". [1] https://mcfunley.com/choose-boring-technology https://mcfunley.com/choose-boring-technology
- bdcravens 3y agoIt also applies to trying to avoid being clever with the tech you choose.