Engineer’s Odyssey

a someones journey

[jfabsss-engineer]

Week 16: Eggventure is DONE!

This week, we had our final meeting with Sir Carl for the last checking of our application, Eggventure. It felt like a huge milestone because, after all the hard work and countless hours spent on refining the project, it was finally done. However, this week turned out to be incredibly rough and exhausting. The pressure of meeting deadlines, fixing last-minute bugs, and ensuring everything was in place for the final review made it feel like every minute counted. The stress of trying to perfect every detail, while also juggling other responsibilities, left little time for anything else. It was one of those weeks where you’re constantly running against the clock, and the exhaustion really started to take its toll. Despite all the challenges, getting the app ready for final review felt like a major accomplishment, and once it was done, there was a sense of relief mixed with pride in knowing that we had put everything into it. But after all the challenges, it was incredibly satisfying and relieving to finally see our project come to fruition. The feeling of completing the application and knowing we had put in so much effort and dedication made all the late nights and stressful moments worthwhile. It was a huge weight lifted off our shoulders, and the sense of accomplishment was overwhelming. As for Sir Carl, I genuinely enjoyed this course because of his guidance and teaching style. His ability to keep us engaged, challenge our thinking, and push us to perform our best made all the difference. Even when the going got tough, his support and insights kept us going. I’m grateful for his dedication to helping us succeed and for making the learning experience memorable. This course wouldn’t have been the same without his encouragement and expertise, and I can honestly say I’ll carry the lessons he taught us throughout my academic journey and beyond.

[jfabsss-engineer]

