Resisting the Temptation of Edge Technologies

Friday, April 12, 2024

Note: This post may surprise some of my colleagues, as I am known for my enthusiasm for new technologies. However, I have learned the hard way that not every new technology is the right fit for every project. This post is a reminder to myself and others to resist the temptation of edge technologies and make informed decisions about technology adoption.

The allure of cutting-edge technologies is undeniable. They promise to revolutionize industries, redefine efficiency, and even reshape how we live and work. However, the shiniest new tools are not always the right fit for every project or business.

The Latest Isn't Always the Greatest

While new technologies often grab headlines and spark imaginations, they aren't always the best choice for your specific needs. The allure of using the newest tech can be strong, but it's important to step back and assess whether these solutions genuinely align with the goals you're trying to achieve. The newest software or hardware might seem impressive (and fun to talk about), but if it doesn't serve a purpose in your project or solve a specific problem, it's likely not worth the investment.

Examples of some hyped technologies of current times include blockchain, artificial intelligence. Architectural patterns like microservices, serverless, and event-driven architecture are also popular. Programming languages like Rust, Go, and Kotlin are gaining traction.

Look Beyond the Hype

It's easy to get caught up in the excitement around new technologies. Every day, there seems to be a groundbreaking development or an innovation that promises to change the game. Right now it's AI. Tomorrow it might be quantum computing.

However, adopting technology simply because it's trending can lead to unnecessary complexity and wasted resources. Before deciding on a technology, ask yourself: Does this actually address any of my current needs? If the answer is no, it might be best to pass on what might merely be today's tech fad.

Start with the Problem, Not the Solution

A common trap many businesses fall into is letting the technology dictate their strategy rather than their strategic needs guiding their technology choices. To avoid this, begin by defining what you need to accomplish — identify your business requirements first. What problem are you trying to solve? What are the most critical outcomes for your project? Once these questions are answered, you can look for technologies that align with your goals.

Team members should not be afraid to challenge the status quo and ask tough questions about the technology choices being made but at the same time, they should be focused on the business objectives and not just the technology itself. It will be always more interesting to work with something new, but it is important to remember that the technology should serve the business, not the other way around.

Making Wise Architectural Decisions

When it comes to deciding on the technological backbone of your project, consider three essential factors: what your business needs, your team's expertise, and the maturity of the technology.

A new, untested tool might not be the best choice if your team isn't equipped to handle it or if it hasn't been proven reliable over time. Choosing the right technology should be a balanced decision that supports your business objectives without adding unnecessary risk.

There is a time and place for innovative technologies. The best practice is to start small — perhaps by integrating them into side projects or less critical aspects of your business to test their viability. This way, you can evaluate their benefits without putting your main operations at risk. Once a new technology has proven itself in these test cases, you might consider a broader roll-out.

Consider the example of microservices — an architectural style that structures an application as a collection of services that are highly maintainable and testable, independently deployable, and organized around business capabilities. While they are popular, microservices are not suitable for every project. They work best in larger, more complex projects where their benefits can truly be realized. Read more about when to use microservices.

For my experience, I consider microservices to be the worst architectural pattern for every project except for the ones that is not.

Another example is AI. While it's a powerful tool, it's not a one-size-fits-all solution. Many businesses are eager to incorporate AI into their operations, but they often lack the data infrastructure or expertise to do so effectively. Even worse, they may build entire projects around AI without fully understanding that they not offering any real value to the business.

All these decisions eventually cost time and money. It's essential to make informed choices that align with your business objectives and capabilities.

This is even applicable to the bare programming languages. For example, If you have a team of developers that are experts in Java, it might not be the best idea to switch to a new language like Rust or Go just because they are trending. The learning curve and potential pitfalls might outweigh the benefits of using a new language.


Choosing the right technology is crucial for any project's success. While it can be tempting to opt for the latest and greatest advancements, it's essential to remain grounded in what truly serves the project's objectives. By critically assessing the need, resisting the allure of hype, and cautiously experimenting with new tools, you can ensure that technology serves your business, not the other way around.

This article was generated with the assistance of AI and refined using proofing tools. While AI technologies were used, the content and ideas expressed in this article are the result of human curation and authorship.

Read more about this topic at: Importance is All You Need