COV

Fellowship of programmers

Like many other things too, most software projects are rather large scale. Far too large for any individual to ever complete before most potential customers are long dead.

So we come together and we work together, we're pulling our resources in brains and thought and are pulling togehter.

We form teams, and we call ourselves the backend team or the ops team.

Teams of software developers necessarily need to discuss the issues at hand and reason about how to approach and solve problems. The team as a whole then has to implement the outcome of such deliberations of individuals at eye level.

To that end everybody must be on board and teams will often adopt some more or less established way of collaboration, more agile or less, maybe including interesting or odd company rules.

In the end it doesn't matter all too much as long as there is agreement and as long as it works for a specific team and in terms of getting things done that need doing.

What's important is that we stick to what we agree upon, trust in our teammates to do the same and go about our daily work the way we think is sensible.

When we cut corners, when we are lazy, when we think we know better and when we ignore the others, then we're not doing that. Then we're failing our fellow programmers, we create considerable amounts of unplanned und unwanted work for everybody and while we are very lucky to have a really cool job, we make it unnecessarily hard and frustrating.

Often enough all of that happens and more, and none of it on purpose. So we need to vigilent, keep tabs on such developments and be open and polite in bringing them forward and we need not worry: A fellowship can stomach that ;-)