jeymzzzzzz

[jeymzzzzzz]

Week 17 (Part 2)

Continuation for Part 1, leads us to Week 17 (Part 2). Though it gave us short duration to finalize everything for the presentation, me and team managed to finish up everything and present them in a short time.

And what can I say? It was a success!! Finally!! Our hard work has paid off and both the papers and our webapp have been officially approved by our instructor, Sir Carl. This milestone marks a significant journey as a Computer Engineering student. Looking at back now, I mean way back since Week 1, I've come a long way to achieve something wonderful that can provide not both of the experiences in working other fields, but the hardships and countless nights of no-sleeping and Kopiko Blanca Twin Pack drinking spree have paid off. It serves us as a testament to their unwavering support and belief in our abilities.

THANK YOU SIRR LABYUU ADVANCE MERRY CHRISTMAS PO 🎉🎉🎉

[jeymzzzzzz]

Week 16 (Part - 1)

To give you a summary of our project, we kinda cooked the code to the point we had to cram everything in one night. From the software debugging to finalizing the manuscripts, just for everything to get exemptions on the final exams. Because, what would be a great idea to finish your papers and codes 100% then take an early Christmas break?

We eventually did present our papers, but... We had so much revisions to work on before considering it as an 100% complete. Luckily, Sir Carl had to announce that he will be exempting us in exchange for completing the manuscript papers and the code until Saturday (Week 17). So me and the team up for the challenge and work ourselves up at night just to finish it.

Week 17 coming up yo!

[jeymzzzzzz]

Week 15

This is actually our Quiz 2 and last day of SDE before finalizing our papers and website for the requirements of SDE. The quiz is all about covering the topics of Mining and Data Visualization. Luckily I had to study those topics and it went well. After dismissing us, we grab a one last picture to remind Sir Carl how awesome we are on our journey.

Week 16 LEZ GOO

[jeymzzzzzz]

Week 13-14

week 13 is our first week of Quiz in final term, so we was somewhat ready but not so ready. You could say we are in the middle of it. After the quiz, he gave a short discussion about data mining, explaining how companies use data to understand their customers and afterwards there would be an activity for it. Nicee.

Then fast forward to week 14, it was WELLness week (days) but we had to do something with our website, so me and the team had to visit to Osmena Hydraulics to give their honest-opinion about our software. And based on what it happend during the testing it was really good and they liked it very much! A big win for us.

[jeymzzzzzz]

Week 12

Aight week 12 week twelve! So to give u a bit of context, Sir Carl assigned a short seatwork to check if we had reviewed the course material on Topic 7: APIs. The lesson introduced the basics of APIs, including their definition, significance, functionality, examples, and types, such as public, private, partner, and composite APIs. For instance, they enable apps to integrate with social media platforms, payment gateways, or weather services. Sir Carl also elaborated on how APIs facilitate communication by sending and receiving requests between systems.

Afterwards, we had a group activity where we simulated a patient securely accessing medical records via an API linked to a healthcare provider's electronic health record (EHR) system.

Oh yeah one more thing.. This dude pulled a funny attempt on putting a weird wallpaper on the google chrome and everyone go nuts with it and had a good time hahahahahaha

[jeymzzzzzz]

Week 11

Wow, it's the final term. How the heck did I survive that? Well anyways, week 11 brings new topics and methods for software improvement. And week 11 is all about the Software Realibility and Quality Management.

Following the discussion, we moved on to a post-class activity involving group seat work, where each group tackled specific assignments related to this week’s topic. Additionally, our team decided to redesign the inventory UI after finding the initial design unsatisfactory, dedicating the entire week to improving its appearance and functionality.

Here's some revisions:

[jeymzzzzzz]

Week 10

Ahh yes, PIT Presentation. This is where I had to locked in for a bit. So much obstacles and challenges we had to encounter, but at the day of the presentation, we obtain some juicy results which led to us the positive results.

It was a 90% on front-end, and 80% on back-end. If there's an award for achieving that kind of goal, I would give the award to my coffee cuz hes the MVP

week 11 see u at cu — I mean USTP diay

[jeymzzzzzz]

Week 8-9

MIDTERM EXAMS WOWOWOWOWOWOWOW

We did our usual midterm exams around October, then afterwards I had to work on our code.

Update wise, I focused on the backend aspect of our program since I was in-charge of the backend aspect, while Raniel worked on the front-end side. With our one core member left the team, it's only the three of us to accomplish this subject

week 10 bye bye

[jeymzzzzzz]

Week 7

Week 7 is the Quiz #2 so to give you the elephant in the room.

The quiz played out as expected—surprising for some, but meeting the expectations of others, as everyone had their own take on it. 

Covers a range of topics, including enumeration, identification, especially the SUS (AmongUs), which is the System Usability Testing. 

