Assessing Yourself Honestly

Before applying anywhere, it helps to know honestly where you actually stand. Not to discourage yourself, and not to inflate your confidence either — just an accurate picture, because acting on a wrong one wastes effort in the wrong direction.

Underestimating yourself means not applying to things you were actually ready for, or apologising for gaps that are completely normal at this stage. Overestimating yourself means walking into interviews unprepared for basic questions, or applying only to roles well beyond your current level and collecting rejections that a slightly different target would have avoided.

Both come from the same root cause: not having checked honestly beforehand.

1. Can you build something small from scratch, with no tutorial open? Not follow one — build something on your own once you've learned the pieces. If not yet, this is the actual priority, ahead of applying anywhere.
2. Can you explain your own project out loud, clearly, in under two minutes? If you struggle to explain it, an interviewer will notice, whatever the code looks like.
3. Do you know why your code works, or did you copy a working pattern without fully following it? Both get something built; only the first survives being asked "why did you do it this way".
4. Can you read an error message and have a reasonable first guess at the cause? This is the single most practical junior skill, and cheap to build with practice.
5. Have you ever had your code reviewed or criticised, and how did you react? If the honest answer is "badly", that is worth working on before an interview, not after a bad one.

Self-assessment has a limit — everyone is a poor judge of their own blind spots by definition. A second opinion helps: ask a teacher, a further-along peer, or anyone technical to look at one project and be genuinely honest, not encouraging. Encouraging feedback feels better and teaches you less.

Comparing yourself to senior developers, to impressive online portfolios built over years, or to the most advanced person in your batch produces discouragement with no useful information attached. The only comparison worth making is between where you are now and where you were a month ago, and between what you can currently do and what a junior role in this landscape actually requires — covered in the previous lesson.