This sort of thing also tells me that people have an incorrect notion of what our work is really like. As a senior developer, I spend quite a bit of time interacting with people: discussing the problems our customers have; how we can make our product better; how I can make other coworker's jobs easier; how my systems will interact with other components; reviewing proposals, feature requests, and requirement documents and providing feedback to help refine them; reviewing other developers' code and mentoring junior members of the team.
I absolutely _don't_ spend 8 hours just interacting with a computer. I won't argue that there aren't any jobs in the field like that; and, in fact, entry-level positions do tend more towards "just implement this spec". But I think it's misleading to give people the idea that there is no human interaction involved in our jobs.
Comments
This sort of thing also tells me that people have an incorrect notion of what our work is really like. As a senior developer, I spend quite a bit of time interacting with people: discussing the problems our customers have; how we can make our product better; how I can make other coworker's jobs easier; how my systems will interact with other components; reviewing proposals, feature requests, and requirement documents and providing feedback to help refine them; reviewing other developers' code and mentoring junior members of the team.
I absolutely _don't_ spend 8 hours just interacting with a computer. I won't argue that there aren't any jobs in the field like that; and, in fact, entry-level positions do tend more towards "just implement this spec". But I think it's misleading to give people the idea that there is no human interaction involved in our jobs.
Yes, but when you first take the job you'll spend at least a couple of years dealing mainly with just the computer.