Aboutfuck code ninjas. I hack my way through code and get shit done.
Joined devRant on 8/3/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Spent days telling people what to do. What the database fields should look like, went down to every little bit, which was annoying because I hired them to think for themselves.
Spent a couple days verifying this and that. "Is this field really needed?"
Of course it's needed, otherwise why would it be in the specs? It took me two fucking days to communicate on these things they could have just done in half an hour.
They do it wrong. It's been clearly outlined and it's still wrong.
Management then insists on more communication so things don't go wrong. We have meetings every day to discuss what must be done. Every other day we have meetings between another project leader to discuss what we just discussed. Every two days we have progress report meetings.
We spend 70% of the time communicating now and everyone still gets everything done wrong. This is why you have to be really, really careful when hiring. Technical interviews can just be giving someone a spec and seeing whether they can do it.