This. (read the comments)
It reminds me of a time I was trying to write similar collision detection for an XNA project.
Not many relevant code samples in C# back in those days.
I was running out of time (I needed the feature for a scheduled demo) and ended up using a dll someone had published.
All of reddit.com/r/ProgrammerHumor is worth checking out.
As a guy who is still working on his own minimalist game engine (in Java), I understand how he feels.
Last time I checked it, there was a “Volume Slider” epidemia.
Oh boy, remember the phone number input cancer?
That page is gold!
“Asked the team lead one too many questions last week and this showed up today”
A former head of technology I worked with handed out little rubber ducks to every programmer in the company, to support what is called rubber duck debugging.
The problem at that time was that these little rubber ducks made a horrific squeak noise when squeezing them, which obviously everybody was doing the first weeks and programming productivity pretty much halted at this time 
Sound approach, but poor choice in the rubber duck model I’d say. BTW, does this have a fancy acronym too, like RDD? Or RDDD? Rubber Duck Driven Development? RD³? Can we go deeper?
I am not a programmer by trade. I learned basic on an apple lle and graduated to turbo pascal before life kicked in and I had a real long break. Now I am back at it with c# and unity. Rubber duck debugging is something i had not heard of but I do it unconsciously. My wife frequently looks over and shakes her head as I point at the screen and mumble to myself. I never really realized that was what was goin on. Explain it and it makes sense…well yeah. I will have a new rubber duck tonight. I think i will name her sally. She will be a good listener and always know when to just stare blankly looking for further explination of the current problem. I hope this dosent start some weird fetish or mental crutch…sort of.
I named mine Howard, obviously after Howard the Duck 
I think the dude could as well quit and change the jobs. If it took them several days to come up with solution, and they didn’t find separating axis theorem and one of the many examples, their gamedev future looks grim.
And yes, shooting rays doesn’t work. Been there, tried that.
RDDDDDDDD
Rubber Duck Deep Digital Debug Driven Development Decoupling Direction
I think we’re approaching Red October depth here.
Another one that could have been written by me.
