Work Story
Returning to a Project With More Responsibility
Two Participation Periods
I worked on the Marine Food Inspection Program in two periods: February to April 2024, and September 2024 to March 2025.
During the first period, I focused on development. After leaving, I did not expect to return. Later, the company contacted me and asked whether I could help again. I decided to go back.
The Role Was Wider the Second Time
The second period was not simply a continuation of the same coding tasks.
I still worked on the software flow: vision and spectral camera preprocessing, AI-result postprocessing, data conversion, API delivery, and browser display. At the same time, I also handled project-coordination work in the small startup team.
That included:
- organizing requirements and development progress;
- writing reports and technical documents;
- coordinating schedules and field visits;
- communicating with the people involved in the project;
- connecting development problems to the next practical action.
What Returning Changed
Returning made me look at the same project differently.
The first time, I mainly saw the part I had to implement. The second time, I had to see how code, equipment, documents, schedules, and people affected one another.
That wider view changed how I think about software. A feature is not finished only because the code runs. Someone has to understand the requirement, prepare the input, receive the result, check the field condition, and explain what happens next.
A Boundary I Keep Public
The project included confidential material. I do not publish internal screens, datasets, partner information, model details, reports, or performance numbers.
What I can explain is my responsibility and the system flow. That is enough to show the kind of work I did without turning protected material into portfolio decoration.
The Lesson
Leaving and returning are both part of this story. The important part is that I returned to a wider responsibility and stayed with the work through development and coordination.