rygine

Awake Security is an early stage network security and analytics company backed by Greylock Partners that is building a platform that takes a new approach to enterprise network security and monitoring. We process billions of events to give security teams microscopic to macroscopic visibility into their networks and enable data science for advanced threat detection.

The UI team at Awake is small, fast moving, and offers full autonomy in creating solutions. We're currently working with the latest versions of Chrome and keep our libraries/tooling up to date (when it makes sense). We're looking for someone who is passionate about security/privacy, design, user experience, and attention to detail.

UI tech: ES2015+, PureScript, D3, React, Redux, Webpack, PostCSS w/ cssnext, Jest, Enzyme, ESLint, stylelint, Yarn, Node 7+ Other tech: Scala, Haskell, Go, Kafka / Samza, Greenplum

Awake Networks is an early stage network security and analytics company backed by Greylock Partners that is building a platform that takes a new approach to enterprise network security and monitoring. We process billions of events to give security teams microscopic to macroscopic visibility into their networks and enable data science for advanced threat detection.

The UI team at Awake is small, fast moving, and offers full autonomy in creating solutions. We're currently working with the latest versions of Chrome and keep our libraries/tooling up to date (when it makes sense). We're looking for someone who is passionate about security/privacy, design, user experience, and attention to detail.

UI tech: ES2015+, PureScript, D3, React, Redux, Webpack, PostCSS w/ cssnext, Jest, Enzyme, ESLint, stylelint, Yarn, Node 7+

Other tech: Scala, Haskell, Go, Kafka / Samza, Greenplum

Specifically, these lines got to me:

>If we focus on solutions, focus on helping others, focus on sharing ideas, we’ll be in a better place. We’re all part of a broader community and we all have an impact on it. We can either have a positive impact or a negative one. It’s entirely up to us.

> This is the reality the community faces. We can either work to fix it or we can continue digging a deeper hole for ourselves.

At my company, we were using Lerna [1], a library to help manage mono repos. It wasn't perfect, but it worked. So I thought I'd contribute. I spent a good deal of time replying to issues, fixing bugs, and working on new features.

This was at a time when the author was mostly absent. Without the amazing help of gigabo [2] and hzoo [3], the project would have grinded to a halt. As new users rushed in to use this relatively new tool, there were many new issues and feature requests.

When the author did make his presence known, he was not very helpful [4] [5]. These are just the examples that stood out to me as a contributor. Most people understand that 1 person can't be expected to maintain a big project like this, especially when they are busy at Facebook bootcamp. That's why it had 2 additional members to help. Unfortunately, as a result of [5] above, the author decided he no longer wanted [2]'s help and removed him from the project. He removed a huge contributor because he disagreed with him and failed to openly discuss the issue. Ironic. I stopped contributing immediately. As a result, Asini [6] was born.

The thing that really pisses me off about this post from the author is that he's promoting open communication, sharing, helping others, etc... when it's the complete opposite of my experience with him. Maybe he just had a bad day on those days, maybe it was something else. I don't know him personally, I can only assume things based my interactions. Regardless, this was some extremely poor handling of an open source project.

It looks like he's active on the project again, but it doesn't look like much has changed. [7] [8] [9]

Mr. Kyle, if you're reading this, I really hope you'll follow your own advice. If I have misunderstood your actions in the past, I'm open to being wrong.