whit537

Got it! :)

True! It is not disruptive just because it sucks. In fact, it is not disruptive at all yet—what has it disrupted? Nothing. :^) What I said, though, is that I'm not _discouraged_ at its limited utility at this point in the game. It's to be expected. Everything, as you say, sucks at first.

In terms of Innovators Dilemma: Robb Oat is not useful to existing "customers" of software engineers (product managers, engineering managers, lead engineers). But because of its drastically lower cost and higher speed, it _may_ open up new markets that barely exist right now. If successful in these new, smaller markets, it may eventually move upmarket and displace existing "technology" (i.e., us) once it can compete on productivity. That's the point at which it will have proven itself to be disruptive.

The next step for Robb Oat, if it's to go anywhere, is to find the smaller, newer market where it can be useful. TBD

Ready for the CFP! :^)

Maybe skip Leviticus and come back to it later?

That's definitely how it has played out, yes. The big one for me was:

https://github.com/robb-oat/server/issues/7

I coded it up myself and then was like "wait I should be dogfooding this" so I did and Robb Oat spit out basically what I had just written. That was the aha moment for me.

Also I've been reading Innovator's Dilemma and basically all disruptive technology sucks at first so I haven't been too discouraged about it.

Yeah I thought about using "developer" instead of "engineer." I'm in the US and we don't have a professional organization that owns the term. Meh.

Am I allowed to say developer? Is that what I'm supposed to say?

You're making me blush, aliqot. Thanks for the kind words!

Hit me up chad@zetaweb.com and let's get you a new heart coin. I still have the punch. :D

Thanks for trying it out! :^)

As you can see it struggles with whitespace.

Yeah it blew me away when DALL-E spit that out on the first try. Both the name and the logo are so perfect, and DALL-E cut the time down from hours if not days or weeks to seconds to get there. At the same time I did iterate on it, I made it two words, Robb Oat, instead of one, Robboat, to make it more relatable and easier to figure out how to pronounce. :^)

Runner up was Sobbart Root. :D

Thanks, Ali, and congrats on the launch! :^)

Possible but not actual. Pallets is the project in question here, and Armin is only barely involved anymore, specifically he doesn't see any of the money they raise.

Yes I confirmed with him ahead of time that he doesn't see any money sent to the Pallets project.

Which SDK? I'm hearing internally that we do have extra context still.

> two types of social media strategies: open strategies, in which firms provided public responses to at least 75% of complaints, and closed strategies, in which at least 75% of the time, firms responded with just a single message directing the complainant to a private forum.

Consider a middle ground: direct the complainant to GitHub (or some other public off-Twitter channel). I wanna think this is the best strategy, but there's probably not enough companies doing this at scale to meaningfully compare.

The question occurs to me because I was talking with someone from Iran recently and learned about Internet shutdowns there. Why can't it happen here?

https://www.netfreedompioneers.org/iranian-elections-2021-ho...

Gotta be creative to work for https://en.wikipedia.org/wiki/MSCHF (according to his LinkedIn).

Anecdote: Troy Polamalu's account (840k followers) has been hacked and scamming people for going on two weeks and his media team can't get Twitter to even respond let alone resolve. :(

https://www.reddit.com/r/steelers/comments/s6zx3c/polamalus_... https://www.reddit.com/r/steelers/comments/s67xoi/troy_polam... https://twitter.com/tpolamalu (scammer took it private)

Next time let's go with "We Just Gave 11¢ Less Than $155,000 to Open Source Maintainers." :smirk:

Sorry. :^(

We'll keep trying to do better!

That's awesome! Good luck! :D

We're thinking through how to follow up on this post with additional signal-boosting throughout the year, point taken about exposure value to small projects. We'll keep that in mind!

Thanks for Nim and keep up the great work! :^)

Not meant to be snide, no. It's something we thought about when allocating our budget: how are projects going to perceive this? Is giving $100 or $500 worse than giving nothing at all? So my question was also asked in earnest! :D

Back to your original question, then:

> Does $500 reflect the value and developer time savings you've received from the project over the years?

I guess the binary answer is yes, though I quite agree with you that it's difficult to gauge value in open source a priori.

Thanks for the kind words about Sentry ... and thanks for making Rollup! :)

I'm genuinely curious what they donate, maybe it's already that much? More? Less? No idea. Also, at their scale cost of FTEs dedicated to upstream open source becomes a significant consideration. How many kernel hackers do they employ?

I'd love to see other companies express their open source donations in terms we can compare across companies. Yes, in absolute terms $155k (rounding up ;) is not that much, but Sentry is not that big. We have ~75 engineers. How much do other companies with 750 or 7,500 engineers donate to open source, per engineer?

> you left unpaid volunteers to deal with an angry customer.

> You didn't even get a product manager or customer success manager to intervene.

For the record, these are false statements. zeeg did get me, a paid employee, to step in and deal with the situation, which I did:

https://github.com/getsentry/sentry-symfony/issues/436#issue...

It's true that we do have a lot of great volunteers working on our SDKs. We value them and appreciate them, and if/when we let them down we do our best to make it right.

Sorry for letting you down as a customer. We'll keep trying to do better.

Right, I was intentionally reframing the question. As a company we wanted to arrive at a budget through a global view and then allocate from there. Rather than look at 100+ projects individually and build up from "How much value did we get from this one? Or that one? And that one?" ... we wanted to reason about a fair amount overall. Is that bad?

What's a good (practical, repeatable, reasonable) way to determine fairness?

We have no Nim usage in the company. One of our engineers nominated it as something they find personally interesting, and we wanted to give at least a little bit to every project that our employees nominated.

By contrast, we use Rust quite heavily, including our core ingest component: https://github.com/getsentry/relay.

That's why there's such a discrepancy in this case.

:face_with_rolling_eyes:

Imagine my surprise seeing https://news.ycombinator.com/item?id=28693731 surface serendipitously three weeks ago. That post from four years ago during Gratipay's final days is linked in today's announcement. :D

<3