133 karma · joined January 1, 2019
> Here's the trick: github.actor does not always refer to the actual creator of the Pull Request. It's the user who caused the latest event that triggered the workflow.
As someone deeply familiar with this problem (ex-JupiterOne), I'd caution against asserting that 'deep level of customization' is a differentiator. Your buyer (CISO) and userbase (Sec Engs) are drowning. They (and I) don't want yet another product to build on top of. This is a key reason why Wiz is so successful -- an operator can turn Wiz on and immediately receive value, no adjustments or additions needed.
I'd strategically focus on making the 'actionability' part the cornerstone of the product and really become obsessed with making that part of your product incredible. The Goliath-killing story you need will be formed by figuring out how to get your product to the point where someone can turn it on and immediately receive value for the most impactful security problems first (ex: Log4J) and the total surface area of problems the product solves for second.
Anecdotally, this has not been the case for me.
Similar to the parent, I have accelerated my learning tenfold by ditching D**** in favor of reading, watching, and listening to content in my target language as well as speaking to a tutor I found online.
I've wasted a tremendous amount of time going through and ultimately completing a tree only to find myself crossing the finish line not being comfortable saying anything in that language. Is that a criticism of me? Perhaps. But, the big D once fooled me into thinking the answer to that question was that it is. Which is to say, I don't believe it's a criticism of me.
fucking lol, the audacity