Counting Crow

Everything is Obvious by Duncan J. Watts

What if my previous conversations are all frivolous and now I am asking a serious question? Am I doomed?

I’ve been a subscriber of @wired.com for a while but it was due to their tech articles. But off late, they are turning out be a great news org. Kudos!

I got 4/6. I am not sure if I am breaking any etiquette of wordle but I’m guessing your 2/6 is synonymous with house?

Name a non-LOTR character who could resist the One Ring.

And here I thought something was wrong with my phone today 🤦🏽‍♂️

Trying to see if this works in bluesky

@skyview.social unroll

Indians never forgot that golden rule!

The best part is the you can keep running mental simulations even after you finish the book. What if Gandalf never came back? What is the impact on the story then? Why didn’t the eagles just fly Frodo and Sam to Mt. Doom in the first place? Again, something great software architects always do.

My opinion is that immersing in great literature which has many characters and plots augments a software developer’s skills significantly. Btw, I think the book should be big like LOTR, or The Mahabharatha or the Iliad. Because you have to keep so much of it in your head.

LOTR had many plot lines going on at the same time - Frodo’s journey, Aragorn’s path, Gandalf’s adventures. However, all of them converging to the same goal. How would multiple teams in a company working on different parts of the systems converge to common outcomes?

When Frodo felt that Bilbo should have killed Gollum, he (and we as readers) didn’t know the critical role Gollum would play in the story. Sometimes the smallest things influence the system in unexpected ways.

You thought you had a great partner who you can rely on? Boom, Saruman just imprisoned you. What contingencies have you put in place in case your trusted API partner turns malicious or gets hacked?

Let’s take the LOTR example. Lots of characters, locations, moments - big and small, multiple plot lines, choices made by these characters. I see a lot of parallels between understanding complex software architectures and reading epic stories.