･
Reviews 12
･
Average rating 4.9
I'm leaving a review because I completed it. I actually completed it about a week ago, but I'm writing it down during lunch, so I'm not sure if it'll be helpful. 【Reason for taking the course】 Personally, I decided to take the course after seeing the preview of [Preparing to easily create working software.]. 【Impressions about the course】 Rather than feeling like I was creating a backend framework, I felt like it was a course about gaining insight into issues faced during development. The topics of each section were interesting, but since the lecture time was short compared to the topics, it was more like suggesting directions rather than pursuing depth. 【Other】 The source code kept piling up, but since the packages below biz and below fw were the same project, and test codes and logic codes were continuously added together, the project file felt increasingly complicated. This may just be my personal feeling. I wonder how it would have been if the course had been developed by dividing each function of fw into modules and writing biz by referencing the modules.
Hello. This is Zero. Among the lecture management functions of Inflearn, there is a student management screen. There, you can check the progress of each student's lecture. Unlike others, Mr. Eui-Jong showed a steady progress, and it was helpful as a lecturer. Thank you so much for your hard work. Regarding the direction, One of the things I kept worrying about when I planned the lecture was that if I talked too much, I would get off topic, and if I implemented it in depth, the code would become difficult. To overcome that, I organized the lecture from the perspective of a beginner developer who understands the problems that occur in actual work and turns them into functions of the framework. Of course, the functions created in the lecture are lacking, and as Mr. Eui-Jong said, it was also intended to end with just suggesting the direction. This is not a framework that you learn and use, but a framework that you improve because it is inconvenient, and I hope that it will broaden your horizons. The final version of the framework is located below. https://github.com/zeroshift01/zeroshift01/tree/master/inflearn08 You will see that the framework that was just a direction has changed to a level that can be used in practice. Let me talk about the second package management standard. It goes without saying, but in practice, the framework resources and the business resources are used separately. However, from the perspective of explanation, there is an advantage in not separating the resources, so we did not separate the biz and fw resources. When looking at the resources based on Eclipse, it seems that it will be easy to distinguish the resources if you look at it in a hierarchical structure. To answer the third question about the test code, since a package is a directory information that can modularize a function from a cohesion perspective, we managed the resources with the idea that it would be effective to place the test code that checks the defects of that function in the same location. Of course, the end of the file is made so that it can be known that it is a test code, like Emp001_test.java, and with such a rule, in practice, the test code is managed so that it is not transferred to the operating environment. In addition, if it is located in the same package, it is also good for testing the default method. ^^ Thank you for your review.
