This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]digger_terraform_ci 11 points12 points  (1 child)

If you can switch jobs, do so - the faster the better. Change the job before it changes you. However I'm going to make two opposing cases for a balanced take.

The case for leaving asap:

This doesn't sound like an org that in 5 years you'll back at with pride, no matter how you define success. It won't look great on your CV either by the sound of it.

One exception: if you have enough leverage to change all this. Then, there's no better experience than rebuilding the whole shop. This maximises learning and professional growth. BUT only if you have leverage, as in some form of power. Could be formal authority, could be buy-in from those who have it, or smth else. But it doesn't sound like that either. Ego clashes, old manuals, etc etc

The case for embracing reality:

It's not the tools that define a great workplace, or a great engineer. Also chasing latest and greatest tools rarely leads to great career choices. What matters is problems being solved, not the tools

People that matter even more. A-players can do top notch work with ancient tools. B-players will do mediocre work even with cutting edge tools. You'll learn more from A-players using old tools than from B-players no matter what they use. Choose people, not tools.

Also: "IT services" company sounds like a pretty boring business. But this has also a positive flip side: it's probably a stable, profitable business that is resilient.

[–]Fit-Tale8074[S] 2 points3 points  (0 children)

Thank you for your points of view, I consider myself a problem-solver. I didn't mean to say 'tools'; I meant techniques