First Principles

A first principle is a basic assumption that cannot be deduced any further. Over two thousand years ago, Aristotle defined a first principle as “the first basis from which a thing is known.” First principles thinking is a fancy way of saying “think like a scientist.” Scientists don't assume anything. 

- James Clear.

This is a new series of blogs where I cover a topic in detail. Although I'll be adding some mundane information for the sake of completion, I'll keep in mind to not add information which can easily by availed by a mere "Google Search". This will provide the reader with a holistic understanding of the topic while providing additional resources for some of its parts.

But there's a practical limit to which a certain topic can be reduced for the scope of this blog. Some assumptions will always be there about the education of the reader and basic know-how of Computer Science is expected. So then why do I call this series "First Principles"! It's because while covering these topics I'll cover answers to basic questions, as to why a certain thing is the way it is, what are the alternatives and various other trade-offs. The coverage will be broken down to a certain limit with few assumptions like I said before.

Upcoming posts:

• It's about time
• AWS SQS Best practices
  
• Maven dependency resolution
• JVM DNS catching
• Cassandra performance using idempotent calls
• Cassandra Write batch
• Randomness + Pseudo randomness
• Hash Functions
• Low level DB structure & its difference with interface (C* thrift VS CQL)
• Temporary Files in Linux
• Flavors of GC memory errors
• MySQL Antipatterns