I've spent my whole career working with neurodivergent people in tech.

Here's to the people who thrive with interrupts, who work best when juggling four different things, are pretty great incident responders, and can code while talking on slack.

Here's to the people who need four uninterupted hours to get anything done, but what they get done is fantastic, and they have the in depth knowledge to explain nuances you didn't even know were there, making them the folk who find the long term remediations after incidents.

Here's to the people who take great joy in picking the lint out of a codebase because it's fun, who refactor for the challenge, who see bad process and ache to get changes in to reduce the friction.

Here's to the people who seem to know everyone, who reach across teams to tap experts who don't get the recognition others do, and work best when working WITH.

Y'all are amazing

The crates.io team is currently proposing to change the policy governing crates.io!

They are looking for feedback wrt to the changes.

They are clarifying the rules regarding what is appropriate or not.

IMO the biggest change is that they are looking to add rules that allows them to remove 'inactive squatted' crates and re-assign them to others.

If you might be impacted by this, be sure to check it out and read about it.

https://github.com/rust-lang/rfcs/pull/3463

#rust

I added soft-blocking checks to my publishing flow by writing my own GitHub App that runs inside of an Action. Before I could submit my reports to each pull request, I had to authenticate with GitHub. Yet, when I got a key from GitHub, I could not use it! JavaScript's cryptography expects a different key format. I share how to convert RSA keys and later sign (gasp) a JWT to acquire an API key. The rest was easy from there. Every detail of how this works is written inside!

Also, I share how I publish to NPM in a GitHub Action.

#cryptography #github

https://cendyne.dev/posts/2023-07-24-custom-github-actions-check-runs-github-applications-and-npm.html