[hzlatar]

Thank you for taking the time to answer. You sound like a good rational engineer. Things that work don't need unnecessary splash of coolness.

On my previous job, I had been working for 15 years on the development of a complex business system. It included desktop apps, mobile apps, webs, on-premises and clouds. Throughout the years, we have introduced many then cutting-edge technologies for new products within the system. Some technologies before they were cool. But, the fine-working-already-done products, we kept supporting with the original technology for the lifetime of the product.

The point is that many new tools and technologies bring a very limited value to the finished working products.

Now, I am a maker of the new development tools. So, I am eager to push them to the world, but wouldn't like to be perceived as an "architecture astronaut". Your opinion helps in understanding how and why engineers choose new tools and technologies.

[FpUser]

"Coolness" is not in what I use inside my product but how "cool" customers think it is because of features, robustness, price etc. It feels very "cool" to me when my products work and serve customers.

>"Now, I am a maker of the new development tools."

This is a part where I spend money. Good tools are very valuable as they directly save me time / money.

>"The point is that many new tools and technologies bring a very limited value to the finished working products."

Even for new ones. For example my servers are modern C++. In theory I should be using Rust / Go for new ones if I listen to a chorus. Guess what modern C++ works just fine for me and produces stellar results hence no reason for me to switch. I do some toy projects with new languages / tech to get a grip and be aware just in case.