>A programmer is given a very specific set of tasks (eg. send data from A to B, fix bug, implement X), and his problems are mostly technical. I don't think thi

>A programmer is given a very specific set of tasks (eg. send data from A to B, fix bug, implement X), and his problems are mostly technical. I don't think this is a fair comparison. This is actually one of those cases where I like the distinction between "programmer" and "coder". What you're describing sounds like a "coder" or a "code monkey," not at all like what I do in my job. If you were to translate this job over to art, it would be something like tracing over lines, making very minor touchups to pre-specified areas, or perhaps mixing paint. An artist who has complete freedom over their tools and their subjects would best translate to a programmer who also has complete control over their tools and their subject. They are not beholden to a company for specifics, except perhaps that something actually gets built. More likely this is one person who has an idea for a project and designs and implements everything themselves - and spends more time considering what features to add, the best way to add them, or otherwise experimenting with techniques, than actually writing production code.