news.volyx.in

Choose Boring Technology (2015) (mcfunley.com)

433 points by tosh · 13 days ago · 245 comments on HN

Article summary

The article discusses the importance of choosing 'boring' technology in software development, arguing that it is better to use well-established and well-understood technologies rather than innovative but untested ones. The author suggests that companies have a limited number of 'innovation tokens' that can be spent on new technologies, and that using these tokens wisely is crucial for success. The article also emphasizes the importance of considering the long-term costs and risks associated with new technologies. By choosing boring technology, companies can avoid unnecessary complexity and focus on solving real problems.

Main themes

  • Boring technology
  • Innovation tokens
  • Technical debt
  • Risk management
  • Software development strategy
  • Technology choice

What commenters say

  • NodeJS is no longer considered a non-boring technology, as it has become a mature and widely-used platform.
  • The concept of innovation tokens is still relevant today, and companies should carefully consider how they allocate their resources.
  • The choice of technology depends on the team's experience level and the specific needs of the project, with some technologies being boring for one team but not another.
  • The JavaScript ecosystem is still considered non-boring due to its fast-paced nature and the constant introduction of new libraries and frameworks.
  • Using boring technology can help companies avoid unnecessary complexity and focus on solving real problems, but it may not always be the best choice for every project.
  • The definition of boring technology is subjective and depends on the context, with some technologies being considered boring in one context but not another.
  • The use of new technologies can be beneficial, but it also introduces new risks and uncertainties that need to be carefully managed.
  • The importance of standardization and stability in technology choice is highlighted, with some commenters arguing that a lack of standardization in the JavaScript ecosystem is a major issue.