There's a particular kind of silence in interview rooms. It comes right after you finish answering, when you can hear the interviewer's keyboard quietly registering your fate. That day, I heard it three times.
I was interviewing for a Senior Backend Engineer role. Most of the conversation flowed — system design, trade-offs, debugging stories, code on a shared whiteboard. But three topics caught me sideways. I answered to the best of my ability, but I knew. I'd walked into rooms before with the confident swagger of preparation, and this wasn't that. I left knowing the rejection email was already drafted somewhere in the future.
Here's the thing, though. I've spent enough time in this industry to know that the rejection itself wasn't the real problem. The rejection email would arrive and disappear into an archive folder. The three gaps in my knowledge would still be there next week, next month, next interview.
So I did what any growth-mindset engineer should do: I closed the laptop, accepted the loss, and went looking.
The Resource Hunt
The internet is generous with information and hostile with structure. After a few evenings of digging through Reddit threads, course catalogs, GitHub stars, and Twitter recommendations, I had my plan:
- Topic 1 — a single book, dense and authoritative, just over 600 pages.
- Topic 2 — a tighter book, about 100 pages, surgical in its focus.
- Topic 3 — one well-reviewed YouTube video and two long-form articles that complemented each other.
Four resources. Three topics. One goal. I felt good. I felt prepared. I made coffee, opened the first book, and got to work.
That feeling lasted about a week.
The Quiet Chaos of Self-Learning
The problem with self-learning is that nobody hands you a syllabus. Nobody breaks the 600-page book into Tuesday and Thursday chunks. Nobody tells you whether to watch the YouTube video before the article, or after, or whether to read the second article before circling back to chapter four of the first book.
So I did what most self-learners do. I jumped. A chapter here. A video there. An article when I got tired of the dense book. Some nights I'd close my laptop unsure whether I'd actually moved forward or just paddled in a circle.
Worse, the doubts started compounding. Did I really understand chapter three, or did I just read the words? Was that article supposed to come before or after the video? Am I still preparing for the next interview, or am I drifting?
The momentum I had on day one was gone. The plan was still there, technically. But the progress — the felt sense of getting closer — had evaporated.
A White Paper and a Pen
In a moment of mild frustration, I grabbed a sheet of white paper and a pen. I wrote down every resource. I broke each one into sections — chapters, video segments, article subsections. I drew checkboxes next to each. And I started checking them off.
It worked. Sort of.
The act of carving the resources into visible, finite pieces gave me something to push against. Each checkmark was a small dopamine hit. Each completed section was proof that the work was real.
But the paper itself became the next problem. Re-drawing it when I changed my plan was tedious. Estimating what was left meant squinting at the page and counting in my head. The energy of maintaining the system started competing with the energy of doing the learning. Real progress was hidden behind a layer of paper bureaucracy.
I'd built myself a tracking system that mostly tracked my tracking.
The Engineer's Instinct
There's a moment that comes to every engineer where you stop and ask the obvious question: why am I doing this by hand?
I'd been so focused on learning the three topics that I'd missed the meta-pattern. The problem in front of me wasn't a knowledge gap anymore. It was a tooling gap. I needed something that could:
- Hold all my resources in one place.
- Let me break them into trackable units without re-drawing anything.
- Show me real progress — not just checkboxes, but the shape of where I'd been and where I still had to go.
- Let me set goals and pace myself against them.
- Treat my learning the way I'd treat any other project worth shipping.
So I built it. I built Preplani.
Preplani is the curriculum I wish I'd had after that interview. You bring your own resources — books, videos, articles, courses, anything — and turn them into a structured plan you can actually follow. You define the goals. You set the pace. You see the progress. And when you adjust the plan (you will), the system adjusts with you.
It isn't a course platform. It isn't a content library. It's the layer in between — the structure that makes everything else stick.
Why This Matters for Self-Learners
The story I just told isn't unique. Every self-learner I've talked to has lived some version of it. The bootcamp graduate teaching themselves system design. The career-changer working through a stack of PDFs. The senior engineer preparing for a staff interview. The student picking up a new framework on weekends.
The resources exist. The motivation exists. What's almost always missing is a way to hold the whole thing together — a personal curriculum that respects your goals, your pace, and your own judgment about what you need to know.
Most learning tools assume someone else designed the path. Most productivity tools assume you already know what to do. Self-learners live in the gap between, and that gap is where good intentions quietly go to die.
Preplani is for that gap. It gives a growth mindset something to hold onto — a place to put the plan, the resources, the tasks, the milestones — so the energy you bring to learning actually compounds instead of evaporating between sessions.
The Loop
I didn't get the Senior Backend Engineer role. The rejection email arrived, exactly as expected, and I archived it. But the loop closed somewhere unexpected — I now own a product that exists because of that interview. The three topics I didn't know became the seeds of the thing I built.
If you're a self-learner with a growth mindset, I think you'll recognize yourself somewhere in this story. And I think you deserve a better white paper.
You can build your first plan at preplani.com.