2 ms·
> Maybe instead you could probe at interview time whether they are happy with their microservices There is no way anyone tells you in interview that the codeba
by pjerem 5y ago
> Maybe instead you could probe at interview time whether they are happy with their microservices
There is no way anyone tells you in interview that the codebase is crappy or that they are unhappy with.
You’ll always be told « well, like everywhere, we have legacy, but we learnt for it and now every new project is in [put REST + shiny front tech here] and we are happy with it. We migrate step by step ».
And then you’ll realize that the codebase they called legacy is what makes the company’s money, it’s not that bad compared to new project and is a pain to maintain because nobody works on it anymore except for urgent bug solving.
So, they’ll probably tell you that « they are happy with their microservices » (or quite happy) because they already try to fool themselves about it.
- Trasmatta 5y agoThis is so accurate it hurts. No interviewer is ever going to say "dude, our codebase is terrible. The CTO wrote most of the core logic 9 years ago and everybody is afraid to touch it, so we just paper over it with increasingly complex interfaces and abstractions. There are like 25 different ways of doing everything, because every 6 months a dev comes in and thinks we should use their favorite new design pattern everywhere, but then gives up halfway through implementing it. Everything is either massively over engineered or complete spaghetti."
- zimpenfish 5y agoTo be fair, I have had that conversation in a couple of interviews but then I'm usually coming in as a contractor to patch up these kind of things.