Twitter | Search | |
Lee Byron
I make things , previously . React, GraphQL, Immutable.js, Web, Mobile, JavaScript, Nonsense.
5,425
Tweets
514
Following
29,894
Followers
Tweets
Lee Byron Jul 17
Replying to @kuizinas
Re: your original question. "Graceful error handling" absolutely. Imagine fetching news feed, hitting a snag on one particular story, and having a default behavior of rendering nothing. That's a bad UX. Instead the better default is it renders all stories except the failed one.
Reply Retweet Like
Lee Byron Jul 17
Replying to @kuizinas
IMHO Early GraphQL got the error management story backwards, and clients lack tools to manage errors in-query (try/catch in your GraphQL?). Without that the reasonable default is nullable and the edge case is non-null.
Reply Retweet Like
Lee Byron Jul 17
Replying to @kuizinas
Historical context is at FB, lacking permission to see a thing should be observably the same as that thing not existing. At FB nearly every object in the data model had some permissioning and potential to render null (or bubble up a null). A list with a null entry was common.
Reply Retweet Like
Lee Byron retweeted
Tanmai Gopal Apr 28
Join us! Also, also, please welcome surprise guest the one and only Lee Byron
Reply Retweet Like
Lee Byron Apr 22
I often think about a job interview lunch I had with a VP where I pronounced paradigm “pair-uh-dig-em.”
Reply Retweet Like
Lee Byron Apr 20
Replying to @rtfeldman
That’s very good
Reply Retweet Like
Lee Byron Apr 20
Replying to @ProfessorLevy
Mine was Chumbawamba
Reply Retweet Like
Lee Byron Apr 20
Remember Ska?
Reply Retweet Like
Lee Byron Apr 10
Replying to @mehulmpt @rubicon49bc
DNS Privacy up on it, I just hope a community member is holding it. If not I’ll see what I can do about a brokering service to contact the owners, but in the past I’ve found this to be a very very slow process
Reply Retweet Like
Lee Byron Apr 10
Who owns - and would you like to donate it to the GraphiQL project?
Reply Retweet Like
Lee Byron retweeted
GraphiQL Apr 3
Good news today! We are joining forces with to adopt our beloved graphql-playground. Read more to learn what happens next and how you can get involved!
Reply Retweet Like
Lee Byron Apr 1
The GraphQL Foundation turns one. We’ve accomplished so much as a community. Here’s a look over the past year and what’s to come.
Reply Retweet Like
Lee Byron Mar 25
Replying to @DJFreshUK
This feels mean spirited, Daniel
Reply Retweet Like
Lee Byron Mar 24
Do you use and want to contribute to Immutable.js? I’m calling for maintainers. If interested DM me your github and email, I’ll set up a maintainers call.
Reply Retweet Like
Lee Byron Mar 23
I’m grateful for my team at , who despite being holed up in their homes for weeks and facing a scary market and world have brought creativity, energy, craft and hard work every day.
Reply Retweet Like
Lee Byron Mar 23
Replying to @awelfle
Because of this tweet or did you find it afterwards?
Reply Retweet Like
Lee Byron Mar 20
Replying to @leeb
Today I realized I haven’t commuted or sat in traffic for two weeks. That time has been spent with my family instead, and I’m grateful for that.
Reply Retweet Like
Lee Byron Mar 20
Replying to @leeb
I’d like to re-engage and try to bring positivity. I’m going to try to take a moment every day or so to share something I’m grateful for, or a positive thought.
Reply Retweet Like
Lee Byron Mar 20
I haven’t been very active on Twitter in the last few months. Between Trump, election, industry, and now pandemic drama my feed has gotten increasingly frenetic and stressful. I’ve found my mood and state of mind to be fragile, so I’ve stayed away.
Reply Retweet Like
Lee Byron Mar 13
Replying to @sseraphini
Not sure, depends a lot on your implementation. You could add trace logging that adds batch IDs and creation times to try to see why they’re split up
Reply Retweet Like