Jordan Eldredge

Jordan Eldredge

@capt.dev

Engineer on http://relay.dev at Meta | Made http://webamp.org | Hacking on GraphQL Server for TypeScript http://grats.capt.dev

441 followers449 following145 posts

Jordan Eldredge reposted

Jordan Eldredge reposted

There’s a lawsuit against WhatsApp making the rounds today, claiming that Meta has access to plaintext. I see nothing in there that’s compelling; the whole thing sounds like a fishing expedition.

Setting Chrome to mimic a 3G network it's even worse! 8 distinct layouts.

What the heck is going on with Spotify's embedded player that it flashes through no fewer than six different layouts as it loads?

What the heck is going on with Spotify's embedded player that it flashes through no fewer than six different layouts as it loads?

Remembering the time a few months ago where I asked Claude to write a Bach chorale using LilyPond and then do 10 iterations of critical feedback and improvements. It ended up with this hilarious monstrosity. The reviews it gave the final draft were quite impressive...

And its grades for the final version: * Voice Leading Evolution: Bach-level sophistication * Harmonic Sophistication: Transcendent melodic expression * Hierarchy of Priorities: Transcendent artistryd

Jordan Eldredge reposted

Happy New Year 🎉 New year, new resolutions: fewer null checks, clearer error handling, and getting nullability right in GraphQL. Let's see how far we get this year.

I updated grats.capt.dev internal snapshot tests to serialize using markdown and the result is so nice! Snapshot output now has syntax highlighting and nice readable headings showing what each bit of the output means.

Jordan Eldredge reposted

maybe not the best moment for it but i finally condensed my “why react server components” into a short blurb that does well on HN

Jordan Eldredge reposted

Ever wonder how GraphQL clients like Relay keep your app’s data perfectly in sync without extra network calls? 🤯 Meta’s Sabrina Wasserman breaks down the core engine behind modern GraphQL clients. Watch here 👇 www.youtube.com/watch?v=hz0...

youtube.comLocal Data Consistency With GraphQL - Sabrina Wasserman, MetaHave you ever wondered how GraphQL clients like Relay keep local data consistent across surfaces, ensuring that changes made within a session are seamlessly ...

Jordan Eldredge reposted

I think the npm client should probably follow pnpm in making post-install scripts be opt-in and recording that decision in package-lock, so if a package that was previously inert suddenly has a post-install script, it wouldn't execute. www.sonatype.com/blog/the-sec...

sonatype.comThe Second Coming of Shai-Hulud: Attackers Innovating on npmSha1-Hulud returns to npm with automated, self-replicating malware and pipeline persistence. Sonatype details the campaign and how to stay protected.

Jordan Eldredge reposted

I simply refuse to accept that police ever have to look like this. this is just pure cosplay. it should be illegal for cops to be dressed like soldiers going to war.

Jordan Eldredge reposted

Local reasoning. Zero over-fetching. Seamless pagination. Optimistic updates. Consistent UI. Tiny bundles. Built in lock-step with #GraphQL; Meta's Jordan Eldredge shares The Big Ideas in #Relay to enhance user experience and developer velocity. youtu.be/yInL1aPZjvI

youtube.comThe Big Ideas in Relay - Jordan Eldredge, MetaRelay, Meta’s advanced GraphQL client for React, has many innovative capabilities not available in other clients. We will explore these capabilities, what th...

Jordan Eldredge reposted

One of the huge perks of working at a software company is, when there's something about the product that bothers you personally, you can get your hands dirty and find out why it's basically impossible to get fixed

Jordan Eldredge reposted

GraphQL error handling sucks. There, I said it. Null checks everywhere, and ambiguity: error, or true null? We've all been there. In this talk, Benjie Gillam shows how to fix GraphQL's biggest mistake in 512 bytes. 👇 youtu.be/odwQUAkmW44

youtube.comFixing GraphQL's Biggest Mistake in 512 Bytes - Benjie Gillam, GraphileGraphQL error handling sucks. There, I said it.Ever hunted through the errors list to figure out if a null was legit or caused by an error? If you're like me...

There were only about 50 skins which were not already in our collection. Further confirmation that the museum's >101,000 skins represent the vast majority of all skins ever created.

I’ve been made aware of a 2013 “panic download” archive of downloads.nullsoft.com containing ~60k Winamp skins. Downloaded and hashing all the files to find any which are not already in the Winamp Skin Museum.

Jordan Eldredge reposted

Jordan Eldredge reposted

📣THREAD: It’s surprising to me that so many people were surprised to learn that Signal runs partly on AWS (something we can do because we use encryption to make sure no one but you–not AWS, not Signal, not anyone–can access your comms). It’s also concerning. 1/

Meredith Whittaker @meredithmeredith.bsky.social

PSA: we're aware that Signal is down for some people. This appears to be related to a major AWS outage. Stand by.

Jordan Eldredge reposted

Markdown+metadata is such a good format for blog posts. But deploy-to-publish feels heavyweight, and I often want to publish from my phone. Current setup: Author in Notion and pull from Notion API to Markdown in SQLite DB. Site renders from SQLite.

I also periodically materialize the Markdown in the DB to files in the repo so that I have a durable backup with course grained history in a fully open format. This is a hedge against wanting to drop Notion for something else (Obsidian?)

Works especially well with SQLite’s full text search. Been building a little search DSL for my site which compiles to SQLite’s FTS+structured search/sort conditions. github.com/captbaritone...

github.comjordaneldredge.com/packages/search-query-dsl at master · captbaritone/jordaneldredge.comMy personal website. Contribute to captbaritone/jordaneldredge.com development by creating an account on GitHub.

Markdown+metadata is such a good format for blog posts. But deploy-to-publish feels heavyweight, and I often want to publish from my phone. Current setup: Author in Notion and pull from Notion API to Markdown in SQLite DB. Site renders from SQLite.

Jordan Eldredge reposted