*open blog*

Article looks good lets read it

*Scroll 1mm*

*THIS FAT ALERT BOX ACROSS THE ENTIRE SCREEN WITH NO X BUTTON SAID YOU HAVE TO REGISTER TO CONTINUE READING THIS ARTICLE WHAT ARE YOU GONN-*

*ctrl + w*

"Don't deploy on Friday" is a public admittance that your company either has no CI/CD pipeline, or that all your devs are retarded rhesus monkeys who only wipe their ass if the product manager wrote it as a spec.

If the saying was: "Don't port your whole API to GraphQL on a Friday", or "Don't switch from MySQL to Postgres on a Friday", I would agree.

But you should be able to do simple deploys all the time.

I deployed on Christmas & New Year's eve. I've deployed code while high on LSD, drunk-peeing 2 liters of beer against a tree after a party. I've deployed code from the hospital while my foot was being stitched up. On average, we deploy our main codebase about 194 times a week.

If you can't trust your deploys, maybe instead of posting stupid memes about not deploying on Fridays, you should fix your testing & QA procedures.

Fuck me the goalposts move so quick at the moment that we cant even get code released before it's out of date.

Learn git right after you learn your first programming language.

Knock, knock.
Race condition.
Who’s there.

package FirstRant

import "fml"

func main( ) {
fmt.Println("Hello, DevRant")
}

Do not disturb someone especially if they are in the zone.

Hint : earphones on, a ton of error logs on screen.

To the new devs:
Never push production on friday

Naming advice for new devs:

Test
Test1
Testtest
Final
Finalfinal
Final1
Asdjsfkd
Jkhfd