Month: August 2025

Monday, August 25, 2025 – Last week, I was assigned a new task, to build the final feature for the Next.js project. Alongside that, I was also introduced to a second task, which I’ll begin once the first one is completed.

While waiting for the API for my first task to be ready, I took the opportunity to work on creating a command API as a kickstart. This gave me a clearer vision of what to expect and how the flow should look. During this time, Mr. Peter also explained the objectives in more detail and answered my questions, which really helped me see the bigger picture of the project’s direction.

Once the API was ready, I returned to my first task. I started with the main page, which displays the list, and then moved on to the create and edit pages. My main focus was ensuring the “create” function worked smoothly. By the end of the week, I had completed the create page, though it wasn’t fully successful yet. That will be my main priority to refine and finalize this week.

Monday, August 18, 2025 – Last week, I continued working on the feature. With the event-triggering issue resolved, the update command could finally be called correctly. I then focused on implementing the calculation logic, which was the core functionality of the feature.

After updating the command API with the correct logic, I created controller tests to verify everything was working properly. When I demonstrated the progress to Mr. Peter, it turned out I had misunderstood part of the logic flow. I clarified the requirements with him to ensure I had the right understanding moving forward.

By the end of the week, I managed to complete the feature, although I still plan to conduct more thorough testing. I pushed all my changes, and Mr. Peter also explained the upcoming tasks I’ll be working on next week.

Monday, August 11, 2025 – Last week, I was assigned a new feature by Mr. Peter. The goal was to design a UI similar to Excel, where users could freely edit cells, and moving to the next cell would automatically save changes. Additionally, certain fields needed to be auto-calculated based on the updates.

To start, I created a simple get list UI, which was fairly straightforward. Afterward, I moved on to the UI portion, focusing on building a simple display list.

Next, I worked on an update command so that users could update data line by line instead of saving the entire list at once. This approach would be faster, but at first, I skipped adding the full calculation logic and only tested the basic command. I then integrated the UI with the update command. Unfortunately, it didn’t work as expected, the event wasn’t being triggered.

Towards the end of the week, Mr. Peter helped me identify the issue. It turned out there was a small mistake in the naming convention within the UI, which I had overlooked. Once corrected, the update event worked as intended.

Monday, August 4, 2025 – Last week, I couldn’t complete the UI for the latest feature I was developing. Since it was urgent and needed to be published quickly, Mr. Peter took over and finished it.

Meanwhile, a UI bug was discovered with button positioning on a feature I had previously worked on, the button was hidden on smaller screen sizes. I fixed the issue immediately and pushed my latest changes.

By the end of the week, I focused on testing and fixing several minor bugs across different features to ensure stability. I also received a new feature assignment from Mr. Peter, who explained the requirements in detail. I plan to begin working on this task in the coming week.

Monday, July 28, 2025 – Last week, I worked on a new task for the Nextjs project, where I was assigned to create a new UI page for a feature. Since the feature was quite similar to an existing system, the design process was straightforward and easy to implement.

Once the UI was completed, I immediately tested it. At first, there were minor bugs after sending the command. When the API was fixed, I tested again, but this time, nothing appeared in the progress section. Later, Mr. Peter helped by creating a progress bar helper and fixing the current logic of the progress bar, which resolved the issue.

Another small task I worked on was adding a SortBy filter in a different project. I began by building the UI logic and implementing enumeration for it. However, towards the end of the week, although the main feature was up and running, I was not able to finish the SortBy UI. Still, I pushed all my changes for review.