Technology evolves rapidly, and there’s always something new on the horizon—whether it’s the latest programming framework, cloud service, or infrastructure upgrade. While adopting modern solutions can be beneficial, the reality is that newer doesn’t always mean better for every situation.
Take Ferrari, for example. It’s one of the best cars in the world, but is it the right choice for a school run? Probably not. A more practical car would get the job done with less hassle, cost, and maintenance. The same logic applies to technology: just because something is new and advanced doesn’t mean you need it.
I have often experienced scenarios where using the latest technology might not be the best choice. A lot of companies subscribe to a lot of technology that they don’t need and waste valuable money.
Overengineering with the Latest Programming Techniques
Imagine you’re building a simple to-do list application. You could use the latest programming frameworks, microservices architecture, and AI-powered features to predict tasks. But is all that necessary? For a basic to-do app, a straightforward monolithic architecture with a simple front-end and back-end would suffice. Overengineering with advanced techniques not only increases development time but also adds unnecessary complexity and cost.
If you’re building a simple company website or blog, plain HTML, CSS, and JavaScript (or even a CMS like WordPress) can be more efficient. Using heavy frameworks adds complexity, increases load time, and requires ongoing maintenance for security updates.
I believe in giving time to the new technology to mature before I start implementing it in projects. When KnockoutJS came to the market with a lot of hype, we used it in our projects. Within a few years, the popularity of the KnockoutJS went down, and I found it challenging to find the experts to support those projects.
Cloud Services: When Simplicity Wins
Cloud computing has revolutionized how we build and deploy applications, but not every project requires the latest cloud services. For instance, if you’re running a small blog or a personal portfolio website, you don’t need a high-availability, multi-region cloud setup with auto-scaling and serverless functions. A basic shared hosting plan or a simple virtual private server (VPS) would work just fine.
Serverless computing (like AWS Lambda, Azure Functions) is a great innovation, but is it necessary for every application? If you have a small internal tool that runs reliably on a virtual machine or traditional hosting, switching to serverless can introduce unnecessary costs and complexity. Serverless makes sense for highly variable workloads, but if your system has steady traffic, traditional hosting might be more cost-effective. A simple VM-based or containerized deployment could work just as well. And you can host many tools in one VM.
Kubernetes is the gold standard for container orchestration, but do you really need it for a small business application with just a few users? If you use Kubernetes for small apps, you will require DevOps expertise and additional costs for managing nodes and networking, which is unnecessary complexity when a more straightforward solution would suffice. If your application runs on a single server or has a few containers, a managed container service like AWS ECS or Docker Compose could be simpler and more cost-effective.
Some businesses rush into a multi-cloud strategy, believing it provides better reliability and cost savings. However, managing multiple cloud providers can increase complexity and costs without providing real benefits. If your workload is stable and fits within one cloud provider, it’s often more straightforward and more efficient to optimize for that platform instead of spreading across multiple providers. Multi-cloud is useful when business continuity, compliance, or specific services require it, but not just because it’s trendy.
Databases: Not Every App Needs Big Data
When building an application, it’s tempting to use the latest database technologies like distributed NoSQL databases or real-time analytics engines. However, for many use cases, a traditional relational database like MySQL or PostgreSQL is more than adequate. These databases are reliable, well-documented, and easier to manage for smaller-scale applications. A local library management system doesn’t need a distributed database like Cassandra. A simple SQL database will handle the data efficiently and cost-effectively.
Mobile Apps: Native vs. Cross-Platform
While native mobile app development offers the best performance and access to device-specific features, it’s not always necessary. For many applications, cross-platform frameworks like Flutter or React Native can deliver a great user experience without the need to maintain separate codebases for iOS and Android. However, a small business app for tracking inventory doesn’t need the performance optimization of native development. A cross-platform solution can save time and resources while still meeting the business’s needs.
AI and Machine Learning: Not Every Problem Requires a Smart Solution
Artificial intelligence and machine learning are powerful tools, but they’re not always the right solution. For example, if you’re building a basic chatbot for customer support, a rule-based system might be more than enough. Implementing a full-scale natural language processing (NLP) model would be overkill and could lead to unnecessary costs and complexity. A simple FAQ-based chatbot using predefined responses is often sufficient for small businesses, rather than deploying a complex AI-driven conversational agent.
I am not against the new technology, but I am against the hype. The key to effective technology use is understanding the problem you’re trying to solve and choosing the right tools for the job. Just as you wouldn’t use a Ferrari for a school run, you don’t always need the latest and greatest tech for every application. By focusing on simplicity, cost-effectiveness, and practicality, you can build solutions that are efficient, maintainable, and fit for purpose.