_pplp

4 ms·

1.
by _pplp 5y ago
I appreciate the perspective. If you're telling me I worked there at literally the worst possible time frame, I'd believe it. I may have my experience skewed through the perspective of Nick's influence, but tbh many of my iss
2.
by _pplp 5y ago
Oh god don't remind me about Trace. I had to deal with the Controller side of that and it was a damn nightmare. He basically dictated that you couldn't use any kind or repo+deployment pipeline except for what his team was building
3.
by _pplp 5y ago
> Nick was hired out of his job at Amazon because he was supposed to be the AWS expert. This always cracked me up. From what I can tell, he was a mid level dev on the Alexa web api team. He knew AWS sure, but he did not have the cred at
4.
by _pplp 5y ago
I've since heard that the repo has been taken down and all the keys rotated, but just kinda makes you wonder how many APs and switches and cloud keys, etc are still out there using compromised keys. Also, even though they may have had
5.
by _pplp 5y ago
Hoo boy, this is gonna be a fun one. For reference, I spent a year (mid-2018 to mid-2019) running the UniFi Network team and worked with Nick during that time. > * Why was it so easy for a lead engineer to get access to a root AWS user w
6.
by _pplp 5y ago
> This man was a senior developer Dude, let's not be generous. Could he write code? Yes. But this is a guy who wrote everything in Node, but absolutely _refused_ to use any existing libraries except for ones he personally wrote. He