In the end, everyone completed the quiz, and there was a lively discussion about the answers. The quizzes ultimately served as preparation for the midterms, with several sections appearing as questions on the exams. Quiz 2 is done, but a new boss comes to arise... I'm talking about Midterm Exams.

[jeymzzzzzz]

Week 6!

 Week 6 6keew. Anyways, Week 6 again for the Software Testing activity, in a way that ensures the development of our systems proceeds smoothly and enhances robustness, particularly regarding software design quality factors. The discussion also covered various types of testing that can be applied to our software for improvement.

Following the lecture, we participated in an activity where each team analyzed a provided software design to identify its flaws. We highlighted the mistakes or issues present in the design and proposed several solutions to correct or improve it.

T'was a lovely weekend. On to the next one (Week 7).

[jeymzzzzzz]

Week 5

 Fifth week is here brothers. And this was the week were we had to take a Quiz. There are two parts of Quiz. Part 1 is where we would take our online quiz on prisms. And part 2 is where we would take our face-to-face quiz.

Honestly I was also surprised since I wasn't expecting for a part 2 quiz. But hey, "it is what it is". Soo uhh it started with an identification section, followed by an analysis where they were given a scenario. In this scenario, they had to link specific aspects of the analysis and create a new function based on the given one.

While many students managed to answer several questions, some, including myself, struggled. During the quiz, an earthquake drill interrupted us, forcing us to pause and "evacuate." After the drill, we resumed the quiz. (Maybe in the next quiz I'll study hard)

[jeymzzzzzz]

Week 4

 Week 4, Week Four, Week 4! Man, it's been a month since I've ever started taking blogs for our SDE subject haha. It's a great way to track the team's progress from start to finish.

Anyways, it's been 4 Weeks since we've first tackled on SDE. We covered the topic of Software Design and its key objectives, also explored concepts such as Modularity, Abstraction, and other related ideas. While we discussed various approaches to software design, the primary focus was on Design Patterns, Implementations, Code Review, and Code Refactoring.

see u in week 5

[jeymzzzzzz]

Week 3

Week 3 came along, and this week is when we get to consult on our progress for the project's development.

To give you better context, our project is about an Inventory Management System (IMS) that handles basic IMS needs for people who want to implement technology in their company. Although the description seems basic, it is very useful and essential for startup businesses that want to improve their operations. While we're somewhat accustomed to these consultations, this was the first time we got to show our very own prototype of the project. We were a bit nervous but excited throughout the consultation hours.

Nonetheless, the presentation was successful, and we received a positive reaction from Sir Carl, which really boosted our morale and motivation to keep going. Despite the suggestions and recommendations he gave, we still have a long, long way to go before we can conclude that our project is complete.

Week 4 coming up!

[jeymzzzzzz]

Week 2

 Second week of SDE, Sir Carl Suasola discusses about the context of SDE or What is Software Design Engineering is all about. It gives a lot of details that reflects SDE into real life projects that most startup companies used to. It follows the topic by explaining that SDE is both Art and Science, since it blends creativity with technical rigor. The balance between structured problem-solving and creative innovation is what makes software design engineering both a science and an art. He further discuss about the SDE life cycle and introduce us the waterfall model, which he did discuss a while back on our Project Management, but this time with its different variations and aspects of the model itself.

After the discussion, we've given a group activity about deducting a case study about the company's background, its objectives, services, challenges faced, SDE applied on the company, and its conclusion. Which we are required to finish it around 30 minutes and one random individual from the group will present it at the front. Overall, it was a really fun activity and everyone was very cooperative with the activity itself and we even get the best laughs afterwards. 

Kitakits sa Week 3! <3

[jeymzzzzzz]

Week 1

How did I survive two years of suffering in this course? Honestly, I dunno. But I do know that starting in August, I will officially be a 3rd-year Computer Engineering student at USTP CDO.

The first week of Software Design and Engineering (SDE) was a breeze. It was an essential day for introducing ourselves to other students and getting to know a little bit about ourselves in the process. We recited our names, ages, and favorite songs. When it was my turn to shine during the recitation, I had many, many songs that could easily be my all-time favorites. However, I decided to go with Adele's hit song, Hello. 

Why Hello, you ask? Well, to be frank, I honestly don't know. Somehow, the song just popped into my head during the recitation, and I went along with it. But thinking it over, the word "Hello" seems fitting—it reflects my attempt to reconnect with everyone, including the faculty. I am entering my 3rd-year CPE with high hopes and this is my opportunity to reconnect with my new classmates. After all, introducing yourself is essentially about making your presence known to new classmates and getting to know them better.

The course outline covers the basic topics that students will encounter over the five-month period. It includes how to deploy our proposed work to an application, how to test it, how to maintain it, etc. Afterwards, we reviewed the grading system and recited the student pledge together. Over the course of the 3-hour class, that was essentially the gist of it. I don't know how this subject will unfold, but I am both excited and scared. It feels like a huge milestone for my future self.

See you for week 2, I guess?