You can’t code during a conference call
A company of programmers produces code. A company of managers produces meetings.
Can we talk for a minute about how irritating this smarmy attitude is? It’s the conceit of anarcho-syndicalists writ small. It’s assembly workers complaining about supervisors, masons complaining about architects, and rogue cops complaining about The Chief. It’s Dilbert.
“We could get so much more done if only management would stop getting in the way.”
Look, if you are going to work on anything that has more than a few moving parts, someone is going to need to coordinate and make sure that everything is moving in harmony. If you are going to have clients or customers, someone is going to need to talk to them, process their needs and then filter them into design changes and requirements docs. If you are going to test your software, someone will need to do triage and fit feature-set to budget and schedule.
Every hour that you spend on this is an hour that you are not programming.
Are you going to too many meetings? THEN YOU HAVE CRAPPY MANAGERS. Good managers hold meetings only when they’re needed and spend a great deal of their time shielding employees from the minute to minute neuroses of clients, investors and the public. Good managers reign in the natural over-enthusiasm of programmers to realistic commitments and judiciously nudge development along the right paths, ensuring that time is not lost on wasted or unimportant features.
Good programmers understand that code is not software and see a value to maintaining an overall direction and vision for a project. Then they either hire good managers or sacrifice one of their own and ‘promote’ them out of active development.
photo credit: Paul Mayne
