What I learned from ruined interview
I've had a very high self-esteem regarding my skills. I had my first difficult technical interview, and wow, they really surprised me. They made me realize that...
(By the way, this was a good experience for me because I treated this 'defeat' not as a failure, but as an opportunity for growth. Because of that, I didn't start belittling myself or beating myself up. On the contrary, it sparked a desire in me to improve.)
- If you don't review things, you'll forget them. (I've forgotten my algorithms, so I need to revive my LeetCode practice. If I'm doing at least 10 commits a day, one medium LeetCode problem should be the minimum.)
- I'm very superficial on a lot of topics and don't go deep at all. I was content with the tip of the iceberg, and my ego thinking I knew everything and could do anything was preventing me from actually learning. (LangGraph and RAG, for example. I'm now realizing how necessary they are, so I need to dive deep into them.)
Just writing projects and launching startups won't make you a good programmer. A good programmer thinks about the technical details and solves problems. You first need to develop the skill of solving small problems, and then you can go build companies.
You need to be in competition with yourself. You have to grow much more than you have been.
advice to students always be competing