Blue screen as I login? Yes, it is Monday morning, why do you ask?

We work in an office where we must lock our computer screens because our screens may have confidential information on them, plus you could do things as the person without taking any blame (ie sending an email).
Anyways anytime someone forgets to lock their screen we always prank them pretty hard. The greatest thing we ever did was in our latest release we had our managers buy us drinks at the pub. Well our managers left to go to the pub and one of them forgot to lock their computers. So we downloaded an image of the blue screen of death and made it full screen, unplugged his mouse and keyboard for added effect, and locked his computer. He came in the next Monday and couldn't log in because his keyboard wouldn't work. He actually called IT to bring him a new keyboard and mouse... then he unlocked his computer and freaked out with the IT guy because there was the blue screen of death. Needless to say he got a brand new computer as well as a new mouse and keyboard.

I'd call it a win win?

Monday : Trying to work when a Windows Blue screen attack xD

I want to talk about my last six months at work. Who wants to hear it?
Spoiler alert : from introverted nerd to Talkative flirt
What did it cost? Everything.

Came to work this morning with a bunch of cards coloured red, marked "urgent"...

And it's Monday... the day after Sunday...

The blues day...

Blue's my favourite colour, but this blue (and reds) I do not like...

Ok snoozy mind of mine... wake up!!

It was in May and I had a recruiter call be up about an interview for a dev position. I went to the interview, thought it went all right and awaited feedback.

Nothing came... I called the agency a few days later and he said he'd get me something back by end of the week.

Still nothing. I called again and he was all "oh sorry, I forgot, and I'll get it tomorrow".

You can probably guess; nothing. A couple weeks pass so by now I'm pretty confident I don't have the job, so I continue looking.

Then early afternoon on a Friday in November that agency calls back:

Agency: "Hi, how are you?"

Me: "Hey, I'm fine"

Agency: "Excellent, remember that interview in May for that company?"

Me: "Yeah, why have they go another position available?"

Agency: "Better, you start work with them on Monday"

It took the guy 6 months to get back, nothing from him or the company. Then he calls up out of the blue. No idea what he would be done had I already got a job.

I actually did accept, still work there now 4 years later, for now.

A CASE AGAINST BLUE PRISM
Let's review one of the worst weeks I had with Blue Prism

Monday: Yay! Solved one of the problems we've been carrying around for a week before.

One of the robots suddenly became slow. Like, REAL slow. A process that would take 3 minutes per record now takes 45, and that broke apart all the following schedule.

There were no updates on the application server, the production machine, the robot, it just became slow. And not always slow; a process manually run from console room would work, a process in debug room would work, it's just the scheduled part that caused problems.

It turned out, BP didn't seem to like that particular combination of schedulation + process + machine. Moving the process to a different machine seemingly fixed that. IDK why.

Tuesday: One of our processes waits for a code to appear in the page, and when that happens, it memorizes this code. However, now it is always returning blank. Worked for months, now it breaks every single time.
After half a day of debugging a bug which DIDN'T HAPPEN IN DEBUG MODE YET AGAIN, at 11pm I decided to just place a nonsensical timeout in page before reading and call it a day.

WEDNESDAY: a scheduled process didn't start. "No sessions created". Thanks Blue Prism, very cool.

THURSTAY: This time, schedulation did start, but the process is "waiting". As in: it's 9:30 am, the process has been stuck in the same step since 6:00 am. Turns out, it blocked during a navigate stage; you need to send a string to clipboard using the standard BP action for that, then paste and click "enter", but for some reason the standard BP object sent "ORRCO" instead of "ORRICO" to clipboard, which obviously returned no results and then... the process just didn't feel like doing things anymore. No errors, no logs, nothing: just sitting on its ass. Because fuck you that's why.

Friday: another process uses a very moderate amount of scripts to work. Nothing really fancy, just a couple of lines of code to place in page some IDs and selector to help BP do its thing, otherwise selecting these elements would be a nightmare.

But

Failed while invoking javascript method:Exception from HRESULT: 0x80020101-> at mshtml.HTMLWindow2Class.IHTMLWindow2_execScript(String code, String language)

The same script -it's not dynamically generated-worked yesterday, the day before and the day after. But sometimes it will not. Why? The answer, my friend, is blowin'' in the wind