Programming

26036 readers

90 users here now

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 programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

106

Dealing with YOLO Vibelord colleagues (lemmy.world)

submitted 3 days ago by reabsorbthelight@lemmy.world to c/programming@programming.dev

47 comments fedilink hide all child comments

So my manager today asked me if I could stay later when there's broken things in prod, and then today his star dream employee yolo'ed a full stack change into prod without review. It's fucking massive and implements new API endpoints, touches >20 files. Many of the diffs are too large to render in the browser.

It's almost comical, but something immediately broke.

Most of my day, I'm digging through code to identify bugs created from this shit, just to get a stealth merge midday.

I kind of don't know what to do.

you are viewing a single comment's thread
view the rest of the comments

[–] Kissaki@programming.dev 5 points 3 days ago* (last edited 3 days ago) (1 children)

if I could stay later when there’s broken things in prod

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.

[–] reabsorbthelight@lemmy.world 5 points 3 days ago (2 children)

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

[–] Kissaki@programming.dev 1 points 1 day ago

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.

[–] Skullgrid@lemmy.world 7 points 3 days ago

Unfortunately the Vibelord is his favorite employee

escalation time