devjaeyoon8462's honest review, A Portfolio Guide from a CTO Who Has Reviewed 10,000 Applicants course

This is a portfolio course that frontend developers can gain a lot from as well! The course introduction includes the phrase, “It is structured from the perspective and background of a backend developer,” so some of you may be wondering whether to take it as frontend developers. I had similar concerns at first, but after taking the course myself, I came to think that it is a sufficiently useful course for frontend developers as well. To sum it up in one sentence, it was: “A course that makes you look back and reconsider whether you are properly including in your actual portfolio the things you thought you already knew!” While taking the course, there were some points that made me think, “Isn’t this a little obvious?” However, when I looked back at my own portfolio, I realized that knowing something and expressing it well in practice are entirely different matters. There were many cases where I had overlooked things in my actual portfolio that I had taken for granted, and after taking the course, I was able to review my portfolio again and think about what to keep and what to remove. What I particularly liked was that, rather than simply presenting the “correct” answer in the form of “You should include these things in your portfolio,” the course explained what people reviewing portfolios look at and how they make their judgments. As a result, after taking the course, I found myself thinking not only from the perspective of someone writing a portfolio, but also about how the person viewing my portfolio might perceive it. I also liked that the course reflects current trends, including how to address and incorporate AI into a portfolio—something that is difficult to leave out of recent developer recruitment. Rather than simply listing trendy technologies, it gave me an opportunity to think about how to present them meaningfully in a portfolio. Personally, I also appreciated being able to think about the difference between a résumé and a portfolio. Looking at job postings, a résumé is often required while a portfolio may be optional. This led me to consider when a portfolio is necessary, what role it should play if it is needed, and what it should show differently from a résumé. For that reason, I personally think there would be even greater synergy in taking this course together with the résumé course! It allows you to think about how to divide up and communicate your content between your résumé and portfolio. Thank you sincerely for creating such a great course!