Re:The Death of Microservice Madness in 2018
by z3t4 on Sunday January 21, 2018 @05:58PM
(#16200603)
You don't always have to know why but it's somewhat frightening that so many "engineers" don't have a clue why they are doing something (because Google does it). And I'm of course guilty of it myself jumping on the hype-train or uncritically taking advice from domain experts only to find out years later that much of it was BS. Most of the time though, you will not reach enlightenment. I guess it's in our nature to follow authority, hype, trends and group think.
[ Parent
| on HN ]
Re:The Death of Microservice Madness in 2018
by walrus1066 on Monday January 22, 2018 @04:23AM
(#16203056)
They're only following their incentives.
What's gonna look better on a devs CV: 'spent a year maintaining a CRUD monolith app' vs 'spent a year breaking monolith into microservices, with shiny language X to boot'.
We can be a very fashion and buzzword driven industry sometimes.
EDIT: this perverse incentive goes all they way to the top, through to CTO level. Sometimes I wonder if businesses understand just how much money and effort is wasted on pointless rewrites that make life harder for everyone.
Re:The Death of Microservice Madness in 2018
by therealdrag0 on Tuesday January 30, 2018 @11:53PM
(#16271433)
"Resume driven development" :)
Re:The Death of Microservice Madness in 2018
by michaelcampbell on Monday January 22, 2018 @09:03AM
(#16204365)
> it's somewhat frightening that so many "engineers" don't have a clue why they are doing something (because Google does it).
This doesn't stop at engineering; open offices, teaser/trick based interviewing, OKR's, ... Even GOOGLE doesn't do some of those things anymore, but the follower sheep still do.