My colleague sent me this. Think before you act!

Hi Bob,

This is Alan next door. I’m sorry buddy, but I have a confession to make to you.

I’ve been riddled with guilt these past few months and have been trying to pluck up the courage to tell you to your face but I am at least now telling in text as I can’t live with myself a moment longer without you knowing.
The truth is, I have been sharing your wife, day and night when you're not around.

In fact, probably more than you, particularly in the mornings after you’ve left for work.

I haven’t been getting it at home recently, but that's no excuse I know.
I can no longer live with the guilt and I hope you will accept my sincerest apologies.

My wife has known for some time now and I’ve promised her that it won't happen again.

Regards, Alan.

Bob, feeling anguished and betrayed, immediately went into his bedroom, grabbed his gun, and without a word, shot his wife twice in the head, killing her instantly.

He returned to the lounge where he poured himself a stiff drink and sat down on the sofa.

He took out his phone to respond to the neighbour's text and saw he had another message:-

Hi Bob,

This is Alan next door again.
Sorry about the slight typo on my last text, I expect you worked it out.
Anyway, but as I’m sure you noticed, my predictive text changed ‘WiFi’ To ‘Wife’.

Hope you saw the funny side of that.

Regards, Alan.

So I recently had a university project which focuses video game audio. We had to work in groups of 3 students and the task was to create a video game which uses audio as a gameplay mechanic.

Our idea was to create a game where you collect different audio samples which get looped as background music, and you have to select the correct ones to have a nice tune. To make it a bit more challenging we had enemies, guns and grenades plus doors which only open if the correct music is playing.

The guns fire on-beat, and the grenades always explode on the first beat of the next bar.
It was quite challenging to get things synced since even small offsets are noticable.

I wrote some nice code and theoretically it should have worked but for some reason the gun shots and the grenades didn't quite hit the beat of the music.

I tweaked stuff, created workarounds, optimized lot's of code to get execution times down but it still only worked sometimes.

I tweaked more and more only to realize that the timing drifted over time.

At that time I worked 20-30 hours on tweaking and trying to get it perfectly timed.

After recalculating some numbers I realized that all the audio samples are recorded at 135 bpm, but the guys who did the recordings said it was 130bpm.

I asked them if it could be the case that the samples are 135bpm and they said:
"yes, they are at 135 bpm as we told you"

I scrolled back in the telegram conversation only to see that they said 130.
Changing the number to 135 resolved all the problems and all of my workarounds and tweaks weren't needed.

So I worked for nearly 30 hours just because they didn't notice their fault and even when they realized that the timing is off sometimes (which took forever because they never played the game), they didn't even consider that they might have given me the wrong numbers.

This all wouldn't be that bad if both of my teammates had worked for more than 15 hours but they didn't. I did all the hard work and the only single thing they did fucked up my workflow. It fucked up the system I created and it fucked up the gameplay as things got unpredictable. Because of their fucking fault I worked as much as both of them combined IN ADDITION to all the other work I did (built 3 maps, coded everything, created animations, ...)

I love working in teams, but only if the whole team is motivated. Those two fuckers were the exact opposite.
Luckily i found the error so I could fix it, but guess with whom I'll never ever work together again?

Ahhh i don't even want to remember... Dynamic text interpreter that will translate a PDF+excel to a dynamic data structure that will accommodate any changes... Where is my gun again?!