A weekly review that keeps prep honest

xingqpa24 days ago

Preparation has a way of feeling productive while quietly going nowhere. You read a chapter, watch an explanation, skim three solutions, and at the end of the week you have a pleasant sense of effort and very little you could reproduce under pressure.

The thing that fixed this for me was a short review at the end of every week. Twenty minutes, same three columns, no tooling.

The first column is what I can now do without help. The bar is deliberately high: I have to be able to start from an empty file and get to a working answer while explaining the reasoning. If I need to peek, it does not go in this column. Most weeks this column is shorter than it feels like it should be, and that gap is the entire point of the exercise.

The second column is what I touched but cannot reproduce. This is where most of the week’s reading ends up. It is not wasted, but calling it learned is how you end up surprised in an interview. Items here either get scheduled for real practice or get dropped on purpose.

The third column is what got in the way. Interruptions, a topic that turned out to need a prerequisite I did not have, an evening lost to a tool that did not work. Writing this down stopped me from making the same plan again the following week and expecting a different result.

Two small rules keep it from decaying. I write it at a fixed time, because a review that waits for a good moment never happens. And I keep the previous week visible while writing the new one, which makes drift obvious: when the same item sits in the middle column for three weeks running, the honest move is to either start it properly or admit it is not a priority right now.

What surprised me was how much this changed planning rather than studying. Knowing that the first column has to be filled with things I can actually do makes me choose fewer topics and go deeper on them, which is what I would have claimed to be doing anyway.

Comments0

Recommended Reads

Post

Transitioning from DBA to Data Science

Hello Everyone, I hope you're doing well. My name is Saikiran Panthagani , and I have been working as a Database Administrator (DBA) . Over the last six mon

Post

Seeking Guidance

Hi everyone, I’m a MERN Stack Developer with 4+ years of experience, but lately, I’ve been struggling to get interview calls despite being confident in my devel

Post

Seeking guidance regarding JOB application.

Anyone with experience this post is in regards to learn a the way one's who are getting interview calls and getting hired for a person like me who is being

Post

Github account suspension

My github account got suspended how to recover Iam a student I had many repositories and I also did contributions I was preparing for GSOC since july and contri

Post

Packet Capture Tool Comparison: Charles, Fiddler, TraceEagle, Wireshark, and Proxyman

Packet capture is one of the most common techniques developers use in daily debugging. There are many tools on the market, but each has a distinct positioning a