I've come to the conclusion that there is zero upside in your job description requiring you to write code. You might have to write in Java, or lose a weekend every 9 weeks to production support, or maintain some shitty legacy code.
Instead, you want the freedom to write code, but a job title that makes it clear that you don't have to write any code. If you're a data scientist or an architect or in R&D, you get this freedom. It's best, in sum, if you get to build things and solve problems by writing code, but aren't seen as a cog that can be plugged into any code-writing or -reading hole.
Comments
"Software Strategist" doesn't sound, to me, like someone who writes any code.
I've come to the conclusion that there is zero upside in your job description requiring you to write code. You might have to write in Java, or lose a weekend every 9 weeks to production support, or maintain some shitty legacy code.
Instead, you want the freedom to write code, but a job title that makes it clear that you don't have to write any code. If you're a data scientist or an architect or in R&D, you get this freedom. It's best, in sum, if you get to build things and solve problems by writing code, but aren't seen as a cog that can be plugged into any code-writing or -reading hole.
You may be right. I was thinking more from a communicative standpoint than a job requirements standpoint.