Back in game dev final year, working on GameCube kits, I encountered a weird rendering bug: half the screen was junk.

I was following the professors work and was bewildered that mine was broken.

The order of the class (c++) was different...
I think there was a huge leak somewhere and the order of the class meant memory was leaking into VRAM. I never had the chance to bug hunt to the core of it... Took a while to realise it was that...

It opened my eyes to respect memory haha.

This is not just an obligatory 'stickers have arrived' post...

...this is a farm assured, oak smoked, northern tale of sticker arrival, infused with succulent, Instagram filtered, bengal pet photo...

This is not just any rant... this is an M&S devRant.

"What is going on... this should work?!
Is my maths wrong?
My maths is wrong...
Oh no!
It's a model view projection matrix?!
I'm shit if I'm failing at this, it's 3D dev 101!
I got a first class degree... I don't deserve any of this or this job!!"

<2 seconds later>

uniforms.viewMatrix.set(camera.matrixWorldInverse.elements);
uniforms.viewMatrix.set(camera.projectionMatrix.elements);

"You set the same uniform twice you tool, due to copy and paste..."

Imposter syndrome in my early days put myself into a roller coaster of emotions. I always compared myself to others to the detriment of myself.
Thankfully overcame that working with some great guys.

But yeah, coding has impacted life for the best though. The challenge, creativity and constant learning is beautiful.

!rant but recommendation:
"JavaScript: The Good Parts" Douglas Crockford.

I really like this book.
It's chewed away my misconceptions of JS. Especially coming from C++.

Small and precise.
JSON, JSLint and JSMin developer is the author.

max - min != center.
(min + max) * 0.5 does though...

I astound myself sometimes on Friday afternoons...

Assert ref != NULL rather than conditional check it more often.

Silently returning / ignoring is way worse if object was meant to be valid.

The caller should deal with it. (As abstract as possible preferably...)

Obviously there's places where conditional is necessary.. but silent null checks can cause more pain than good.

TL/DR;
Worked as outsource where Scrum was misused. Please use it as a guide rather than law.

RANT;
Just remembered working as an outsourced programmer...

The Scrum master got us all... all of us... everyday... most people on Skype too... to update with our plans, issues etc.

So including the time trying to get everyone to sync up on Skype at around 9am, introductions, updates from EVERYONE... back and forth suggestions... I'd be starting near midday.

The task was related to making a tile based menu system that was populated with items from a backend... On paper, I only really needed to talk to the 1 artist and the 1 backend guy to understand the request / responses.
But even the art assets were arbitrary sizes... untileable... at the time they even had to be power of two too... My god, getting them changed was a nightmare...

In the end I was too slow for them.
Gladly.

At the core, alongside repositories and IDEs, the trusty pen + paper is best for seeing bigger picture and fast note taking.
Although my chicken scratch handwriting isn't one to rave about.
It's changed from cursive to curseive over time...

float version = 1.8f
if (version >= 1.8f)
{
/*
Do nothing because you forgot
about floating point precision
you tool...
*/
}

I.. I'm sorry... I'll sacrifice some virtual chickens to appease the Gods.