I've not been a dev for very long, but I don't care for the "build to these specifications" approach. I like to know what outcome I'm helping achieve and why it matters because I think that knowledge helps achieve the outcome. This is part of why I enjoy software consulting.
I agree, but I have seen people of all kinds and preferences.
I've actually been stopped couple of times when I was explaining background - literal line: "Thanks Nikola, but I don't need the context - just tell me what the build and I'm happy:)". This was a team member who was a sysadmin, then tech architect, then decided knowing background and being responsible for outcomes was not contributing to his quality of life, and went back to sysadmin, and lived very happily ever after in carefully managed ignorance. I've seen a number of people who have decided their happiness is in scope management. I don't work like that, for now, but I fully understand that perspective.