Week 15: Last na :((

This week marked our final session with Sir Carl, where we took Quiz 2 covering the last topics of the course—data mining and data visualization. To our surprise, he included bonus questions that were entirely subjective, and as someone who often struggles to express my thoughts clearly, I found them more difficult than the actual quiz. After finishing the quiz, we gathered to listen to a heartfelt farewell speech from Sir Carl. He expressed how much he enjoyed teaching our class, saying we were one of the groups he looked forward to meeting every Friday, even calling us one of the best. While I have a feeling he might say this to all his sections, I couldn’t help but feel a sense of pride. Sir Carl has truly been one of the most memorable instructors in my college journey. He help us to be more productive and to be more courageous in life, but he has a remarkable way of motivating us, pushing us to keep going even when things seemed tough. His guidance throughout this course has left a lasting impact, and I will carry the valuable lessons I've learned from him as I continue my studies, I am looking forward sir Carl as my instructor soon!

[jfabsss-engineer]

Week 14: Activity for Creativity

This week, we had our first quiz of the final term, covering topics on software reliability, quality management, and application programming interfaces. After the quiz, we all hoped for an early dismissal, but true to Sir Carl’s style, he dove straight into a discussion on data mining. Following the lecture, we were given an individual multiple-choice seatwork, which thankfully was straightforward and based on the discussion. Just when we thought we were done, Sir Carl surprised us with a written group activity. Despite the unexpected extra work, my group members were a fun bunch, and their jokes made the task more enjoyable. We finished the activity quickly and finally headed home. In week 14, I decided to get ahead by studying the materials Sir Carl shared on data mining, which introduced concepts like data warehouses, clustering, classification, and decision trees, used to uncover patterns in large datasets. I learned how businesses apply data mining for fraud detection and customer insights, which helped me appreciate its value in transforming raw data into actionable information. Studying on my own allowed me to dive deeper into topics like data preprocessing and the steps involved in the data mining process, including problem identification, method selection, and result interpretation. I was particularly intrigued by how methods like decision trees and clustering simplify complex datasets to solve real-world problems.

[jfabsss-engineer]

Week 13 : Study na

Since there was no class today, I used the opportunity to study the materials shared by Sir Carl, particularly on Application Programming Interfaces (APIs). APIs act as a bridge that enables different software systems to communicate and share data seamlessly. For instance, when a weather app retrieves current conditions from a server, it uses an API to fetch and display the information. APIs not only make software interactions more efficient but also save time and reduce errors by automating tasks. Their role in ensuring fast and accurate data exchange is invaluable in today's fast-paced digital world. Additionally, I spent some time revisiting our manuscript, applying the concepts I’ve learned to refine its structure and content. This revision process helped clarify our ideas and ensured that everything adhered to the principles of effective communication and best practices in software development. The idea of finally having some time to recharge and reset gave me a surge of energy, and with that renewed drive, I tackled the group activity with a newfound determination. By the end of the day, the finish line felt within reach, and I knew completing this task would allow me to step into wellness week with a clear mind and a lighter heart.

[jfabsss-engineer]

Week 12: KAKAPOY IS STARTING

This week in Software Engineering and Design, we focused on Software Reliability and Quality Management, emphasizing the critical need for creating trustworthy systems. Sir Carl explained that software reliability is all about ensuring that programs run without failure over a defined period. We explored key metrics such as Mean Time Between Failures (MTBF), which helps predict the expected uptime of a system, and Mean Time to Repair (MTTR), which measures how quickly issues are resolved. By examining these metrics alongside failure rates, we gained valuable insights into a system's long-term reliability. This lesson reinforced the idea that software development is not just about writing code; it’s about crafting systems that users can depend on, even in the face of challenges. Prioritizing reliability ensures that software not only fulfills its intended purpose but also builds user trust through consistent and predictable performance.

[jfabsss-engineer]

Week 11 : FINALS NA

This week, I gained a deeper understanding of what truly defines high-quality software. Software quality is not just about a program running without issues; it's a broader concept that encompasses several key characteristics. These include correctness (ensuring the software meets its intended purpose), maintainability (how easily bugs can be fixed or improvements made), portability (how well the software performs across different platforms), testability (how easily the software can be tested for issues), reliability (its ability to function consistently under varying conditions), efficiency (how well it utilizes resources such as time and memory), integrity (security and protection against unauthorized access), reusability (whether components can be reused in other projects), and interoperability (how well the software works with other systems). Together, these factors ensure that the software is not only functional but also robust, user-friendly, and adaptable to evolving needs.

A key approach to achieving and maintaining software quality is through Software Quality Assurance (SQA). SQA is a structured method that ensures the processes and techniques used in software development adhere to predefined standards and best practices. It’s not just about identifying and correcting defects but also about preventing them through proper planning, monitoring, and assessment of the development process.

We also explored two widely recognized standards in this area: ISO 9000 and ISO 9126. The ISO 9000 series focuses on quality management systems, offering organizations a framework to consistently deliver high-quality processes and products. It emphasizes principles such as customer focus, leadership, employee engagement, and continuous improvement. On the other hand, ISO 9126 (now replaced by ISO/IEC 25010) specifically addresses software quality, defining it in terms of attributes like functionality, reliability, usability, efficiency, maintainability, and portability.

[jfabsss-engineer]

Week 10 : Finally

This week, my team and I presented our system, and at first, we were really nervous. We kept worrying about getting a low grade, whether Sir Carl would find our system lacking, or if a function might fail during the demo. Those thoughts weighed heavily on us, making it hard to relax before the presentation started.

Fortunately, Sir Carl’s friendly and approachable demeanor quickly eased our nerves. The presentation became more enjoyable as we found ourselves sharing a few laughs along the way, all while staying professional. He engaged with us throughout, making the whole experience feel more like a fun conversation than a stressful evaluation. His witty jokes, along with playful references to his favorite duo, Maki and Maloi, lightened the mood even more.

In the end, we couldn’t have been happier with the results—98 for our front-end and 94 for the back-end! It felt amazing to see our hard work recognized and appreciated. What stood out most, though, was how much we enjoyed presenting in such a supportive environment. It wasn’t just about the grades; it was about the positive interaction and experience that made all the effort worth it.

[jfabsss-engineer]

Week 9: Examination Day!

This week has been an exhausting whirlwind because it’s our midterm examination period, and I had to double down on studying just to stay on top of all my subjects. On top of the exams, we were also required to complete Performance Improvement Tasks (PITs), which made things even more overwhelming. Juggling all these responsibilities really tested my endurance and focus.

At the start of the week, I felt incredibly nervous, thinking the exams might be identification-based, which can be tricky and stressful. Thankfully, I was relieved when I found out that most of the tests were in multiple-choice format. It gave me a little breather, though I still had to stay sharp and manage my time well to get through everything.

One specific moment that stands out to me is from question number 41. I was so convinced that the answer was 52—but it turns out, I was wrong! Despite that small setback, I’m still proud of how far I’ve come and grateful for the progress I’ve made. Looking back, this week really stretched my limits, forcing me to dig deeper and push myself to study harder than ever before.

Overall, it wasn’t easy, but I feel accomplished. No matter the challenges or the nerves, I kept going—and that’s what truly matters.

[jfabsss-engineer]

Week 8 : It's Time

This week, I was a little bit nervous because after all my studying for the past few days — and before that month as well — it had to finally come into play. I was on the fence about going for this quiz however Sir Carl cracked a joke and make the class laugh. His humor makes the class calm.

To be honest, when it came to the quiz day I struggled! there were many questions that i forgot but, trusting with my guts and what i have studied makes me comfortable in answering all through out the quiz.

It was such a feeling of relief when I finally did. Doing the quiz brought me so much relief, knowing everything I put in had finally paid off. I even found myself around the dinner table after talking about how we all got through the hard portions which made it a little more enjoyable to compare notes with peers.

[jfabsss-engineer]

Week 7: No Class

This week has been all about keeping things moving. Even though we didn’t have class today, I still had work to tackle. I went over Activity 2, and while it felt a bit tricky at first, breaking it down into smaller parts really helped.

I also took some time to check out the lesson materials on USTEP to get ready for our upcoming quiz. Studying without the usual class routine wasn’t the easiest, but I stayed focused and got through it. I’m starting to see how keeping up with tasks, even on days off, really pays off in the long run.

One of the highlights this week was coding the authentication feature for our application. It was awesome to see everything come together. I had to do some debugging along the way, but when the login and registration system finally worked, it felt like such a win. Contributing to something so crucial reminded me of why I love coding in the first place.

I also worked on the database normalization for our project paper. Getting that right is so important, and it felt great to organize everything efficiently.

All in all, it’s been a busy week with its fair share of challenges, but I’m feeling good about the progress I made. No class doesn’t mean no work; it’s just a chance to get ahead. Each task I finish and line of code I write brings me closer to my goals.

[jfabsss-engineer]

Week 6 : Sus

This week has been both fun and exciting! We had an insightful consultation with Sir Carl about the development of our system, which really opened our eyes to new possibilities. Our classes were quite intense, running straight until 9 PM, but Sir Carl’s discussion on the System Usability Scale (SUS) and various programming and debugging approaches resonated deeply with our experiences.

One of the highlights was an engaging activity where we had to identify problems in a given picture and propose creative solutions. This exercise really encouraged us to think critically. We also practiced solving problems both manually and automatically using spreadsheets with provided data, which not only sharpened our technical skills but also boosted our confidence in tackling real-world challenges.

Additionally, we assisted our friend Fidel Bacol, who was left to complete an activity alone because his groupmates had to go to Manila. It felt great to lend a hand and support him, and it made the experience even more enjoyable for all of us. Overall, it was a week filled with valuable learning, teamwork, and collaboration!

[jfabsss-engineer]

Week 5: Put me In a Test

This week has been tiring, with lots of quizzes and assignments keeping me busy. One of the main events was our quiz in System Design Engineering, which I studied hard for. The topics included structural patterns, behavioral patterns, and creational patterns, all important for understanding design principles.

During the quiz, I felt overwhelmed by the difficult questions that tested my understanding in this subject. The last section, where we had to restructure diagrams, was particularly tough. I was quite nervous about how I was doing and whether my answers were correct.

However, I found some relief when our instructor, Sir Carl, gave us hints during the quiz. Hearing those clues made me realize that I was on the right track with some of my answers, which helped calm my nerves.

Overall, this week has been a real test of my focus and resilience. While it was challenging, I feel accomplished for pushing through. Now that the week is ending, I’m looking forward to some downtime to relax and recharge. Finding that balance is important as I prepare for whatever comes next!

[jfabsss-engineer]

Week 4: The Art of Software Design

This week was both exciting and full of learning. We had a project consultation with Sir Carl, which was a key moment for our project. He helped us identify the issues with our work and gave us clear advice on how to improve. His feedback was really helpful in shaping a better direction for our project.

The class was also very engaging. Sir Carl’s energetic teaching style made the sessions enjoyable. We had an activity where we were given a scenario and asked to create pseudocode and design a GUI. This was a great chance to apply what we’ve learned and practice our skills.

Through this activity, we saw how important good communication is within our team. Working together and sharing ideas helped us come up with better solutions. It was clear that teamwork and clear communication are crucial for making progress and achieving our goals.

Overall, this week was a great experience that not only helped us advance our project but also showed us the value of collaboration and ongoing learning in software engineering.

[jfabsss-engineer]

Week 3 : Being an Engineer

That evening, the atmosphere in our class was lively and upbeat, thanks to an engaging icebreaker game organized by Sir Carl. It was a great way to loosen up and bond with our classmates. Afterward, Sir Carl guided us through a detailed discussion on how to successfully build a project, with a focus on understanding and satisfying user requirements. This part of the class was insightful, as we explored the importance of aligning project goals with the needs of the end users—something crucial in software engineering.

The most interesting part of the night, however, was the hands-on activity where we had to conduct a paper review. We were given a specific scenario and asked to analyze it by identifying the purpose of the study, the challenges it faced, the methodologies used, and its overall impact. The catch? We had only 30 minutes to complete the task, which really added to the excitement and pressure. My group was assigned the topic iLearn: A Digital Learning Environment, a system designed to support learning for students aged 4 to 18 in schools. It was fascinating to dive into how digital environments like this can enhance the educational experience.

Everyone in the class was fully engaged, and the teamwork was incredible. I was fortunate to work with a group that collaborated seamlessly. We divided the tasks efficiently and contributed different perspectives to come up with a solid review. Once the time was up, each group had the opportunity to pitch their findings. Listening to other groups' presentations was both informative and thought-provoking. It was clear that each group had a unique approach to their analysis, making the session not only educational but also a great learning opportunity for everyone involved. The level of knowledge shared by my classmates was impressive, and it was rewarding to see how much we all learned from each other in such a short time.

[jfabsss-engineer]

Week 2: A Quickstart

This week, Sir Carl provided us with a comprehensive module that served as an essential introduction to the world of software engineering. The module thoroughly defined what software engineering is, explaining not just the technical aspects but also why it’s a crucial field of study. It delved into the fundamental skills required to succeed as a software engineer, offering a clear roadmap for what we should focus on as we progress through the course. My major takeaway from the module was the software development lifecycle, which detailed the step-by-step processes for creating, testing, and maintaining software. Additionally, the module covered various tools essential for modern software engineering. This foundational knowledge is key to bridging the gap between theory and practical application. Despite it being a holiday, my teammates and I decided to meet virtually via Google Meet to discuss what we had learned from the module. The discussion was incredibly productive; we were all on the same page, which made collaborating on Activity 1 much smoother. We shared insights, clarified doubts, and worked together to answer the questions posed in the activity. It was encouraging to see how well our ideas synced, and we’re now close to completing the first activity. This module, combined with the collaborative effort on Activity 1, has been a very effective jumpstart into the subject. It not only reinforced the theoretical concepts but also gave us the opportunity to apply them practically. I’m excited to see how these foundational skills will evolve as we continue through the course.

[jfabsss-engineer]

Week 1 : Orientation Day

My first day in Software Design Engineering was really fun and interesting. We started by introducing ourselves, and the creative ways my classmates shared about themselves made it enjoyable. Sir Carl then walked us through the course syllabus, explaining what we'll be learning and working on. His excitement about the course made me look forward to what's ahead.

We also did a student pledge, which felt like a good way to start our journey together as a class. It made me feel like we're all in this together, ready to help each other out.

The best part of the day was the project consultation. We got to talk about our project ideas, and Sir Carl gave us helpful feedback. I realized there were some things I needed to fix in our project , with that we felt encouraged to make it better.

Overall, the day was a great mix of fun and learning. It made me even more excited about the course, and I can't wait to keep learning and improving as we go along!