I would like to express my overwhelming gratitude to Alan for creating this course and to my friend who recommended this bootcamp. I am a non-major who has been lucky enough to make a living as an iOS developer through a government-funded academy. The industry I entered with just a short 6-month government-funded education course was brutal. I was busy copying and pasting without even having time to understand the code day by day. As the years passed and I gained experience, would I really be able to call myself a developer? Wouldn't I just be a "coder" and not a developer? I couldn't stand it and tried all kinds of bootcamps and even much more expensive mentoring than this course. But none of that is necessary. (Just kidding. Exaggerating. The bootcamps and mentoring I took before were also very helpful to me.) Alan is the best. This course is that crazy. At this price and this quality, it's like Alan's course is cheaper than tires! It's really that good. If you've studied a little bit, you've probably heard a lot about how classes are allocated to the heap and the heap is slow, and how structures are allocated to the stack and are faster than the heap. I've also memorized this content through many educational courses. But I was just memorizing it, and even though I took expensive, high-priced mentoring, I couldn't say I understood it... If someone asked me why, I couldn't answer. In this lecture, Alan explains why the heap is slow and the stack is fast, and why Swift is a fast language as its name suggests, in an easy-to-understand way with pictures. If you are worried that it will be difficult to understand because you lack the basics, I would like to tell you not to worry. He explains it over and over again and keeps talking, so you can't help but understand. (It's just like hitting your head. Now Alan's memory structure diagram won't go away from my head.) Before I took the class, I didn't understand the memory structure... In fact, code data heap stack. You can find millions of search results just by searching Google, so you can find out what it is right away. But I didn't understand them properly, so I always had this thought. 'So what the hell is going on? My code goes up to the code area, but it's also allocated to the data area, heap, and stack areas. Does it go up here and there? What the hell is that?' Alan's explanation of the memory structure shows how much effort he put into making it as easy to understand as possible. What each memory area is responsible for and how the code I wrote works in each memory area. It sinks in with pictures. In fact, even if you don't know this, if you're just starting out like me, you can make an app, and these days there's chat gpt to help you develop, so it shouldn't be too difficult. If it just works, that is. But when you start thinking about more efficient code... performance optimization, you'll definitely hit a limit. This course provides a basic foundation for breaking through that limit and growing. In other words, I can confidently say that it will be a huge help. If you think this amount is expensive right now, just work hard for that amount. Then this course will pay you back with a salary increase that is more than twice the current tuition.