|
|
|
|
|
by qz2
2099 days ago
|
|
My wife is a fine example: Problem: coffee machine not working. Her representation of the problem: we need to buy a new coffee machine. Really what’s going on: coffee machine needs cleaning properly but it doesn’t match the rest of the stuff in the kitchen now. Edit: I'm sure this analogy probably works better for the folk downvoting when you look at it in terms of computation. Perhaps I should have write "the developer wants to rewrite this function as a microservice" whereas the real problem is "we need to fix this defect". The real thing is the developer wants to write a new shiny microservice full of new bugs rather than actually fix the damn bugs. Same as my wife wants a new shiny coffee machine but doesn't want to clean the old one (which is a shitty job, which I did in the end anyway because I made the faulty decision of saying yes to myself too quickly. I also fixed the bug) |
|
Yes, there's a bug in the production services, but maybe it's a nightmare to maintain and there are more and more bugs creeping in and a microservice might help make it more stable - and maybe the developers want more experience with new tech to grow professionally as well.