I'd still call that programming. Turning requirements into code is part of the job, and even if you spend all day doing nothing but listening to people spout in

I'd still call that programming. Turning requirements into code is part of the job, and even if you spend all day doing nothing but listening to people spout incoherent requirements at you, you're still wearing the hat of a programmer. Contrast that with a startup where you wear many hats at once, including spouting incomprehensible requirements yourself, and I think that's where I'd tend to agree with the parent poster.