Programmer Humor

19454 readers

18 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

724

Old timers know (sh.itjust.works)

submitted 4 months ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev

117 comments fedilink hide all child comments

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

[–] jet@hackertalks.com 13 points 4 months ago (4 children)

Promotes/deploys are just different ways of saying file transfer, which is what we see here.

Nothing was stopping people from doing cicd in the old days.

[–] tiramichu@lemm.ee 20 points 4 months ago* (last edited 4 months ago) (3 children)

Sure, but having a hands-off pipeline for it which runs automatically is where the value is at.

Means that there's predictability and control in what is being done, and once the pipeline is built it's as easy as a single button press to release.

How many times when doing it manually have you been like "Oh shit, I just FTPd the WRONG STUFF up to production!" - I know I have. Or even worse you do that and don't notice you did it.

Automation takes a lot of the risk out.

[–] anonymoose@lemmy.ca 3 points 4 months ago (2 children)

Not to mention the benefits of versioning and being able to rollback! There's something so satisfying about a well set-up CI/CD pipeline.

[–] Pacmanlives@lemmy.world 2 points 4 months ago (1 children)

We did versioning back in the day too. $application copied to $application.old

[–] anonymoose@lemmy.ca 1 points 4 months ago

But was $application.old_final the one to rollback to, or $application.old-final2?!