Tobias Pfeiffer
@pragtob.bsky.social
1K followers 240 following 300 posts
Likes people. Teamplayer, Open Source Enthusiast, Software Developer, Benchmarker, TDDer, Speaker. Elixir, Ruby, JavaScript. Loves green.
Posts Media Videos Starter Packs
Hex all the way! Glad you got them, but also: funny post! 😁
I wanted to release a new benchee version with the compile warnings before its release and planned to do that this weekend... guess I was too slow!

It's already fixed on main, will see to a release asap.
Reposted by Tobias Pfeiffer
This. And all framed as “not taking sides” or “jumping to conclusions.” Most of the upset with RC was about lack of comms, kicking out people on GitHub, and platforming DHH, none of which have been sufficiently addressed.
Reposted by Tobias Pfeiffer
Ruby community: Look, we can be angry about what's happening, we can raise our complaints, but under no circumstances should anyone _ever_ harass someone's families, coworkers, or friends.

That is completely unacceptable, and wholly against the ethos of the language. We must do better.
Reposted by Tobias Pfeiffer
the reason I advocate for projects to have a code of conduct is because harassment is never okay. not only is harassment never okay, harassing families and coworkers is even worse. get out of here with that.
Ruby community: Look, we can be angry about what's happening, we can raise our complaints, but under no circumstances should anyone _ever_ harass someone's families, coworkers, or friends.

That is completely unacceptable, and wholly against the ethos of the language. We must do better.
If you wanna talk elixir I'm always around :) That said of course, there's not as many jobs as in the other languages you mentioned (although probably more than in Hanami I suppose)
Reposted by Tobias Pfeiffer
Another 🔥 package release from @maennchen.dev 😎
AshDiagram is a library for generating beautiful diagrams to visualize your #AshFramework applications. Generate Entity Relationship, Class, C4 Architecture, and Policy diagrams directly from your Ash resources and domains. 🚀
Reposted by Tobias Pfeiffer
It's incredible how this whole thing has cut to literally every important cultural and political question in OSS.

These are the big questions, the values you build communities around. We should be clear about the things we believe. We coasted on the status quo and differences are now clear.
Reposted by Tobias Pfeiffer
Me: DHH is saying some kinda racist stuff, and he’s outright bullying people in PRs.

Them: But look over here! André had a gap in his commit history! And he once got paid $150 / hour to do *open source*!!! Outrageous! 😲😲😲
Reposted by Tobias Pfeiffer
The way that certain people in this community attack André, while turning a blind eye to DHH’s (objectively far worse) behaviour. It’s fucking disgraceful.
I love that it's you and @rickrickenharp.bsky.social replying here. Your exchange made me go "wow what the fuck happened and how do I find it" (I managed).

All respect to Justin, that post was weird to me for how much ad hominem it was...
Didn't read bluesky for a weekend. Immediately completely out of date on what's currently going on.

Hot damn people. What a mess.

About a year ago I had "Community" down as probably the biggest factor in favor of Ruby - and a huge at that.

This all _significantly_ weakens that point.
Reposted by Tobias Pfeiffer
I went through Ruby Together's old Form 990s with the IRS:

1. Andre never reported more than $60k in compensation to himself in a year. Seems pretty reasonable to me.
2. Meals/travel/IT expenses are about $20k year, roughly ~6.6% of revenue, which to me is reasonable.
Thanks a lot for your work, writeup, response and perspective.
Reposted by Tobias Pfeiffer
"[you] discovered that people with no active affiliation or agreement in place had top level privileges to some of this critical infrastructure."

The people you removed about were actively paid for contractual on-call support through Ruby Central. Far from unaffiliated.
Reposted by Tobias Pfeiffer
I really appreciate your post @apiguy.dev. Thank you for posting your thoughts. I wish you had the info I had to make your decision.

Here's the core issue:

Before Sept 9, when a trusted maintainer broke our shared contract and added an RC non-maintainer, you had no ability to enact your vote.
Reposted by Tobias Pfeiffer
The Ruby community deserves to know who voted for this and what information they were acting on.

Ruby Central is actually very opaque. They don’t publish donations, they don’t publish votes, the community has no say who’s on the board. There is no accountability.
And... easily avoidable to boot.
I mean, if they had only taken away access from people who didn't do anything for 1 year+ and sucked at that communication then I'd tend to agree.

That's a far cry from what happened though.

Removing access from inactive maintainers is very different than the broad swing they took.