> My only concern is to design and implement what they ask for. Whether what they ask for has any value, it is not my responsibility. You're describing a compi

> My only concern is to design and implement what they ask for. Whether what they ask for has any value, it is not my responsibility. You're describing a compiler. You are not a compiler; you are a software engineer. You will, especially as you get more senior, be asked for things that are wrong. You will be asked for things in the form of a fuzzy problem statement with no direct guidance on what to change, with the understanding that you will talk to relevant people and figure out what needs doing, and then you'll build that. One day, your job will be to figure out, with no prompting whatsoever, what things need to be built, and you'll build those things. Your job isn't "to create value," but it's not "build the thing as described without questioning it" either. That's a compiler.