I spent the day building my project instead of preparing for tomorrow's interview — useful work, wrong time.
Day 16 was a little complicated.
I spent a significant part of the day building my project instead of preparing for the interview scheduled for tomorrow. And while I don't necessarily regret it, I know I made a trade-off.
For the first round, I feel reasonably confident about my preparation, so I decided to give the project more time today. I've always believed that implementation-based learning is more valuable than simply reading concepts, and working on the project gave me an opportunity to actually apply what I'm learning.
But there's a problem.
Building something can feel extremely productive.
You are writing code, solving problems, seeing features come together, and getting a visible outcome at the end of the day. But when an interview is tomorrow and there is still a lot left in the preparation plan, that productivity can actually become a distraction.
That's something I caught myself doing today.
The project is important to me, but right now the immediate priority is the job search. Building the project doesn't guarantee that I'm becoming better prepared for the interview sitting in front of me.
So while I wasn't particularly happy with today's balance, I'm also not going to overthink it. There are still several days left in the week, and I should be able to recover some of the lost ground.
The next few days — Wednesday through Sunday — will be about getting back on track with the goals I set at the beginning of the week.
Tomorrow, though, the priority is simple.
Interview.
I'll give it my best, see where I stand, and use whatever happens as another piece of feedback for the journey.
Day 16 wasn't my most productive day.
But maybe recognizing why I wasn't productive is itself part of the process.
Sometimes the hardest distraction isn't doing nothing. It's doing something useful at the wrong time.
Comments