[!TIP] View the final deliverable: 📥 Download my M1 Professional Activity Report (PDF)
The first year of a Master’s degree is often viewed as a simple academic transition. However, when combined with a demanding apprenticeship at Orange Business Services (OBS), it transforms into a true test of professional maturity. This article reflects on the construction of my activity report—an exercise required by Ynov Campus that forced me to step back and analyze my evolution: from an integrator role to that of an autonomous technical lead.
1. Understanding the Purpose: Beyond a Simple “Logbook”
The classic mistake when writing a end-of-year report is falling into a chronological description. The academic and professional expectations for this deliverable were clear: analysis takes precedence over description.
It was not about listing JIRA tickets resolved or lines of code written, but about demonstrating a reflective posture. Why did I make this architectural choice? What was my actual impact on the team? How did I mitigate the isolation of being the sole developer in my domain?
2. Professional Context: A High-Stakes Industrial Environment
My integration into OBS did not take place in a sandbox. I was directly immersed in Industry 4.0 and Edge Computing projects, where operational technology (OT) constraints often dictate rules to IT.
I structured my report around my ability to thrive within this complex organization. My role quickly evolved: from a technical executor (Flutter/Python development), I stepped into the responsibilities of mobile lead, requiring constant interaction with diverse stakeholders (project managers, domain experts, industrial clients).
3. Critical Analysis of My Missions
[!IMPORTANT] A great report relies on concrete metrics.
Rather than listing my tasks, I selected the missions with the highest impact. For instance, the architectural overhaul for the APS integration (PlanetTogether). I dissected this mission following a strict analytical framework:
- The Context: An unmaintainable monolith threatening future deployments.
- The Method: Applying Clean Architecture principles and modular breakdown.
- Fact-Based Results: Transforming a chaotic script into a 130-line orchestrator backed by 716 automated tests.
4. Leadership, Autonomy, and Problem Solving
Being the sole developer on a product (Single Point of Failure - SPOF) carries significant risk for the business, but above all, immense pressure for an apprentice.
In my report, I documented the strict discipline I adopted to keep moving forward:
- C4 Architecture Diagrams: To map the system and share knowledge.
- Capacity Management: Learning to say “no” and plan realistically.
- Cross-Domain Communication: During factory audits, I stepped away from my IDE to talk with operators on the ground and understand their genuine friction points.
5. Uncompromising Assessment: Failures & Lessons Learned
A purely self-congratulatory report carries no value. The jury (and myself) expected an honest evaluation of my struggles.
I addressed early time-management mistakes at the start of my apprenticeship, as well as the challenge of establishing quality standards (such as automated testing) in environments where fast delivery is sometimes prioritized over technical debt reduction.
These setbacks were my best teachers. They justified implementing my multi-model AI workflow (GPT-4o, Claude Opus) to accelerate design phases without compromising quality.
[!NOTE] This report marks the end of a cycle. While Master 1 taught me to solidify my engineering skills and work autonomously, my Master 2 goal is clear: strengthen technical leadership and expand my influence over the global architecture of OBS projects.