> At the end of the day, their job will only be transforming my thoughts into code.
Technically, part of their job is transforming your thoughts into requirements, presenting options and recommendations about how to resolve problems (or even a different problem to solve), determining what's even possible (and what other possibilities are), and determining what code actually needs to be written.
Someone who is good at those parts is no more easily replaceable than a brilliant business mind with tons of contacts and much more difficult to replace than the vast majority of "ideas and thoughts" that they're working with.
For a high level software developer, "coding" is the least of the responsibilities; it's the easy part.
Technically, part of their job is transforming your thoughts into requirements, presenting options and recommendations about how to resolve problems (or even a different problem to solve), determining what's even possible (and what other possibilities are), and determining what code actually needs to be written.
Someone who is good at those parts is no more easily replaceable than a brilliant business mind with tons of contacts and much more difficult to replace than the vast majority of "ideas and thoughts" that they're working with.
For a high level software developer, "coding" is the least of the responsibilities; it's the easy part.