目录

I. Preface: Review of the Alpha Phase and Purpose of Summary

II. Sorting Out Core Problems in the Alpha Phase (Classified by the Whole Process of "Learning by Doing")

(I) Problems Related to Learning New Skills

(II) Problems in Project Practice Advancement

(III) Problems Related to Team Collaboration

III. Root Cause of Problems: Cognitive Deviation of the Software Engineering Concept of "Learning by Doing"

IV. Specific Impacts Brought by Problems

V. Preparatory Improvement Ideas (Laying the Groundwork for the Beta Phase)

VI. Summary

---

I. Preface: Review of the Alpha Phase and Purpose of Summary

1. Phase Overview: The core goal of the Alpha Phase is to build the basic architecture of a current affairs news website, realize the classified display of regular news (such as politics, economy, society, entertainment, etc.), news detail viewing, and the prototype development of the Fuzhou University Column (including the entrance for campus news display); the team consists of 12 members in total, and the overall progress rhythm is early demand sorting, mid-term technical selection and basic development, and late-stage function integration, presenting an overall "learning by doing" progress state;

2. Summary Background: Clarify the core state of the team during the Alpha Phase — adopting "learning by doing" as the main mode, involving the learning and practice of new contents such as the front-end Vue framework, back-end SpringBoot framework, MySQL database design, and Git version control. At the same time, it is necessary to specifically overcome technical difficulties related to project-specific needs such as crawling and updating current affairs news data and differentiated display of content in the Fuzhou University Column;

3. Summary Purpose: Through systematic review, sort out the core problems encountered during the phase, analyze the root causes of the problems (focusing on the cognitive deviation of the concept of "learning by doing"), and provide a basis for avoiding similar problems, optimizing team collaboration and development processes in the Beta Phase.

II. Sorting Out Core Problems in the Alpha Phase (Classified by the Whole Process of "Learning by Doing")

Explanation: Classified according to the logic of "learning new skills - project practice - team collaboration", each type of problem needs to supplement "specific scenarios + scope of impact + duration" to avoid vague descriptions.

(I) Problems Related to Learning New Skills

1. Ambiguous Learning Direction: When learning the front-end Vue framework, the core needs of the news website such as "list display, pagination loading, and detail jump" and the Fuzhou University Column such as "characteristic style adaptation" were not considered to screen knowledge points. Instead, all contents such as component encapsulation and state management were learned blindly, resulting in low learning efficiency in the early stage. When developing the news list pagination function and the column's characteristic style, it was still necessary to check materials again, delaying the development progress by about 3 days;

2. Disconnection Between Learning and Practice: After learning Git version control, the scenario of "multi-person collaborative development of different news modules (regular news/Fuzhou University Column)" was not used for practical branch management, and only basic submission commands were simply mastered. In actual collaboration, members responsible for the development of the Fuzhou University Column did not create feature branches based on the development branch, but directly modified the code in the main development branch, leading to code conflicts with the development of the regular news module. It took 2 days to resolve the conflicts later;

3. Insufficient Problem-Solving Ability: When developing the current affairs news data crawling function, problems such as data acquisition failure caused by anti-crawling mechanisms were encountered. When developing the Fuzhou University Column, problems such as the adaptation of campus news source interfaces were encountered. In both cases, over-reliance on search engines to try solutions blindly, and no idea of "locating problems - analyzing anti-crawling/interface characteristics - summarizing adaptation methods" was formed. Similar data acquisition problems occurred repeatedly 3 times, accumulating 4 days of time consumption;

(II) Problems in Project Practice Advancement

1. Insufficient Demand Decomposition: The decomposition of core functions in the early stage was too general. The "Fuzhou University Column" was not refined into specific small tasks such as campus news classification (such as school league committee notices, academic activities, campus life), differentiated design of column styles, and isolated storage of campus news and regular news data. As a result, the function of "sorting column news in reverse chronological order of release time" was missing during the development process, and conflicts between the column style and the regular news module occurred. It took 3 days to supplement and modify later;

2. Inadequate Technical Selection: The team's technical reserve was not fully evaluated, and a third-party news crawling framework was blindly selected. Later in the development, it was found that the framework had extremely poor adaptability to niche campus news sources and high learning costs, making it impossible to efficiently obtain Fuzhou University campus news data. It was necessary to replace it with a basic crawler scheme for re-development, leading to an overall delay in the development progress by 5 days;

3. Lack of Testing Awareness: Only focusing on whether the function "can run", no testing process was planned in advance, and no special tests were conducted on the core of the news website such as "data loading timeliness", "multi-browser compatibility" and the Fuzhou University Column such as "content display accuracy". Later, it was found that the column style was disordered in some browsers, the update delay of current affairs news data exceeded 2 hours, and there was a problem of duplicate display of Fuzhou University campus news. It took 4 days to rework and rectify;

(III) Problems Related to Team Collaboration

1. Unclear Division of Labor: The core responsibilities and docking boundaries of each member were not clarified, and no exclusive developers were assigned for the "regular news module" and "Fuzhou University Column module". Two people developed the regular news list function at the same time, while the Fuzhou University Column data adaptation function was unattended, resulting in unbalanced function development and delayed progress of the column module;

2. Low Communication Efficiency: Daily stand-up meetings were a formality, only simply reporting "development completed" without accurately synchronizing progress bottlenecks and problems; when cross-members docked the function of "jumping from the regular news homepage to the Fuzhou University Column entrance", the jump interface parameters and jump logic were not clearly defined in advance, leading to no response when clicking the column entrance after docking. It took 1.5 days to investigate and fix;

