> we’ve tried to build as much as we can as to skip dependencies, I’ve spent enough time in rails to appreciate debugging owned code - an argument for another time...

Okay, I'll bite. I have no experience in RoR, but does this line suggest that RoR encourages NIH?

This line feels like that scene in a horror movie, right at the beginning, when the camera lingers a little too long on the janitor's face as he cracks a smile that's wider than it should be.

Red flags:

* NIH (mentioned above)

* Using Go in production (more specifically, complaining about the lack of support for Go in production -- you should have known what you were getting into)

* Announcing a hacked-together MVP to the whole company

* Escalated to a VP for a technical issue

* Not using the company's recommended workflow, instead building your own

There's no way that the inability for the author to deploy DocuSign, an API that hundreds of companies successfully use, is on DocuSign.

Also, an maybe this is just a cynical view, but when you start your cautionary tale with a literal, "It all started when I was 11", it's kind of hard to relate.