Let me state my opinion first.
First of all, regarding "in-class" and "out-of-class", it is true that some required courses may not be used in a lifetime for IT engineers or scientists (such as atomic physics), but these required courses are counted as personal Grades, they may not affect your soft engineering level, but they will affect your next platform, just like Ju Zhenliang abandoned the college entrance examination and came to a general school, if the university abandoned the required courses, then if you further study, the next The platform will most likely not be good. Even if you plan to get direct employment with your undergraduate degree, you should at least not fail the course. As for "legally skipping classes", this requires you to skip classes and achieve very good grades purely by self-study. If you are hovering on the edge of passing, or only have 70 or 80 points, just go to class honestly.
Second, about learning methods and mentality. Software engineering is an engineering discipline. Engineering discipline is impossible to learn without practice. Therefore, it is necessary to learn theory in practice and learn as you go. Of course, this kind of "learning while using" is not learning when the project is officially rushing, which is tantamount to reading anatomy books on the operating table. Moderately mentions a mentality: the goal is to learn, but you want to take on paid engineering. I think this kind of mentality is completely unacceptable. If a project provides compensation, it must require high-quality, directly commercialized content. Can a code written by a beginner meet this requirement? Obviously not possible. This is an eye-catching one.
Then I came to a place that I don't quite agree with. The senior mentioned that he "likes to communicate with people", but from his experience and words, he is not good at communicating with people. Because this senior has been in touch with IT very early, he started nibbling on professional books on C++ and Java when we were still struggling with the Chinese and mathematics exam papers, and because of this, when I read it, his words were full of comments about the level of his former classmates. Dissatisfaction and arrogance about one's own level, as if those who do not cooperate well with oneself violate authority .
Including the thoughts he mentioned in the middle of feeling that he was "not worth it" and "very tired" - "making others to be what you expect", "punishing yourself with other people's mistakes", I don't know if I paid attention, these thoughts The premise of "I must be right", I don't think if you are not arrogant, you will not have such an idea.
So I also don't think it's surprising that his project failed. Looking at what he did for the project, it was based on the idea of "I want this project to look like this", and after doing it, he found that "what others expect this project to look like" is different from his own expectations? The reason for this is that there was no unified team goal and interest orientation from the very beginning, and I only felt that others thought the same as myself. In such a situation, there is no room to blame the classmates around. Of course, if the scheduled tasks are not completed, this is slack, but there is no excuse for it.
Cooperation is different from harmony. The starting point of cooperation is the overlapping of interests, rather than the interests of some people serving the interests of some people. Perhaps the author expects a superior-subordinate relationship rather than an environment of free cooperation and communication. I think the results of the author's work are different from his expectations. It is not only the problem of unclear communication, but also the way of thinking is partly responsible for this result.