You write "The communication paths between engineers increase exponentially as the team grows in size.", but in fact the total number of communication paths between n nodes is equal to n * (n-1) / 2, which is not an exponential growth, but an polynomial growth (quadratic to be exact), i.e. O(n^2).

You have given a good overview on the type of technology stack used, it would have been much more helpful if you could have included about databases, and messaging queue being used.

Hi,

You write "The communication paths between engineers increase exponentially as the team grows in size.", but in fact the total number of communication paths between n nodes is equal to n * (n-1) / 2, which is not an exponential growth, but an polynomial growth (quadratic to be exact), i.e. O(n^2).

thanks for the great feedback. I will update the post.

Nothing escapes the Math Police 🙌🏿

I learned so much reading this. Also thank you for the bibliography/works cited.

While diagonal Scaling is an interesting infrastructure scaling, the use of load testing and the small team size were eye-opening

This allows me to delve deeper into some of mentioned concepts

thanks for the feedback

Great read, Neo! In short don’t reinvent the wheel and avoid complexity as long as possible.

I bet Jan Koum is glad he got rejected by Facebook in 2008! Thanks for the article.

edited May 19yeah the moral of the story is life gifts are not obvious because they are wrapped in rejection letters.

Great post! As someone who is building his own product, articles like these are a treat.

edited Dec 17, 2023Hi,

Thanks for the wonderful newsletter.

You have given a good overview on the type of technology stack used, it would have been much more helpful if you could have included about databases, and messaging queue being used.

thanks for the feedback.

Thanks for explaining it with clarity while being concise.

A quick question, what software are you using for your diagrams? I like their sketch feel.

it's excalidraw.