Ruby developer. CTO. Swimmer. Always trying to write more
Communication is more important than coding.
ok, ok, I’m being provocative. We’re not all talk and no action…but good communication is a core principle of the team and is critical to the health of your project and the overall team.
What do I mean that “communication is more important than coding”?
Obviously, we need to actually write some code to build the features, and fix the bugs, and refactor away the technical debt. However, often there’s a choice and it’s in those moments that we should always prioritise communication:
You get it. It’s not that coding is more important than communication, it’s that if you are faced with a choice, the correct path is most likely in the direction of more communication and not more coding.
If you aim for
communication > coding I think you’ll hit the right balance. If you aim for
communication == coding or
coding > communication, you will not be effectively managing your project.
This is an extract from an internal post at Podia about project management for developers