[コードファクトリー] [中級] Flutter 本物の実戦！

Thank you for the great Flutter lecture~ I wrote a long post because there were many things I regretted while listening to the lecture. Summary - It is a great lecture for making apps with Flutter, but is it bad for understanding Flutter? ------------------------------------------------------ Overall course review Judging from the speed at which you wrote Flutter code, it seems that you have done a lot of related work, but compared to that, I felt that your overall project design ability, experience, and IT knowledge were somewhat lacking. Of course, I think it is enough for job seekers or students to listen to, but for developers with some experience, there were many parts where the explanation of concepts was wrong or why the project was structured like this. At first, I wrote a post by asking questions while listening to the lecture, but I thought that if I kept writing, the lecture would not progress, so I just took notes separately and skipped the lecture. Here is what I wrote for now. - Insufficient theoretical explanation of tokens or sessions in the authentication process explanation -> I left this in the question - Insufficient detailed explanation in terms of taking the project structure. I wanted to hear a little bit about what patterns are used in Flutter, but they created a repository and a provider without explanation~ - The response format of the provided server API does not match. It is easier to develop if the response model is the same whether paging is used or not, but if there is paging, it is wrapped once in data and sent down, and if there is not, it is just sent down as is, so it is too inconvenient because it cannot be managed commonly in the client,, - When creating a Dio interceptor, the explanation is like 'It's just a rule~' and you can follow it, and the explanation on the network side is insufficient overall - There are parts where the explanation is skipped here and there, such as "If you know oop,,", and there are parts that talk about it even though it is not a concept about oop - The naming does not match overall. The same image URL field is used as imgUrl, imageUrl, and I don't know why user_model is used as camel as userModel, but username is not used as userName - The more the lecture goes on, the more the same words are repeated. It seems to be due to video editing, but there are parts where the same thing is repeated.. It's uncomfortable to watch - After the gorouter chapter, it suddenly goes to UerMeRepository. In the previous lecture, UserModel was not created, but it was created. It seems like the lecture was missed ... Because of the above contents, rather than listening to the lecture, I watched the lecture by stopping the lecture at the beginning of the lecture and implementing and comparing it myself when I thought, "What should I do?" In fact, the reference codes I saw on github or stackoverflow were much cleaner and had a better structure. (+ I also bought and read the book that he wrote, but I feel like he has never experienced a project at a large company.) I usually don't write reviews while listening to the lecture, but I ended up writing this because he said this so many times during the lecture. "This code can be written differently because it's different for each project, team, and person." "Can't this be done like this?" If you say that, I have nothing to say." You say a lot of defensive things about tackles, but from the perspective of the listener, it sounds negative. If you had various project experience, you could explain various examples and say that there are various methods, but it seems like you are saying this because you can't. It would have been better if you didn't mention it. And you say a lot, "This is a paid lecture, so I will tell you everything," but the explanation is too poor. I think it took more time to look into the internal code while listening to the lecture. In my opinion, if it's an 'intermediate' level, you expect to be explained how the code works internally, but it was a lecture where you just used what was there without knowing how it worked inside. I hope that in future lectures, you add examples of various projects and explanations of internal logic.

This is a lecture that is almost perfect. Although the title of the lecture is [Intermediate], it is not an exaggeration to say [Intermediate-Advanced] because the lecture content is solid. Since most of the content can be applied directly to actual work, it is a lecture that is perfect for current Flutter developers as well as those preparing for employment. Honestly, it is really cheap to learn this quality lecture at this price. Not only me, who has been developing for more than 15 years, but also anyone who has worked in the field for 1-2 years will probably know what I mean. If someone who explains this in detail were to work at a company, I would sincerely and childishly advise them, “Even if you give all your salary to that person, come learn for just one year.” There is no faster growth than learning from a good mentor. In order to really grow as a developer, you definitely need the attitude and passion of a learner, but it would be even better if a veteran who has already walked that path could guide you to the best course. Flutter has been a hot topic for several years, but there is still a shortage of intermediate to advanced personnel. I think that if you listen to this lecture repeatedly and master everything yourself, you will be able to work happily under really good conditions. Your skills will improve to the point where you can quickly create not only company projects but also the apps you want to create. I bought almost every book sold in bookstores to study Flutter, and I also came across a lot of online clone coding. I also took lectures on other platforms that really explained Flutter step by step. But this is the most useful. It is the most practical and cost-effective. I sincerely advise you to learn this first and fill in the gaps. I would like to express my sincere gratitude to the instructor, and I look forward to the [advanced] lecture coming out in the future.

I started learning Flutter by taking a Flutter course on another site. I won’t mention the site or the instructor, but when I think about it now, I can only say that the instructor’s level was too low. I had a lot of complaints while taking that course. It felt like I was just practicing typing, and the answers to my questions were not very satisfying. Even though I took all the courses, all I gained was my typing skills. Nothing more or less. After that, I Googled on my own and applied for a 1:1 tutoring class on Soom* to try a personal project. If I look at the code now, it’s really… incredibly crude and messy to the point where I wonder why it was written like that. In the end, I just spent money and didn’t learn properly. Since my personal project wasn’t progressing well, I started looking for other courses, and that’s when I found Code Factory’s course. At that time, I was debating between Code Factory's lecture and another lecture (since there were two lectures by Copac, I was a little worried... hahaha). I can't help but think that it was really lucky that I ended up taking Copac's lecture. Whether it was the 4-hour Dart lecture or the beginner's lecture, I had a hard time because of the build speed or setting errors while using Windows.. Other than that, I never felt so frustrated because of the lecture. Now I'm using a MacBook, so it's really refreshing hahaha I took the beginner's lecture once, and honestly, there were many parts that I didn't understand, so I asked questions several times and googled a lot to figure out how to proceed. In the meantime, I also changed my personal project and am working on it again. I realized that my skills had really improved after taking the beginner's lecture right after I took the intermediate lecture. When I first started taking the beginner's course, I was busy following along, comparing, and understanding the code, but when I saw that I could follow along just by listening to the instructor without looking at the screen in the beginning of the intermediate course, in the basic parts of creating the UI or screen, I realized that the beginner's course was really effective! (Come to think of it, I had no idea about Future/Stream Builder, but now I'm using it in my personal project without any problems.) There's still a lot of content left, and I haven't even started the difficult parts, but I'm confident that if I trust the instructor and follow the intermediate course, I'll level up before I know it. It's the beginning of the intermediate course, but I'll follow along well without falling behind and become a developer like Copac's disciple who can create clean codes on my own!

The lecture I've been waiting for has finally come out. I've been running the lecture since it came out, and the content is so rich that it's worth the wait. I'm an Android developer working in the field, and since the end of this year, I've had to do several small projects in a row with Flutter, so I've been taking Dart and Flutter beginner lectures and working on personal projects. There were some parts that I lacked on my own, so I took other Flutter intermediate lectures, but there were so many parts that were disappointing in the lecture composition and level. Fortunately, the intermediate lecture was uploaded right before I started the projects, so I'm listening to it quickly. The content composition is really good and the lecture preparation is perfect. I asked on the bulletin board when the intermediate lecture would be uploaded, and you said it would take time to prepare more thoroughly, but I can understand that you've prepared really well. I'm writing this without any order because I'm grateful, but if anyone is thinking about taking the course, just take it right away!!

I started listening from the beginner level and am listening to the intermediate level. When I suddenly started using Flutter, I was at a loss, but since you covered everything from the basics, I am so grateful and I don't know how to express my gratitude.!! I will also wait for the advanced lectures ><!