My Internship Blog

 Finally! My PC is fixed, and I’m back to developing on my own. After a week of sharing, it feels great to have my own setup again. Today, I jumped right back into development, applying everything I’ve learned from the past few days—especially on backend integration. I can already see how much smoother my workflow is now that I understand more about how the frontend and backend connect. Excited to see how much more I can improve as I move forward! (📸 Daily selfie outside)

It’s been a full week of sharing a PC with my co-mobile developer, and honestly, I really hope my unit gets fixed next week. Working without my own setup has been a challenge, but at the same time, I can’t deny how much I’ve learned from this experience. Before this, backend development felt like a mystery to me, but now I understand how it works—from structuring APIs to handling requests and integrating them into the frontend. This hands-on experience has helped me grasp backend logic better than just reading documentation or watching tutorials. Despite the technical setback, I’d say this was still a productive week. Now, I’m looking forward to applying everything I’ve learned when I get my PC back. (📸 Daily selfie outside)

The technician didn’t come again today, so I’m still sharing a PC with my partner. At first, it felt a bit frustrating, but now, I’ve started to enjoy it. I’m learning a lot from my partner, especially when it comes to server-side coding. He’s been guiding me through some of the more complex parts of backend development, and it’s great to see how everything ties together. While I’m still waiting for my PC to be fixed, this situation is turning into an opportunity to learn more and expand my skills. (📸 Daily selfie outside)

Finally, the technician arrived today! But unfortunately, the problem with my PC was bigger than expected. He wasn’t able to fix it within the day, and since he had other tasks lined up, my PC wasn’t prioritized for repair. So, here I am, still sharing a PC with my partner. It’s a bit inconvenient, but at least I’m still able to continue working, even if at a slower pace. Hoping tomorrow brings some progress with the repair. (📸 Daily selfie outside)

Still no technician today, and my PC remains unfixed. At this point, I’ve just accepted the situation and continued sharing a workstation with my partner. Surprisingly, I realized that working together on one PC has its advantages—we were able to exchange ideas in real-time, catch each other’s mistakes, and improve our code with two minds working on it. It’s not the ideal setup, but at least we’re making the best out of it. Hoping tomorrow brings better news about my PC. (📸 Daily selfie outside)

The technician still didn’t arrive, so I had to share a PC with my partner in mobile development. We took turns—when he finished his tasks, I swapped in to work on mine. It wasn’t the most efficient setup, but at least I was able to make progress rather than falling further behind. Hoping that tomorrow, my PC will finally be fixed so I can work at full speed again. (📸 Daily selfie outside)

Today was a rough day—my PC unit went down, and unfortunately, the technician wasn’t available to fix it. With no workstation, I couldn’t do much except oversee the work and follow my teammates' progress. It was frustrating not being able to contribute directly, but I still took the time to review the code and plan ahead for when my setup is back. Hoping for a better day tomorrow once the issue is resolved. (📸 Daily selfie outside)

The WiFi is finally back, and we were able to continue our work from where we left off. Since I lost time yesterday, I had to double my efforts to catch up on my feature. I focused on refining the frontend and making sure everything was aligned properly before moving forward. The extra push today was exhausting, but it felt good to make solid progress despite the delay. (📸 Daily selfie outside)

Today was an unexpected short day at work because of network issues. Our WiFi had no connection, so we couldn’t proceed with our tasks efficiently. Since everything we do relies on internet access, we were dismissed early for the day. It felt unusual leaving work earlier than usual, but I guess it’s a small break from the routine. Hoping the issue gets resolved soon so we can get back on track tomorrow. (📸 Daily selfie outside)

Today, I started working on a new feature from scratch, focusing on the frontend. It feels refreshing to build something without worrying about backend connections—just pure UI development. I really enjoyed the process, and everything went smoothly. Tomorrow, I’ll have to connect it with the backend, and I hope things go just as well. For now, I’m just satisfied with how the frontend is coming together. (📸 Daily selfie outside)

 Still working on frontend and backend integration, but today feels different. I’m finally gaining confidence in understanding how everything connects. The once confusing code is starting to make sense, and I can now debug and troubleshoot with a clearer approach. There’s still a lot to learn, but I’m seeing real progress. Looking back at how much I struggled before, I can say that things are improving. Persistence is really paying off. (📸 Daily selfie outside)

Still working on backend and frontend integration today! The process is getting clearer, but there are still some confusing parts in the code that I need to figure out. Some functions don’t behave as expected, and debugging them feels like solving a puzzle—frustrating but also satisfying when things finally work.  I’ve been reading through the code carefully to understand how everything is structured. It’s a bit overwhelming, but I know that once I get the logic, it’ll all start to make sense. Just need more patience and practice! Also, today’s coffee update: necessary as always.  (And of course, here’s my daily selfie outside 📸)

Today, I’m still working on connecting the backend and frontend. It’s a continuous process of testing, debugging, and making sure everything flows smoothly. Some parts are working as expected, while others still need fixing and adjustments. I’m slowly getting the hang of it, but there are still some challenges—especially when handling API responses and errors. But that’s part of the learning process, right? Trial and error until it works!  Hoping to fully integrate everything soon!  And yes, today’s coffee break was well deserved.  (Here’s my daily selfie outside 📸)

Today, I finally understand better how to connect the frontend and backend! It turns out that all I really needed to do was study the APIs and services provided by the backend and make sure I’m using the correct routes to fetch and send data properly. Now that I’ve got a clearer grasp of how everything ties together, things feel less overwhelming compared to before. It’s actually exciting to see how the frontend and backend communicate seamlessly!  Looking forward to applying this knowledge in the coming days and building more features. Also, today’s coffee count: still at a reasonable level… for now. (As always, here’s my daily selfie outside 📸)

