











{"author":"Faiq Najib Al-Aziz","body":"\n_So anyway_, a while back I was sitting in an internal meeting, Zoom or Google Meet, I honestly can't remember, when a colleague suddenly lit up with enthusiasm:\n\n\u003e _\"What if we migrate to microservices while we're at it? To be modern, to be scalable, to be-\"_\n\n_To be what, exactly?_ Our system at the time had two main features, a team of four people, and traffic that barely hit a thousand requests a day on its busiest day. The case for microservices? Zero. The enthusiasm for it? A hundred hahaha.\n\nI can't blame him. I've been there. And if I'm honest, I still slip into that mindset sometimes. The pull toward shiny new technology is very real, and there's nothing inherently wrong with it, _as long as_ we recognize it as a pull, not a technical decision.\n\nWhenever I have to choose a tech stack, I hear two voices pulling in different directions: the ego that wants to look sophisticated, and the business that cares whether the system works and delivers value.\n\n## Signs Your Ego Might Be Involved\n\nIf we're honest, ego-driven technical decisions tend to come with signs like these:\n\n**\"This technology is trending.\"**\nOpen Twitter/X and scroll for a bit. There will be a thread about some new framework that supposedly changes everything. Next month there will be another one that changes everything again. Round and round we go. Tech FOMO is real, and following it every time gets exhausting.\n\n**\"It'll be hard to hire people if we stick with the old stuff.\"**\nThat can be true. But sometimes this is a nice way to justify a decision that's more about personal career goals than the system. That's not wrong either. Just be honest about the reason.\n\n**\"Everyone in the community is already using this.\"**\nPeer pressure doesn't stop after high school. In developer circles, it can look like feeling left behind because you haven't tried Kubernetes or Rust, or containerized everything, even though your little monolith is doing just fine hehe~\n\n**\"Good code is fun to write.\"**\nThis one is easy to dress up as professionalism. We pick a complex architecture not because we need it, but because it's fun to build. Then someone has to carry that codebase later, maybe us a few months from now[^1].\n\n## The Business Usually Isn't Picking Your Stack\n\nA little uncomfortable, but usually true: **the business doesn't care if you use PHP or Go, REST or GraphQL, Postgres or MySQL**. It cares that the system runs, is fast enough, costs a reasonable amount to operate, and can be extended when new needs show up.\n\nIn practice, business questions usually come back to things like these:\n\n| Engineer's Question | Business Question |\n|---|---|\n| Is this technology state-of-the-art? | Can it be done on time? |\n| Is the architecture elegant? | Can the team maintain it? |\n| Can this scale to millions of users? | What's the monthly server cost? |\n| Does this use a popular language? | If someone leaves the team, how long does onboarding take? |\n\nThe questions are different. I catch myself spending more time on the left while the people paying my salary are thinking about the right. Sometimes I need the reminder.\n\nThat doesn't mean technical concerns can be ignored. A poor technical choice today can become expensive technical debt tomorrow, which is a business concern too. We have to look at both sides.\n\n## Questions I Ask Myself Now\n\nAfter a few wrong turns (and dealing with the consequences hehe), I try to ask myself four things before choosing a new stack or architecture:\n\n### 1. Can the team still maintain this six months from now?\n\nThe question isn't \"can I implement this?\" It's \"can the team live with it?\" If I leave tomorrow, can someone else continue, or will the first two weeks be a breakdown?\n\nI want the technology we choose to remain understandable to the most junior person on the team[^2]. If not, we're building a knowledge silo, and that's genuinely risky.\n\n### 2. Does this fix a real problem, or an imaginary future one?\n\nPremature optimization is the enemy of productivity. Building a complex event-driven architecture for an application that may never reach millions of users is an extremely costly decision, both in time and in complexity.\n\nMy rule of thumb: **solve the problem in front of us with something good enough for what we can measure now**. If we need to scale later, refactor based on evidence, not my fortune-telling hehe.\n\n### 3. What does it actually cost?\n\nNot just cloud costs. Time counts too. How long does setup take? Onboarding? Debugging when something breaks? How long until a new developer can understand the system well enough to contribute?\n\nSophisticated technology that takes a week to set up locally is expensive, before a single line of business logic has been written.\n\n### 4. Does this speed up time-to-market or hold it back?\n\nDelivery speed matters enormously to a business. A feature that's six months late can mean lost opportunities, users going to a competitor, or investors losing confidence.\n\nIf a technology choice speeds up delivery, great. If it slows it down, reconsider, even if the technology is technically the \"more correct\" choice.\n\n## One Example from My Own Work\n\nLet me _self-reflect_ for a moment. I wrote about [migrating a backend from PHP to Go](/writing/2026/legacy-php-to-go-migration/). The project had 370+ endpoints, 33 entities, and nearly 200,000 lines of code.\n\nAnd the honest question I had to ask myself at the time was: **was this a business decision, or was it my ego wanting to work with Go?**\n\nThe answer was both. I was curious about Go, but that wasn't the whole story hehe~\n\nThe **ego** side: yes, I was genuinely excited about Go. I wanted deeper hands-on experience with it. I liked how Go handles concurrency. That was all real, and I won't pretend otherwise.\n\nBut the **business** side was equally real:\n\n- The legacy system had serious architectural problems, not because of PHP itself, but because of the complete absence of layer separation, making every change a high-risk operation\n- Unpredictable deploys had caused multiple production incidents\n- Low test coverage had made the team afraid to refactor, even when refactoring was urgently needed\n- A single Go binary eliminated the dependency hell on the server that had been consuming the ops team's time\n\nSo Go wasn't chosen purely because it's cool, but because in that specific context, the trade-offs made sense: a large upfront migration cost[^3], but with measurable long-term benefits.\n\nFor me, what matters is being able to explain the trade-offs honestly and stand behind the decision. Not pretending I have no ego at all.\n\n## Ego Can Be Useful Too\n\n**Developer ego isn't always bad.** It can make us want to learn new things, write cleaner code, and push for better solutions. Those things can be useful.\n\nThe trouble starts when ego clouds our judgment. We choose technology to look clever instead of solving a problem. We build something complicated because it's fun, then defend a bad choice because admitting it feels embarrassing.\n\nI still have to check my own motives from time to time. Sometimes the reason really is business; sometimes I just want to try a new technology. That's fine, as long as I don't mix the two up when explaining a decision to the team.\n\nI won't always get that distinction right. But I think it's worth asking before we build the whole thing.\n\nThat's it from me for now. Thanks for somehow ending up here and reading to the end hehe~\n\n[^1]: And it's usually ourselves, six months later, who've completely forgotten why we built it that way in the first place hahaha.\n[^2]: This doesn't mean you can't use advanced technology. It means there's a responsibility for documentation, an onboarding plan, and ensuring knowledge isn't centralized in one person.\n[^3]: Migration using an incremental, per-module approach rather than a big-bang rewrite, a hard lesson learned from many teams who've tried the latter and failed.\n","body_clean":"So anyway, a while back I was sitting in an internal meeting, Zoom or Google Meet, I honestly can\u0026rsquo;t remember, when a colleague suddenly lit up with enthusiasm:\n\u0026ldquo;What if we migrate to microservices while we\u0026rsquo;re at it? To be modern, to be scalable, to be-\u0026rdquo;\nTo be what, exactly? Our system at the time had two main features, a team of four people, and traffic that barely hit a thousand requests a day on its busiest day. The case for microservices? Zero. The enthusiasm for it? A hundred hahaha.\nI can\u0026rsquo;t blame him. I\u0026rsquo;ve been there. And if I\u0026rsquo;m honest, I still slip into that mindset sometimes. The pull toward shiny new technology is very real, and there\u0026rsquo;s nothing inherently wrong with it, as long as we recognize it as a pull, not a technical decision.\nWhenever I have to choose a tech stack, I hear two voices pulling in different directions: the ego that wants to look sophisticated, and the business that cares whether the system works and delivers value.\nSigns Your Ego Might Be Involved #If we\u0026rsquo;re honest, ego-driven technical decisions tend to come with signs like these:\n\u0026ldquo;This technology is trending.\u0026rdquo; Open Twitter/X and scroll for a bit. There will be a thread about some new framework that supposedly changes everything. Next month there will be another one that changes everything again. Round and round we go. Tech FOMO is real, and following it every time gets exhausting.\n\u0026ldquo;It\u0026rsquo;ll be hard to hire people if we stick with the old stuff.\u0026rdquo; That can be true. But sometimes this is a nice way to justify a decision that\u0026rsquo;s more about personal career goals than the system. That\u0026rsquo;s not wrong either. Just be honest about the reason.\n\u0026ldquo;Everyone in the community is already using this.\u0026rdquo; Peer pressure doesn\u0026rsquo;t stop after high school. In developer circles, it can look like feeling left behind because you haven\u0026rsquo;t tried Kubernetes or Rust, or containerized everything, even though your little monolith is doing just fine hehe~\n\u0026ldquo;Good code is fun to write.\u0026rdquo; This one is easy to dress up as professionalism. We pick a complex architecture not because we need it, but because it\u0026rsquo;s fun to build. Then someone has to carry that codebase later, maybe us a few months from now1.\nThe Business Usually Isn\u0026rsquo;t Picking Your Stack #A little uncomfortable, but usually true: the business doesn\u0026rsquo;t care if you use PHP or Go, REST or GraphQL, Postgres or MySQL. It cares that the system runs, is fast enough, costs a reasonable amount to operate, and can be extended when new needs show up.\nIn practice, business questions usually come back to things like these:\nEngineer\u0026rsquo;s Question Business Question Is this technology state-of-the-art? Can it be done on time? Is the architecture elegant? Can the team maintain it? Can this scale to millions of users? What\u0026rsquo;s the monthly server cost? Does this use a popular language? If someone leaves the team, how long does onboarding take? The questions are different. I catch myself spending more time on the left while the people paying my salary are thinking about the right. Sometimes I need the reminder.\nThat doesn\u0026rsquo;t mean technical concerns can be ignored. A poor technical choice today can become expensive technical debt tomorrow, which is a business concern too. We have to look at both sides.\nQuestions I Ask Myself Now #After a few wrong turns (and dealing with the consequences hehe), I try to ask myself four things before choosing a new stack or architecture:\n1. Can the team still maintain this six months from now? #The question isn\u0026rsquo;t \u0026ldquo;can I implement this?\u0026rdquo; It\u0026rsquo;s \u0026ldquo;can the team live with it?\u0026rdquo; If I leave tomorrow, can someone else continue, or will the first two weeks be a breakdown?\nI want the technology we choose to remain understandable to the most junior person on the team2. If not, we\u0026rsquo;re building a knowledge silo, and that\u0026rsquo;s genuinely risky.\n2. Does this fix a real problem, or an imaginary future one? #Premature optimization is the enemy of productivity. Building a complex event-driven architecture for an application that may never reach millions of users is an extremely costly decision, both in time and in complexity.\nMy rule of thumb: solve the problem in front of us with something good enough for what we can measure now. If we need to scale later, refactor based on evidence, not my fortune-telling hehe.\n3. What does it actually cost? #Not just cloud costs. Time counts too. How long does setup take? Onboarding? Debugging when something breaks? How long until a new developer can understand the system well enough to contribute?\nSophisticated technology that takes a week to set up locally is expensive, before a single line of business logic has been written.\n4. Does this speed up time-to-market or hold it back? #Delivery speed matters enormously to a business. A feature that\u0026rsquo;s six months late can mean lost opportunities, users going to a competitor, or investors losing confidence.\nIf a technology choice speeds up delivery, great. If it slows it down, reconsider, even if the technology is technically the \u0026ldquo;more correct\u0026rdquo; choice.\nOne Example from My Own Work #Let me self-reflect for a moment. I wrote about migrating a backend from PHP to Go. The project had 370+ endpoints, 33 entities, and nearly 200,000 lines of code.\nAnd the honest question I had to ask myself at the time was: was this a business decision, or was it my ego wanting to work with Go?\nThe answer was both. I was curious about Go, but that wasn\u0026rsquo;t the whole story hehe~\nThe ego side: yes, I was genuinely excited about Go. I wanted deeper hands-on experience with it. I liked how Go handles concurrency. That was all real, and I won\u0026rsquo;t pretend otherwise.\nBut the business side was equally real:\nThe legacy system had serious architectural problems, not because of PHP itself, but because of the complete absence of layer separation, making every change a high-risk operation Unpredictable deploys had caused multiple production incidents Low test coverage had made the team afraid to refactor, even when refactoring was urgently needed A single Go binary eliminated the dependency hell on the server that had been consuming the ops team\u0026rsquo;s time So Go wasn\u0026rsquo;t chosen purely because it\u0026rsquo;s cool, but because in that specific context, the trade-offs made sense: a large upfront migration cost3, but with measurable long-term benefits.\nFor me, what matters is being able to explain the trade-offs honestly and stand behind the decision. Not pretending I have no ego at all.\nEgo Can Be Useful Too #Developer ego isn\u0026rsquo;t always bad. It can make us want to learn new things, write cleaner code, and push for better solutions. Those things can be useful.\nThe trouble starts when ego clouds our judgment. We choose technology to look clever instead of solving a problem. We build something complicated because it\u0026rsquo;s fun, then defend a bad choice because admitting it feels embarrassing.\nI still have to check my own motives from time to time. Sometimes the reason really is business; sometimes I just want to try a new technology. That\u0026rsquo;s fine, as long as I don\u0026rsquo;t mix the two up when explaining a decision to the team.\nI won\u0026rsquo;t always get that distinction right. But I think it\u0026rsquo;s worth asking before we build the whole thing.\nThat\u0026rsquo;s it from me for now. Thanks for somehow ending up here and reading to the end hehe~\nAnd it\u0026rsquo;s usually ourselves, six months later, who\u0026rsquo;ve completely forgotten why we built it that way in the first place hahaha.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\nThis doesn\u0026rsquo;t mean you can\u0026rsquo;t use advanced technology. It means there\u0026rsquo;s a responsibility for documentation, an onboarding plan, and ensuring knowledge isn\u0026rsquo;t centralized in one person.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\nMigration using an incremental, per-module approach rather than a big-bang rewrite, a hard lesson learned from many teams who\u0026rsquo;ve tried the latter and failed.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\n","canonical":"https://najib.id/en/writing/2026/tech-stack-ego-vs-business/","description":"Notes on the pull of shiny new technology, and how I try to tell curiosity apart from a project need.","language":"en","lastmod":"2026-11-11T23:31:00Z","publishedAt":"2026-04-18T00:00:00Z","readingTime":7,"section":"writing","series":null,"tags":["architecture","soft-skill","notes"],"title":"Choosing a Tech Stack: Between Ego and Business","type":"writing","url":"https://najib.id/en/writing/2026/tech-stack-ego-vs-business/","wordCount":1316}
