Join 📚 Kevin's Highlights

A batch of the best highlights from what Kevin's read, .

If you’re mathematically inclined, then you could use the [pigeonhole principle](https://en.wikipedia.org/wiki/Pigeonhole_principle) to describe hash collisions more formally: > Given *m* items and *n* containers, > if *m* > *n*, > then there’s at least one container > with more than one item. In this context, items are a potentially infinite number of values that you feed into the hash function, while containers are their hash values assigned from a finite pool.

Build a Hash Table in Python With TDD

Bartosz Zaczyński

![The solution journey for analytics on Azure starts with learning and assigning roles. Next, choose a storage solution and an Azure BI or AI technology for the workload.](https://learn.microsoft.com/en-us/azure/architecture/solution-ideas/media/analytics-get-started-diagram.svg)

Analytics architecture design - Azure Architecture Center

big data architecture

Software companies aren't made of code, much like bakeries aren't made of bread. Software companies are made of *processes that produce and maintain code*. Software is a by-product of these processes. It's not even the *final* product — it's a means to an end. The final product is a solution to a business problem.

The Machine That Makes the Thing Is More Valuable Than the Thing

François Chollet

...catch up on these, and many more highlights