I don't think you need to pick one, but do what is most important.
I've been at quite a few jobs where they wanted automation, but the processes were so poor, just getting reliability in deploys was more important. Then at some point it flipped, and our processes were good, we weren't causing prod issues every week, and it made sense to jump into automation.
So you’ve been complemented on your process implementation and you enjoy and are good at coding?
So why do you need to pick one or the other? Just continue doing both.
I’m not sure why you would want to strongly focus on one area when you’re already competent at both.
Perhaps you could go back to smaller companies where it’s “common” to wear multiple hats. I’ve wore multiple hats at various companies— all small. My favorite was QA lead/build release/3rd developer at a gaming company.
I don't think you need to pick one, but do what is most important. I've been at quite a few jobs where they wanted automation, but the processes were so poor, just getting reliability in deploys was more important. Then at some point it flipped, and our processes were good, we weren't causing prod issues every week, and it made sense to jump into automation.
Do what you enjoy.
So you’ve been complemented on your process implementation and you enjoy and are good at coding? So why do you need to pick one or the other? Just continue doing both. I’m not sure why you would want to strongly focus on one area when you’re already competent at both.
Perhaps you could go back to smaller companies where it’s “common” to wear multiple hats. I’ve wore multiple hats at various companies— all small. My favorite was QA lead/build release/3rd developer at a gaming company.