166
Dealing with YOLO Vibelord colleagues
(lemmy.world)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
In general, or on this instance?
Do you have team retrospectives? That's where I would bring it up in my team. Raise my concerns, explore and understand what team consensus is around this topic, around risks, quality, etc.
If the team consensus and/or management consensus is YOLO - then I try to protect myself from personal investment and going beyond contractual obligations. Because I already know what will come and how it will negatively affect me personally.
It's possible a honest discussion with management about goals and risks could lead to clarified guidelines, requirements, and goals. If it doesn't, I'd probably be looking for a better job/environment. Because I'll be miserable if colleagues YOLO, no matter how careful I am personally.
I told my manager that we need to focus on quality. He partially agrees, but part of the problem is that he didn't even know how to get to our company git repo till I showed him. All he knows is the front end.
Unfortunately the Vibelord is his favorite employee
I obviously don't know your environment, but I don't think a manager needs access or knowledge to git to effectively manage teams, hear and understand team member concerns, and to steer guidelines and guardrails.
escalation time