All the cool kids seem to use GraphQL rather than REST, today. GraphQL allows us to create a schema on top of which a client can define queries that the server answers. The client has full control over which data it will receive.

This new article gives a short intro to GraphQL and shows how to build a GraphQL server with Spring Boot. It also gives a quick comparison between REST and GraphQL

I recently listened to Tim Ferriss interviewing Jerry Seinfeld - the comedy icon. It's interesting how much of what a comedian is doing can be transported to working as a knowledge worker in the software industry :).

One thing that Jerry Seinfeld said was that when he's writing jokes, he doesn't share them with anyone until at least 24 hours later:

"Never talk to anyone about what you wrote that day, that day. You have to wait 24 hours to ever say anything to anyone about what you did, because you never want to take away that wonderful, happy feeling that you did that very difficult thing that you tried to do, that you accomplished it, you wrote."

It's not that other peoples' feedback is not important - it is important for writing jokes as a comedian and for writing code as a software developer. 

But right after you created something, you're still too emotionally attached to it to accept feedback. It's much easier to re-write text or code after sleeping over it for a night.

The next time you write some text or code, take some time to enjoy the feeling of having created something before accepting other people's feedback (or your own feedback, for that matter).