Top 3: graphql is a trap, IBM's asshole test and a guide to zero downtime migrations

Hello my friends.

Here's what I picked this week, enjoy!

1. GraphQL is a trap + GraphQL is a Trap?​

TL;DR: Thread about the disadvantages of GraphQL and a response to the author from a GraphQL enthusiast from Netflix.

Funny thing, half the commenters on the tweet praise GraphQL and half dislike it. Here are three things I learned from this battle:

• GraphQL is a complexity to the project. Any complexity must be justified, the efficiency it brings must be greater than the efficiency it takes away.
• There is no need to use GraphQL if you don’t have the problems it was designed to solve.
• The flexibility of getting data with GraphQL is an advantage that comes at the price of performance.

2. Changing Tires at 100mph: A Guide to Zero Downtime Migrations​

TL;DR: A guide to database migration without down time.

The steps are as follows:

1. Create the new empty table
2. Write to both old and new table
3. Copy data (in chunks) from old to new
4. Validate consistency
5. Switch reads to new table
6. Stop writes to the old table
7. Cleanup old table

3. Intercom’s 9 fundamentals of great interaction design​

TL;DR: 9 principals of great design in Intercom.

1. Present the same object in a familiar way everywhere
2. Establish hierarchy in your interface
3. Create visual rhythm and balance
4. Use commonly accepted patterns and interactions
5. Use progressive disclosure
6. Be clear and concise
7. Consider responsiveness and speed
8. Guide users to what they should do next
9. Be mindful of accessibility

This tldr is useless without graphical examples of these principles, which you can find in the article.

And in the end, IBM's asshole test.

That's all for this week, take care and have a great one!

– Nick

If you're enjoying the newsletter, share it with a friend or two. Here's one quick way you can do it in 5 seconds:

​Share with Twitter, WhatsApp, Facebook, LinkedIn or copy & paste this link: https://nickbull.me/top-3​