If the situation were just "high pressure" that would be fine, but if you make mistakes (or even if you don't) people get upset. Working in this kind of environment makes it really hard for me to square the circle of encouraging people to work in Open Source.

4
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Aaron Patterson ✅

I think maybe my best advice is: definitely get involved in open source, just make sure either nobody uses your software or you quit ASAP 😆

4
9mo
Patrick Davey

@tenderlove thank you for all the thankless tasks that you do.

0
9mo
loading… HAC (he/him)

@tenderlove thank you for writing this! And THANK YOU for years (if not decades) of work you’ve been doing!
For what is worthy: my immediate reaction when bundler-audit showed one of the CVE did not have a fix on the 6.1 series was: “Holy, I need to upgrade this app to Rails 7 sooner rather than later”!!!
I think folks like me need to be more vocal about how thankful I am for the work you do! 🙏

0
9mo
Max

@tenderlove I feel a sense of pride for having someone like you active in the community each time CVE comes out, because it’s not that we have more security issues, it’s that we have more people looking for them and you’re more diligent patching it. I know it’s not much but “look what you have to do to break this, and it’s still patched” is an awesome feeling each time.

It’s the nature of all preventative work. Everything bad is prevented, so looks like nothing’s done.

0
9mo
Replies