Email or username:

Password:

Forgot your password?
11 comments
Cecelia

@yogthos A table with three settings labeled Commit, Dev, and Prod. Commit has a set of a few balls that roll to Dev which starts another ball rolling around a plate which starts a small barbell rolling along a cloth with a catch for the barbell, the barbell catches the cloth and cleanly pulls it from beneath the set of dishes. This triggers dominoes that start another process for Prod with a big tower of dishes and a much larger barbell which, when it catches the towel, pulls the whole table over.

Bill Bennett

@yogthos I don't even know what commit, dev and prod refer to.... presumably something to do with software?

Even so, this seems a perfect metaphor for the gap between any kind of planning and execution

Matthew Martin

@billbennett @yogthos commit is 1 change to the code
dev is the 1st environment (just a computer) you deploy to check if it works.
Large orgs will also deploy to TEST, STAGE... to check if it works two more times. (at one shop I was at there were like 6 environments to cascade thru & test at each)
Finally you deploy to prod the *real app everyone uses* & you find out there was something different about prod than all lower environments and you're up until late trying to fix it & everyone is mad.

Gabriel Rodríguez

@yogthos This is the most accurate representation I've ever seen 😂

Enkiusz🇺🇦

@yogthos the funniest part is that the cord in prod tied to the table was clearly visible from the beginning. And yet...

Go Up