3 ms·

> many devs at big and mid-sized companies have a very clear financial incentive to adopt the latest trends. I used to be more hesitant about whether it was a

> many devs at big and mid-sized companies have a very clear financial incentive to adopt the latest trends. I used to be more hesitant about whether it was a good idea to start out with microservices, then I started going on interviews. I would paraphrase the phone screens I was given as "Have you accepted microservices as your Lord and savior?". Call after call they wanted me to extoll the virtues of microservices before even considering me for an interview.

lumost 3y ago
I wonder if this incentive is stronger at smaller startups. If I routinely work in small startups which are likely to fail, then spending time in aspects of the stack which are likely to be needed at future startups is a smart use of my time. Micro-services have fairly extreme upfront deployment/automation overhead relative to monoliths. This setup effort is common across many firms adopting microservices.
- TexanFeller 3y ago
  I've for sure found myself thinking along those lines in the past. It's definitely possible it's a common enough thought to affect culture as you suggest.
whstl 3y ago
Interestingly I had the opposite. The more recent interviews I did asked about the advantages and disadvantages of using monoliths vs microserviced, and how to overcome the common problems. I also had questions asking me how I would write frontend applications with and without central state management, or even for which cases I would start with a reactive frontend framework. In one of them I even had a huge disagreement with the interviewer. He still made a point to say I had passed. I think the main difference in this case was that I was interviewed by seasoned pros. When I had interviews with less experienced developers, the topics were as trivial as possible and just looking for confirmation.
- eecc 3y ago
  I guess you and the parent are sampling the microserivce hype curve at different points in time.

lumost 3y ago

I wonder if this incentive is stronger at smaller startups. If I routinely work in small startups which are likely to fail, then spending time in aspects of the stack which are likely to be needed at future startups is a smart use of my time. Micro-services have fairly extreme upfront deployment/automation overhead relative to monoliths. This setup effort is common across many firms adopting microservices.

TexanFeller 3y ago
I've for sure found myself thinking along those lines in the past. It's definitely possible it's a common enough thought to affect culture as you suggest.

whstl 3y ago

Interestingly I had the opposite. The more recent interviews I did asked about the advantages and disadvantages of using monoliths vs microserviced, and how to overcome the common problems. I also had questions asking me how I would write frontend applications with and without central state management, or even for which cases I would start with a reactive frontend framework. In one of them I even had a huge disagreement with the interviewer. He still made a point to say I had passed. I think the main difference in this case was that I was interviewed by seasoned pros. When I had interviews with less experienced developers, the topics were as trivial as possible and just looking for confirmation.

eecc 3y ago
I guess you and the parent are sampling the microserivce hype curve at different points in time.