[0924] Oops
└ posted on Thursday, 28 September 2017, by Novil
Good artists copy. Great artists steal.
- Richard: Ah, bliss! Friday, 3 o’clock, and everything’s ready for the big release next week!
- Colleague: Oops.
- Colleague: Nothing’s wrong. Da Dee Doo Ba… I just want to fire up my old computer to check some… stuff. Ta Tum Ta Tum.
- Colleague: Let’s see. Is there a database backup? Dum De Doo. No cause for alarm… No need to panic… I just need a database backup. La La.
- Sandra: You might be coming home tomorrow night?!?
![[0924] Oops](/comics/2017-09-28-0924-oops.png "[0924] Oops")
Loading ...
So… Richard works for GitLab?
The pain is real! :/
I love being a bureaucrat in local government. 5.15pm on Friday: Nope, doesn’t matter, can wait until Monday.
That facepalm hurt so much I felt it in my spine. YOWCH.
“Well, ████. This sure put a damper on my mood.”
“Oops”. The scariest word in a lot of professions.
I…. don’t get it?
#34 of the most famous last words: “oops”
Is beeing killed by your colleagues after something like that considered as occupational accident?
Thisguy wrote:
I feel the sudden urge to binge-watch episodes of Parks and Recreation…
Backups, backups, backups!
@ 00m:
You know that feeling when you accidentally deleted your book report for school?
Now, imagine you’re a programmer and just erased your assigned project.
Richard’s coworker just messed up big-time. I suspect he’s going to scrounge some open-source and spaghetti it in.
I prefer to develop with a dummy database of randomly generated (more or less realistic) data. At least where that’s possible.
On the other hand, losing source code would be even less of a problem, since git automatically generates backups every time you commit a new piece of code. 🙂
This is terribly familiar…
00m wrote:
In programming, one small mistake or problem can set you back a long time. And this looks like a big mistake or problem hence why he’ll be working on it for more than 24 hours straight.
He just needs to get some buckets to hold some…stuff.
By the way I love how your comic has the soul of Calvin and Hobbes. XD
people were murdered for less lol
@ KarmaTheAlligator:
And this is how you learn to use automatic backups. Most people don’t make this mistake twice.
Well, we all know what this calls for, Sandra. PARTY!
If it’s pre-release, the database shouldn’t contain a lot of valuable data. If it does, then they’re keeping too much statics, or worse, schema and programmability, in the database.
Usually, database-destroying queries on a production database only happen when the boss makes unreasonable demands for changes that would normally amount to a system over haul. And yes, you’d be wise to back up the database before running them.
Problems like this often more happen when doing maintenance on very VERY old code, that you didn’t write, and feel like the person who wrote this should be ashamed of themselves. That Richard is facing this with a brand new release makes me question his design skills.
Also, one does NOT release right before the weekend. You do NOT want to know what breaking bugs are revealed on release, when you’re trying to get some RnR.
I think that guy in the back should be tagged “Calvin.”
http://pin.it/8GH2cIH
Love the Calvin and Hobbes reference
Ironically this happened to me yesterday.
Been there, done that, worked the 40-hour weekend….
SlugFiller wrote:
They were not releasing on Friday. Richard explicitly says that everything’s ready for the big release *next week*.
OTOH, putting *anything* into place from a backup right before a release is going to require an entire new, full, round of regression testing. That could easily make for a 24-to-40 hour weekend (says the voice of experience)….
Centaur wrote:
Thanks for the reference — I was wondering how a pending update would create an immediate emergency as they wouldn’t have been working on the Live database. That “Colleague” was accidentally working in the wrong folder makes more sense.
That said, why is “Colleague” looking for a database backup on an old pc? Unless the old PC had a recent (pre-update development) database snapshot, shouldn’t the Live database have had recent backups that are more current then would be found on an “old PC”?
There are three people you never want to hear say “oops”.
1. Your doctor.
2. Your pilot.
3. Your co-worker.
Three people you do not want to hear the word oops from.
The mechanic.
the data processor
and the surgeon.
I wouldn’t want to hear an “oops” from my dentist, either.
Calvin and Hobbes anyone? Even the dialogue and expressions are almost identical XD
Another three people you do not want to hear the word oops from:
Crane operator.
Chef preparing Fugu.
Tax preparer.
Thou shalt strive to push to production on a Monday.
And on the day this comic strip got posted thousands or maybe even millions of passengers couldn’t check in to their flight because of a software problem.
Coincidence? You decide!
http://www.telegraph.co.uk/news/2017/09/28/worldwide-airport-chaos-check-in-computer-systems-crash/
TvTropesgotmehooked wrote:
I disagree on 2 and 3. If you HEAR the “oops”, then that means they caught it before it went out.
Kein Backup, kein Mitgefühl.
Is it me, or is this comic slightly blurrier compared to the rest? Like it’s slightly larger and being squished down or something.
Inspecting the images directly actually reveals that this comic is 8 pixels wider than usual, so that might do it. ;o
foducool wrote:
Justifiable Homicide.
Thisguy wrote:
Do you mean to tell us that bureaucrats in your country work as late as 5 pm? At that time in Germany they would be long home on a Friday.
Okay the deliberate Calvin and Hobbes joke is enormously cute!
I just want a bucket to hold some…. stuff.
I guess you’re only a good artist then.
As a software developer, I have been there and done that.
git reset –hard on the wrong branch ruins the day.
@ SeanR:
I guess it’ll depend on when they say ‘oops’ 🙂 if they realize when it’s already too late ^^
Richard Sheaves-Bein wrote:
… assuming there IS a working backup.
Once years ago, I had to restore a backup for a file that had been trashed (hardware problem).. Submitted the IBM batch job (this is years ago remember); got back a note from the operator – “That’s funny, there are two physical labels on the tape case!” (YEARS ago!)
Yep. The only backup tape had been overwritten. Not a good day; killed the project. Fortunately it wasn’t a CRITICAL project but it would have been better had it been saved!
I unfortunately know this feeling. I work as a security guard at an electronics warehouse. I come in at 8 a.m. and they tell me that we could get out at 7 p.m. but then at 6:45 p.m. it turns out we gotta wait for another truck to come in and then I don’t get to go home until 10 p.m.
@ Cirom:
How did you catch that?
I went through trade school, where one of the teachers told how, while working, you are not allowed to utter word “oops”, under any situation… it was THE forbidden word.
why is the a calvin and hobbes tag?
@ d.Artemis:
Because it’s from a Calvin & Hobbes strip. The comic has referenced Calvin & Hobbes several times. There is even a reference in the upper left corner of the site page.
Two people you NEVER want to hear say, “Oops”, your doctor during minor, local anesthetic surgery and your computer tech. LOL.
As Bloom County pointed out many years ago, you also don’t want to hear it from somebody who works at the local nuclear reactor.
Murphy’s Law should be in the tags, imho
3 more people you don’t want to hear say “opps”.
1) An explosives “expert”.
2) A person working on a working power system.
3) Anyone near a high pressure line.
Once had my own scary moment while on the top mast of a nuclear “wessel”. Suddenly they shouted over the ship’s P.A. “SCRAM THE REACTOR! SCRAM THE REACTOR!” Turned out it was a drill. (So they said.) In hindsight it would not have mattered if I had been on the ground. If the reactor had failed I was well within the 100% fatality zone. Nuclear power is pretty failsafe but 3 Mile Island and Chernobyl prove it can happen. Of course the facts prove they were the result of massive amounts of human error.