Dan Schafer

[Dan Schafer @dlschafer]

Feedback/PRs welcome, especially if there are optimizations that I missed: there should be good built-in test coverage and benchmarking if folks want to play around with it.

[Dan Schafer @dlschafer]

I've been hooked on Queens puzzles for the last few months, and as a side project built a solver for them: https://t.co/yFbeeUqclv.

[Dan Schafer @dlschafer]

It does basic image recognition to read games in from various sites, especially from https://t.co/QB74CZpbGW (the original as far as I know). It also picks up in-progress games as well, which is useful for getting a hint on hard puzzles.

[Cult.Repo @CultRepo]

We are now Cult.Repo. The original creators behind the iconic Open Source documentaries (@vuejs, @reactjs, @GraphQL) are back together! Honeypot is now called @CultRepo and is independently-owned.

We are on a mission to document the complete history of every major open source language ever created.

With 250K subscribers and over 15M views, we're building on our foundation as creators of the acclaimed Open Source Origin Story documentary format.

Coming in 2025: @ThePSF, @vite_js documentaries and much more.

Our independence is core to our mission. We believe the human stories behind open source deserve authentic, in-depth storytelling.

Our new model is powered directly by:
- Community support from viewers
- Sponsorships from organizations that champion open source

This transition represents our commitment to independent, meaningful tech storytelling that honours the collaborative spirit of open source itself.

[Dan Schafer @dlschafer]

The source code is at https://t.co/qrYhcFfgrm. It's hosted on @vercel with a @nextjs / @reactjs front-end, and a @dagster data pipeline.

[Dan Schafer @dlschafer]

I'm ready to share a side project I've been working on: https://t.co/twSCGZSY2O. It uses historical data to see how typical soccer champions perform in each match; then uses that to generate strength of schedule–aware tables, and to show the difficulty of upcoming matches.

[Dan Schafer @dlschafer]

Just saw the follow-up at https://t.co/3HYFbizhPO — such tooling helps with high-traffic use cases, but not external ones.

You *can* use GraphQL for high-traffic external APIs (as GitHub demonstrates)... but "most of you shouldn't be using it" is spot on advice for that use case

[David Cramer @zeeg]

While these problems might not exist for you, that doesn't mean they couldn't. Internal GQL might be fine. Low user traffic GQL might be fine. The issue is when you have high traffic APIs and/or external APIs. Untrusted user input is what's going to cause outages.

[Dan Schafer @dlschafer]

This tweet by @zeeg points out a valid obstacle towards the adoption of GraphQL — but a surmountable one, in my view. There are two major things needed to overcome this concern. (continued below)

[David Cramer @zeeg]

GraphQL's adoption issue in a nutshell:

"It's great that my frontend can decide what data the API returns!"

What an experienced engineer sees:

"It's terrifying that end users can change the performance characteristics of our service on the fly"

[Dan Schafer @dlschafer]

But this tradeoff is right in a lot of use cases... and when it is, the benefits of GraphQL can be massive, which is why so many folks are using it and happy with it.
(and if someone wanted to build/has built that tooling I mentioned, they'd make a lot of GraphQL users happy)

[Dan Schafer @dlschafer]

@SheilKapadia @BenjaminSolak Love the pod. Thursday 10 question — including 2022, Jason Kelce now has five first-team All-Pro selections.
At what point does he become a likely/sure-thing Hall of Famer? Is he already? Every other Center with 4 AP1s is in! #RingerPhilly