How I am Tackling A Book Called Cracking The Coding Interview?
Today I started my journey of reading a book called, “Cracking The Coding Interview by Author”. I got this book to help me understand algorithms, coding, and design questions that are commonly asked in developer interviews. My goal is to become a Full-Stack Ruby on Rails Developer for a company. Since my background differs from a traditional software developer’s, my focus is on reaching an industry-standard skill level.
So far, I have experience in front-end design and development. Now, my focus is on mastering back-end fundamentals, algorithms, system design, and database architecture to become a well-rounded Full-Stack Ruby on Rails Developer.
How Am I Tackling This Daunting Programming Book?
As someone still discovering my learning style, self-studying has become increasingly challenging as topics grow more complex and time-consuming. But despite the hurdles, I haven’t given up.
This might seem excessive to some, but I’ve started writing simple project briefs for everything - from music to software projects. These documents help me clarify goals, maintain focus, and prevent scope creep over time. For someone who thrives on structure, this practice has been game-changing.
My daily routine will consist of me:
- Reading 1-2 chapters of Cracking the Coding Interview with morning coffee.
- Write a title and concise summary of key concepts.
- Reflect on how to apply them to prepare myself for technical interviews.
This isn’t magic - just consistent work. The summaries test my understanding, improve retention, and directly prepare me for technical interviews.
I’ll put in the work, measure what matters, and course-correct when needed.
If you’ve walked this path before, I’m all ears for practical advice.