Programming is a one-person task. Looping people in gives the rest of
us something to schedule meetings around. So it really depends on what
you want, getting the job done, or creating more jobs.
Actually writing fresh new code is a one person task if nobody ever sees that code again. If someone has to read that code, it's a team activity. If you have to read someone's code, it's a team activity. Determining what to write, what _not_ to write, how to write it and why, are all team activities, often shared with non programmers. Programming is a very social occupation.
I would _love_ to work in an organization where it was normal and encouraged to spend an hour with someone talking about what we want to do and how. no one wants to bother anymore.