This ended up being an anti-microservices rant more than a commentary on Fake Problems.
For what its worth, fake problems even from the non-technical perspective are a huge problem in a lot of organizations. I was hoping this was going to be more about that.
Basically how requirements analysts, business owners/stakeholders, and even devs can tend to focus on edge cases and problems instead of driving forward the 90% solution. You can end up in this cycle of over-thinking where you make bad decisions. Those bad decisions beget more bad decisions until you are left spinning--trying to solve a problem that shouldn't even exist because you were solving a "fake" problem to begin with.
This ended up being an anti-microservices rant more than a commentary on Fake Problems.
For what its worth, fake problems even from the non-technical perspective are a huge problem in a lot of organizations. I was hoping this was going to be more about that.
Basically how requirements analysts, business owners/stakeholders, and even devs can tend to focus on edge cases and problems instead of driving forward the 90% solution. You can end up in this cycle of over-thinking where you make bad decisions. Those bad decisions beget more bad decisions until you are left spinning--trying to solve a problem that shouldn't even exist because you were solving a "fake" problem to begin with.