Website: https://workchronicles.com/comics/
this post was submitted on 13 Jan 2024
702 points (98.0% liked)
Comic Strips
12477 readers
3357 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- [email protected]: "I use Arch btw"
- [email protected]: memes (you don't say!)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Way to make sure they'll never improve. We have merge requests and four eye policy for this, no need for micromanagement. There's never a need for micromanagement, and if you feel like there is, your processes suck, which is your responsibility as a tech lead.
That's really not enough.
Review stops people from polluting your repo with bad code and lets you give feedback.
It doesn't stop people from wasting time writing unfixably bad code that just needs to be thrown out.
Now of course what you can do is give people very small coding tasks and regularly review them before getting it into a shape where it can go in the main repo. But this is just micromanagement via git.
Yeah, I'm glad for redprog that they haven't ran into this sort of thing, but sometimes you end up with people where you sort of have to sit on them a bit to get usable code that you even CAN code review out of them.
I even had one contractor who would, from the very start, refuse to do any work without a step-by-step list of implementation details as his 'project requirements.' First time I've ever had someone DEMAND me to micromanage them. I fucking hated it, I was spending nearly an hour and a half for each hour of billable work I was getting out of the guy. I can only assume some client in the past was wishy-washy about requirements with him, and I totally feel for him on that, but I personally feel he was taking it a bit far lol.
Only upside of that clusterfuck is that it gave me the political position to ensure that no more contractors were hired to work with my team without someone on my team being involved. The quality of our contractors went up rather significantly at that point.
If that person made it through the probation period under your supervision, that's still your fault. And if that person was there from the beginning, a senior in your team could still support them by teaching them good practices, showing them better options, etc. Or, as a last resort you could always assign them tasks that are more within their capabilities.
Micromanagement will never lead to people improving - quite the opposite in fact, they'll start to care less because there's always someone who prevents them doing mistakes.