This lecture doesn't just provide simple methods or answers; it offers opportunities to think for yourself using cases you might actually encounter in practice. I was satisfied with the quality of the lecture.

As a developer working in a similar domain, this was a time for me to rethink how to design and view systems. Thank you.

It was great to see how to utilize AI as a fellow developer, going beyond just using it as an answer-generating machine.

I think it contains good content in a short and simple way~

Following the previous course, I am taking this one as well. I am a junior developer currently in my 4th year. When I was a rookie, I knew nothing, but around my 2nd year, I started having some thoughts. It might be embarrassing to admit, but there were many times when I felt frustrated by the indiscriminately verbose source code or "unclean" code written by senior developers. Even more embarrassingly, I once harbored the arrogance to think that I could do a better job than those seniors if I were assigned the same tasks. I realized later that those senior developers understood the business much better than I did, communicated effectively with colleagues, and were skilled at translating business needs into code. Being "clean" wasn't actually the most important thing. I eventually realized that even if a developer uses two for-loops or avoids using streams, it is better code if it effectively incorporates the business logic. Although I was hired as a developer to get work done, honestly, I wasn't the type of talent the company truly needed or wanted at the time. Rather than focusing on performing the job well, I strongly believed that a "good" developer was someone who strictly adhered to principles like writing clean, well-defined components and following development rules without exception. As I entered my 3rd and 4th years, my perspective gradually began to change as I observed people in the company who weren't developers—people who didn't write code themselves but provided direction for projects and explained their understanding to others. I started to realize that I am here primarily to do the job well, and my role is simply to achieve that through development. It was around that time that I first came across Gemini's lectures. I was surprised because the message of the lecture focused exactly on what is necessary to be a developer who works well. (I wondered if you had read my mind...) In Korea, there is a strong tendency across all fields to struggle with asking questions. Personally, I have always been interested in Jewish education, so I’ve looked into related books and videos. I intend to strive toward becoming a developer who works well and asks good questions. I am certain that the ability to ask questions and the process of solving problems through inquiry to make the best choices in rapidly changing situations will become even more important in the future. (The lectures often mention asking questions and encourage self-thinking, which resonated with me deeply.) Following this course, I look forward to all your future releases.

Thank you for creating a course that gives those without practical experience a taste of how things work in the real world!

I feel this is a really great lecture. There's so much to learn from the source code itself even without the lecture. Personally, although you didn't include it in the lecture, I hope there will be follow-up lectures on inventory and membership~! As you mentioned in the lecture, inventory alone has so many different aspects, so I'm hoping for it because I feel I could learn more things that are different from what I already know~!

Previously, I was only focused on referencing features that others had already built, but now I've learned that when given requirements, it's important to deeply consider how I can solve them myself. Thank you for the great lecture.

The lecture was really excellent. At first, I hesitated thinking it might be targeted at prospective or junior developers, but personally I gained a lot from it. I also felt regret that if this lecture had come out just a few years earlier, it would have been a great help early in my career. More than any other lecture I've taken, it contained the real concerns and questions that you actually face in practice. True to the theme of "the power of thinking," I could vividly experience how to view problems, what criteria to use for judgment, and where trade-offs occur. I was particularly impressed by the flow that constantly made me think—from requirements analysis to various options and the context for making those judgments. Even with years of experience, there were still many points I struggle with, so I resonated deeply with it, and it made me think that I should now actually convert options into code and evaluate them, rather than just turning them over in my head. It naturally brought back the concerns I had when I first started developing, and I felt that many of those concerns were well compressed into this lecture. As time has passed, I've also come to consider more context and deeper concerns, and this lecture felt like it condensed and organized those thoughts. Whenever Jaemin's thoughts were layered on top of the thought-provoking questions throughout the lecture, following that flow felt like my own thinking patterns were being organized. The strengths I felt from Jaemin's YouTube were delivered even more deeply in the lecture with example code, which was much better. If there's an advanced follow-up lecture, I definitely want to take it.

I wanted to learn the code and thought process of someone who does it well, and this course seems to meet those expectations to some extent!