Today I was let go from @CrowdStrike because I was standing up for people too afraid to speak up.

If you have any #EmberJS jobs where you're interested in moving to Glint / gjs/gts (Basically Polaris before it's out), lemme know
They're reasoning: I was now considered an "insider threat"

For a security company this a serious business, however their evidence for coming to this conclusion was the following:
In April of 2022, I recommended to co-workers, per IT recommendation to me over slack, to move their code to a folder outside their HOME directory so that the backup software had less to do. As with JS projects, there are tons of tiny files and this stresses backup software.
The code is already backed up in bitbucket, so this is in compliance with the "everything must be backed up and restorable" policy.
Second, over the past week the company released a "Return to Office Policy" which many remote employees were furious with.
The policy is phrased in a way that made returning to the office seem mandatory - people associate mandatory with possibility for punishment upon violation
Yesterday, there was a Q&A with leadership where they explained that the policy is actually optional, but they won't change the phrasing.

Lots of people were more mad after the Q&A than before.
In slack, in the #waterheater channel, lots of folks were letting off steam to help cope with the new policy.

I had encouraged folks to do the inverse of the policy, since that's what leadership *means*, even though it's not what they *wrote*.
There was also someone who said something about Malicious Compliance, and, me, being a person of the internet, and familiar with the fun subreddit: reddit.com/r/MaliciousCom…
said, "Malicious Compliance is the best Compliance".
lots of things were said in #waterheater over the past week, but that's the main thing they cherry-picked.

These 3 things are the reasons they used to make me not a problem anymore.
I was not given a chance to defend myself, or explain context

Nor was leadership willing to admit that the policy is worth updating the phrasing of

If they had just updated the policy's mandatory phrasing - be more encouraging, and welcoming, all of this would have been avoided
So now, more people will be afraid to speak up.

People who voiced concerns to me over the past week have already started updating their resumes.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with NullVoxPopuli 🇺🇦

NullVoxPopuli 🇺🇦 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @nullvoxpopuli

Jul 30, 2022
Using a one-line function, here is an example of how you prevent "loading flashing" when you refresh or load new data.

Play with it here : tinyurl.com/2p8kjte8

#JavaScript #EmberJS #REPL #StarWars
tinyurl preview: preview.tinyurl.com/2p8kjte8

direct link isn't possible on twitter due to how twitter gives up on parsing my URL 🙃
Here is the one liner:

let previous;
const keepLatest = (data) => previous = data || previous; Image
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(