A job search can stretch on for months, and time spent purely applying and interviewing, with no ongoing building, quietly erodes the actual skills those applications are supposed to demonstrate. This eventually shows up in interviews as rustiness, which then compounds the discouragement of the search itself.
Coding is a skill that fades with disuse the same way any practical skill does. A student mid-course, coding daily, is measurably sharper in the moment than the same person three months into a job search where the only coding happening is occasional interview prep. Applying alone is not practice.
Job hunting and skill-building work better run in parallel, deliberately, rather than treating the search as a full-time activity that pushes everything else out entirely:
Keep building something the entire time you're searching, even if it's small. Beyond keeping skills sharp, it gives you something new and current to talk about in the next interview, which matters more than it sounds — "what have you built recently" is a very common question, and "nothing, I've just been applying" is a genuinely weak answer to it.
Spending literally all available time on applications, with zero time left for building or review, leaves you rustier with each passing week of searching — the opposite of what the time was supposed to produce. Spending all your time comfortably building instead, while quietly avoiding the discomfort of actually applying and facing rejection, produces skill without forward progress toward the actual goal. Both feel productive in the moment. Neither, alone, moves the search forward.
A loose, unscheduled search is far easier to let quietly slide — a day becomes a week becomes a month with the discouragement doing the work of avoidance. A simple, fixed weekly structure removes a lot of the daily decision-making about what to do next, which is exactly the kind of decision that's hardest to make well while discouraged.