Programming

17000 readers

94 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 [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

260

Let's blame the dev who pressed "Deploy" - by Dmitry Kudryavtsev (yieldcode.blog)

submitted 1 month ago* (last edited 1 month ago) by mac to c/programming

74 comments fedilink hide all child comments

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

[–] [email protected] 5 points 1 month ago (1 children)

Possibly the thing that was intended to be deployed was. What got pushed out was 40kB of all zeroes. Could've been corrupted some way down the CI chain.

[–] [email protected] 2 points 1 month ago (1 children)

Which definitely wouldn't have been a single developer's fault.

[–] [email protected] 3 points 1 month ago (1 children)

Developers aren't the ones at fault here.

[–] [email protected] 1 points 1 month ago (1 children)

Not the most at fault, but if you sign off on a shitty process, you are still partially responsible

[–] [email protected] 1 points 1 month ago

That depends entirely on the ability to execute change. CTO is the role that should be driving this.