- Your job won't always involve doing things you like doing. If you're stuck in jobs which use tech you don't like, at some point you have to accept that said tech is here to stay and spend just your work time on it. It's not a great choice, but jobs are like that more often than not.
- If, as you say, containerisation is a bad idea for most companies (I wouldn't know - my company uses the "boring" way of deploying our services), you just need to point out how it's hindering them. I'm sure when management starts wondering why their platform bills are going through the roof or features take ages to go live, you can pitch the boring way to management and make your case with actual facts.
Yes, it's true that at some point I have to stick with a tech I don't like. In general I don't mind doing that. At the end of the day I work for money. The question I'm asking myself is at which point that might be.
Sadly when interviewing I'm not in the position to point out architectural pain points. It feels impossible to argue against k8s. Every time I tried that I get some unreflected cargo cult answer. The people I interview with already invested in k8s so it seems pointless to indicate that there are some massive downsides.
Comments
Two things here:
- Your job won't always involve doing things you like doing. If you're stuck in jobs which use tech you don't like, at some point you have to accept that said tech is here to stay and spend just your work time on it. It's not a great choice, but jobs are like that more often than not.
- If, as you say, containerisation is a bad idea for most companies (I wouldn't know - my company uses the "boring" way of deploying our services), you just need to point out how it's hindering them. I'm sure when management starts wondering why their platform bills are going through the roof or features take ages to go live, you can pitch the boring way to management and make your case with actual facts.
Yes, it's true that at some point I have to stick with a tech I don't like. In general I don't mind doing that. At the end of the day I work for money. The question I'm asking myself is at which point that might be. Sadly when interviewing I'm not in the position to point out architectural pain points. It feels impossible to argue against k8s. Every time I tried that I get some unreflected cargo cult answer. The people I interview with already invested in k8s so it seems pointless to indicate that there are some massive downsides.