Technology

70713 readers

5305 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

278

Let's blame the dev who pressed "Deploy" (yieldcode.blog)

submitted 10 months ago by [email protected] to c/[email protected]

61 comments fedilink hide all child comments

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

[–] [email protected] 20 points 10 months ago (2 children)

Was there a process in place to prevent the deployment that caused this?

No: blame the higher up

Yes: blame the dev that didn’t follow process

Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…

[–] [email protected] 32 points 10 months ago

If they didn't follow a procedure, it is still a culture/management issue that should follow the distribution of wealth 1:1 in the company.

[–] [email protected] 23 points 10 months ago (1 children)

How could one Dev commit to prod without other Devs reviewing the MR? IF you're not protecting your prod branch that's a cultural issue. I don't know where you've worked in the past, or where you're working now, but once it's N+1 engineers in a code base there needs to be code reviews.

[–] [email protected] 4 points 10 months ago (2 children)

Oh you sweet summer child...

[–] [email protected] 10 points 10 months ago

I would hate to work where you developed the idea a protected main/prod branch is something novel.

[–] [email protected] 10 points 10 months ago

I hate to break it to you, but companies with actual safe rails to deploying to production do exist.

And when things go wrong, it's never the responsibility on a single dev. It's also the dev who reviewed the PR. It's also the dev who buddy approved the deploy. It's the whole department that didn't have enough coverage in CI.