3. Chaotic Version Control: No unified Git submission specifications were formulated, and submission information was mostly vague expressions such as "modify code" and "improve function"; during multi-person collaborative development, members responsible for the Fuzhou University Column did not synchronize the code of the main development branch in a timely manner, leading to conflicts between the column style code developed by them and the latest code of the regular news module. Moreover, due to the vague submission records, it was difficult to locate the root cause of the conflict, and it took 2.5 days to resolve;

III. Root Cause of Problems: Cognitive Deviation of the Software Engineering Concept of "Learning by Doing"

Core Conclusion: The core root cause of the problems in the Alpha Phase is that the team did not truly understand the essence of "learning by doing" in software engineering, simply equating it with "learning when encountering problems, exploring while developing", and lacking pre-planning and systematic thinking. The specific cognitive deviations are reflected in the following 3 points:

1. Confusing "Learning by Doing" with "Blind Exploration": Mistakenly understanding "learning by doing" as no need for pre-learning and planning, directly entering the development link, leading to chaotic learning directions and wrong technical selection; in actual software engineering, "learning by doing" needs to clarify learning priorities based on project requirements, complete basic skill reserves in advance, and then deepen understanding through practice;

2. Ignoring the Core of "Summary and Iteration" in "Learning by Doing": Only focusing on the process of "learning" and "doing", failing to summarize and precipitate learning results and practical problems in a timely manner, leading to the repeated occurrence of similar problems; the real "learning by doing" is a closed loop of "learning - practice - summary - optimization", and summary is the key to improving learning efficiency and avoiding problems;

3. Lack of Team Collaboration Awareness in "Learning by Doing": Regarding "learning by doing" as an individual behavior, failing to form a team-level knowledge sharing and mutual assistance mechanism; software engineering is a team collaboration project, and "learning by doing" needs to simultaneously promote team knowledge synchronization and division of labor optimization to avoid individual learning barriers affecting the overall progress.

IV. Specific Impacts Brought by Problems

1. Progress Impact: Due to problems such as low technical learning efficiency, code conflict rework, function docking failure, and crawler framework replacement, the completion rate of core functions in the Alpha Phase was only 75%, among which the completion rate of the regular news module was 85%, and the completion rate of the Fuzhou University Column module was only 60%, which was 8 days behind the expected plan overall;

2. Quality Impact: Due to the lack of testing and chaotic development process, there were 8 obvious bugs in the completed functions, including disordered style of the Fuzhou University Column, delayed update of news data, duplicate display of column news, invalid jump interface, etc., which directly affected the user browsing experience. If launched directly, it may lead to user loss;

3. Impact on Team State: For example: frequent rework and delayed progress led to anxiety among some members; unclear division of labor and poor communication led to tension in the team collaboration atmosphere and decreased cohesion;

4. Subsequent Risks: If the unresolved problems in the Alpha Phase, such as crawler technology adaptation issues, lack of version control specifications, and unclear docking mechanism between the Fuzhou University Column and the main module, continue to the Beta Phase, it will affect the development efficiency of core needs such as real-time update of news data and improvement of column functions, and may lead to chaos in team collaboration again;

V. Preparatory Improvement Ideas (Laying the Groundwork for the Beta Phase)

Explanation: Briefly list the core improvement directions for the above problems. The specific and detailed improvement plan will be elaborated in the blog "Preparation Ensures Success".

1. Optimize the Learning Model: Based on the needs of the Beta Phase such as "improving the function of the Fuzhou University Column, realizing real-time update of news data, and fixing compatibility issues", clarify the core learning contents as "efficient crawler adaptation technology, front-end responsive layout optimization, and data synchronization mechanism", formulate a learning process of "preliminary basic learning + practical deepening + summary and precipitation", and carry out special technical seminars for the specific needs of the Fuzhou University Column;

2. Standardize the Project Process: Refine demand decomposition, classify and decompose the needs of the Beta Phase into specific executable tasks according to "optimization of regular news modules" and "improvement of Fuzhou University Column"; clarify technical selection criteria, giving priority to technical schemes suitable for campus news data acquisition; establish a sound testing process, focusing on special tests for news timeliness, column display accuracy, and multi-terminal compatibility; formulate unified Git version control specifications;

3. Improve Collaboration Efficiency: Clarify the team division of labor, assign exclusive development and testing personnel for the regular news module and the Fuzhou University Column module, and clearly define the docking boundaries; optimize the daily stand-up meeting process, requiring key reports on "progress bottlenecks and collaborative matters needed"; establish a team knowledge sharing document, summarizing special contents such as crawler adaptation schemes and column development problem solutions to promote knowledge synchronization;

VI. Summary

Briefly review the core problems such as vague technical learning, insufficient demand decomposition, and poor team collaboration that occurred during the development of the current affairs news website and the construction of the Fuzhou University Column in the Alpha Phase, clarify that the root cause of the problems is the cognitive deviation of the concept of "learning by doing", equating it with blind exploration. Emphasize that "learning by doing" is not unplanned trial and error, but a systematic process that needs to clarify learning priorities and strengthen team collaboration in combination with project needs (especially characteristic modules such as the Fuzhou University Column). Clarify the value of this summary — providing a clear basis for improving column functions, optimizing the efficiency of news data acquisition, and standardizing the development process in the Beta Phase. In the future, the improvement ideas will be strictly implemented to ensure the smooth progress of the project and improve product quality.

Kind Reminder: After publishing, check the validity of the blog link to ensure it has been added to the Beta Phase High-Quality Blog Collection; if any missing problems are found later, they can be supplemented and modified before the deadline.