[Class Report] Systems Development (3rd Year), Week 55
~ Final Reflection and the Next Step: Putting Your “Core as an Engineer” into Words ~
Week 55 was the wrap-up session after the final presentation.
While looking back on three years of learning,
it became a class devoted to organizing what each student had gained and what they want to develop next.
The theme was:
Understand not just “what you accomplished,” but “how you grew.”
■ Teacher’s Introduction: “Growth only becomes lasting when you can put it into words.”
Mr. Tanaka: “You have all definitely grown.
But if you cannot explain that growth for yourselves, it will not lead to what comes next.
Today, let’s put your own changes into words.”
■ Today’s Goals
- Look back on three years of learning
- Clarify your strengths and weaknesses
- Organize how your understanding of systems development has changed
- Connect this to future learning and career paths
■ Exercise 1: A Three-Year Reflection Activity
First, each student individually wrote down how they had changed since first year.
Reflection points
- Technical skills (programming and design)
- Ways of thinking (problem decomposition and design thinking)
- Team development
- How they approach errors and failure
Student A: “At first, I only thought, ‘As long as it works, it’s fine.’ Now I think about whether it works safely.”
■ Exercise 2: Identifying Your Strengths
Next, students put their strengths into words.
Examples
- The ability to organize design
- The ability to find bugs
- The ability to make UI easier to understand
- The ability to bring a team together
- The ability to identify causes from logs
Student B: “What I thought was just normal for me turned out to be one of my strengths.”
■ Exercise 3: Weaknesses and Future Challenges
At the same time, students also organized the points they want to improve going forward.
Examples
- Spending too much time on design
- Not explaining UI clearly enough
- Not anticipating enough error cases
- Slow implementation speed
Teacher: “Weaknesses are simply points that can be improved.”
■ Exercise 4: How Their Understanding of Systems Development Has Changed
The class then shared how their perception had changed over the three years.
First year
- Development meant writing code
Second year
- Design is important
Third year
- Development includes external integration, AI, safety, and responsibility
Student C: “I realized that development is ten times broader than just writing code.”
■ Exercise 5: An Action Plan for the Future
Finally, students organized what they want to learn next.
What they wrote down
- Fields they are interested in
- Web development
- AI
- Infrastructure
- Security
- What they want to learn from here on
- The next system they want to build
Student D: “Next, I want to build something bigger.”
■ Whole-Class Sharing
Several students presented their thoughts.
- “I started to enjoy thinking about design.”
- “I am no longer afraid of errors.”
- “I gained the perspective to use AI properly.”
- “I learned both the difficulty and the fun of team development.”
■ The Teacher’s Final Message
“In these three years, you have gained:
- The ability to build
- The ability to think
- The ability to communicate
From here on,
new technologies will keep appearing.
But,
if you understand how to think, you can learn anything.
Believe in your growth, and move on to the next stage.”
■ Closing the Class
At the end, each student gave a short final comment, and the class came to a close.
The classroom was filled with a mix of accomplishment, a little sadness,
and anticipation for what comes next.
■ Final Summary
Week 55 was a class about organizing three years of learning in each student’s own words.
The students realized that they had not simply gained knowledge,
but had developed the ability to keep thinking.
This class series reaches a stopping point here,
but the students’ learning will continue from this point onward.