Today, I tried working on frontend and backend integration since we already have an existing backend. Now, it’s just a matter of connecting it properly to the frontend. Since I’m still learning, I had a bit of a difficult time understanding how everything works together. Familiarizing the connection between the two took some effort, but thankfully, Postman made things easier! It helped me test the APIs quickly and see how the data flows. Though I still have a lot to learn, I can feel myself slowly improving. Excited to get better at full-stack development!  (And of course, today's coffee break was a lifesaver once again!) (As always, here’s my daily selfie outside 📸)

Today, I spent time reviewing my intern mate’s code to understand how they structured the backend and integrated it into the frontend. I was really curious about how everything connects—from database to backend, and backend to frontend—since this is my first time diving into backend coding. Since we’re tasked with full-stack development, I know I have to step out of my comfort zone and learn more about the backend. But of course, my true forte will always be frontend development.  This day was mostly about observing, analyzing, and understanding the flow, but I know this knowledge will be really helpful once I start working on backend tasks myself. Excited to learn more!  (And yes, another coffee break was needed for all the studying.) (As always, here’s my daily selfie outside 📸)

FINALLY! I finished the feature today, and I couldn't be happier! After struggling for the past two days, I can finally say to myself, "I did well today."  It was definitely a challenging task, but it was also filled with valuable lessons. I learned a lot about Understanding  the logic behind complex features,  Finding easier solutions to certain functions,  Practicing clean code for better readability,  And so much more! This experience really pushed me, but in the end, it was worth it. Now, I’m ready for the next challenge! (And yes, today’s celebratory coffee just tastes even better!) (As always, here’s my daily selfie outside 📸)

I’m still working on the feature I started yesterday, and let me tell you—I totally underestimated it. I thought it was going to be easy, but turns out, it’s actually a big feature for the project. At some point, I even started doubting myself, thinking maybe I couldn't pull it off. But, despite the struggles, I made progress!  I’m still in the middle of it, and this is the first time I’ve worked on a task that takes multiple days to complete. It’s a new experience for me, and while I didn’t finish it today, I’m hoping tomorrow will be the day I finally get it done. Of course, another stressful day means another cup of coffee. At this point, I just hope my caffeine and sugar levels don’t spike too much! Hahaha. (And as always, here’s my daily selfie outside 📸)

Today, I was assigned to work on a feature, and I decided to make it functional right away. This way, when we connect it to the backend, we’ll only need to dynamically update the data or functions, since I just used static data for testing. I’m also learning a lot as I go—figuring out the logic and understanding how the system should function properly. It’s a great experience to see things come together! And of course, coffee remains my coding stress saver. Today, I even brought my own cup so I don’t have to use the office cup. Gotta keep up my daily caffeine fix while grinding through the code!  (And as always, here’s my daily selfie outside 📸)

Today felt a bit different since I was the only intern at the office. My fellow interns were scheduled for their pictorial, and since I already had mine yesterday, it was their turn today. With the office feeling a bit quieter than usual, I decided to take things slow and just focus on making small progress in our project. I added some minor functions here and there—nothing too big, just enough to keep the momentum going until my shift ended. A chill and productive day overall! Looking forward to having everyone back on Monday.  (And as always, here’s my daily selfie outside 📸)

Two weeks in, and I can say I’m finally getting the hang of my routine! I’ve adjusted my body clock, and I’m actually proud of myself for waking up early now. No more late-night coding sessions—well, at least for now.  an definitely be stressful, but I’m enjoying my time at IDESS IT. Having great teammates makes a huge difference—they keep the atmosphere lively and fun, making each day more enjoyable. I may not be close to all of them yet, but I hope that changes over time. Looking forward to building friendships along the way.  (And as always, here’s my daily selfie outside 📸)

Today was exhausting. We encountered several bugs in the frontend, which took a lot of time to fix. Debugging can be frustrating, but it’s all part of the process! One major change we made was switching our navigation to Expo Router. Initially, we were using a mix of Drawer Navigation, Stack Navigation, and Bottom Navigation, which made things nested and complicated. With Expo Router, navigation becomes much more manageable and easier to work with. Definitely a good decision for the long run! And of course, coffee was my savior today. Without it, I don’t think I would’ve survived all the debugging and navigation restructuring.  (And as always, here’s my daily selfie outside 📸)

Today was a bit challenging. I ran into some struggles with React Native imports, mainly because I’m still not that familiar with how everything works compared to React.js. Another issue I faced was with the expected functions not working properly. It was frustrating at first, but I realized that some things needed to be changed and relearned to fit the React Native environment. Despite the struggles, I see this as an opportunity to grow. I’ll take my time to debug, research, and learn more about how things work in React Native. Slowly but surely, I’ll get the hang of it!  (And as always, here’s my daily selfie outside 📸)

Today, we officially kicked off the development stage! The first step was setting up our development environment, making sure everything was running smoothly before diving into coding. We also had a team discussion where we shared ideas and opinions on how to properly structure our code. It’s important to keep our project organized and scalable, so we talked about: ✅ Folder structure  ✅ Component reusability  ✅ State management  ✅ Best practices for clean code  It’s exciting to finally start bringing our designs to life in React Native! Looking forward to seeing our progress in the coming days. (And as always, here’s my daily selfie outside 📸)

Today, we completed the UI design for our mobile project. It feels great to finally see the full layout come together, and now, we’re getting ready to start the actual development. Of course, some designs still need polishing, but we decided to improve them as we go along during development. Sometimes, things look good in Figma but feel different when implemented, so we’ll be making adjustments along the way. Excited (and a little nervous) to finally start coding this project! Let’s see how things go.  (And as always, here’s my daily selfie outside 📸)