<-- home

The destructive power of Proactive Incompetents

Being proactive is nice, most of the times. There’s a threat full way of being productive: when you are incompetent.

On Compufácil we had an external team that was there to “help” the main equip to launch quickly.

Since the project was starting, they had to decide upon many things, soon their methods appeared to be ugly and many times we had endless discussions on pull requests.

They started doing a module by themselves, but as the time passes, and tasks of that module where given to us, we see how monstrously piece of bad design was there.

Here I have a point to make, we have code reviews, so why the code could be so messy? Well, turns out that our pull requests stayed for ours long being reviewed, and the discussions used to go on and on. To the point that we many times we’re called attention upon the length of the PR’s reviews. In these conditions even the most arduous crafter and careful of us may let some “minor things go”.

It reached a point that we rewrite all these module that they done.

The perception of the rest of the team about their professionalism was getting worse and worse.

We complain about them but it doesn’t help much, the perception was that, even they being incompetent, was better with them than without, so we where instructed to give only easy and mechanical tasks to them.

They messed half of the source code.

The parts of the system that stayed with them for long periods smeels to the point of throwing all away.

They almost completly desmotivated the REST of the group.

The pull requests took hours to review.

The requirements allways got worng.

And now that they are gone we have to live with their legacy.

Now that they are gone we will have to redo all the crap they did, once again, slowly and painfully.

I prefer a lazy but mildly competent collogue than an proactive and incompetent one.