Why I Started 'Getting Cracked'

How do you stand out while building a deeper engineering knowledge base?A look into the shift in mindset that led to Getting Cracked, and where this journey is heading.

Logged in - personal, software engineering on Tuesday, 4 August 2026.

Reading, inquisitiveness, curiosity, the desire to know and understand have always been my driving force. But lately, as #buildInPublic trends on X and AI tools make it easier than ever to gloss over concepts, I wanted to take a step back and build something with real intention -- choosing a depth-first approach to learning before pursuing breadth.

#Why Getting Cracked?

Deep understanding coupled with action.

Everything else is commentary.

In tech's current landscape, dominated by quick tutorials, AI-generated boilerplate, and surface-level updates, it is easy to mistake shipping fast for understanding deeply.

Getting cracked is my container for breaking limitations, exposing assumptions, revealing gaps in my understanding, refining knowledge, overcoming fears, and improving 1% daily until tools become an extension of the engineer and not a replacement.

This blog is where I'll document that process.

Here, you'll find articles about:

Backend Engineering
Linux
System Design
Mathematics
Cloud Infrastructure
Books I am reading
Projects I am building
Mistakes along the way and those before
Lessons learnt

Some posts will be technical deep dives, while others will simply capture my thoughts during the journey.

I am not writing because I already know everything. I am writing because learning in public forces me to think more clearly, research more thoroughly, and explain concepts in a way that others and my future self can understand.

For articles that perhaps deserve a more thought-out process or if I misunderstood something, each section has commentary options attached.

If you're also on the path to becoming a better engineer, I hope you'll find something useful here.

Depth first, breadth later. Welcome to Getting Cracked.