I view thinking about the problem, researching the problem, etc, as being indivisible from the coding aspect. Really, it's telling how -I- feel after a day spe

I view thinking about the problem, researching the problem, etc, as being indivisible from the coding aspect. Really, it's telling how -I- feel after a day spent in meetings. It feels wasted. I'm grumpy that I achieved nothing. Whereas a day without any meetings, where it's head bent down, writing code, even when it involves research or looking up API docs, or going to ask questions of domain experts when interacting with other systems...feels productive. Even when some of it changes because the customer comes back and says "No no no, it should work like (X)". Honestly, it feels more productive when the customer can instantly tell me what is wrong after the fact, than if I spend an hour up front trying to pick their brains, to then code it, and to -still- find out it's wrong. Per another thread we had here, people find it much easier to tell you what is wrong than to tell you out of the air what is right.