danpamisa

[danpamisa]

Week 18

Final exam week! At first, I was expecting something tough—maybe enumerations or essays—but to my relief, it was a 50-item multiple-choice test with more than enough time.

The surprise twist was that Sir Carl gave bonus points to students who wore themed headbands. I made one using unused folders and papers and created a naruto themed headband. It was a creative way to end the term on a lighter note.

That’s it for this chapter. Here’s to finishing strong and finding new ways to stay motivated!

[danpamisa]

Week 17

Instead of a regular class, this week was set aside for independent project work. We used the time to focus on our system and push it closer to completion. Our instructor reminded us to make the most of this chance.

We also got confirmation that our second final quiz will be held online, which gives us some flexibility in how we prepare.

Staying focused to keep both the project and exam prep on track!

[danpamisa]

Week 16

Each group presented their project this week, showing at least 70% completion. Even though our group hadn’t quite hit that mark, we still presented clearly and ended up scoring 78/100 for both frontend and backend.

There are still areas to improve, but the feedback was helpful. It gave us clear direction on what to work on for the final stretch.

We’ll use this input to finish strong!

[danpamisa]

Week 15

This week, we were introduced to Data Visualization—an important part of making data clear and useful. We learned how to use charts and graphs to present information effectively.

After the lesson, we got to apply the concepts through hands-on activities. We ended the session after finishing all the tasks.

Looking forward to using these new skills in our project!

[danpamisa]

Week 14

In our face-to-face session this week, we focused on Data Mining. The lesson helped us understand how to find useful patterns in large datasets. We also had a short seatwork activity to apply what we learned.

It was supposed to be a day for project consultation too, but some group members couldn’t attend due to scheduling issues.

Hoping for better coordination next time so we can make the most of these sessions

[danpamisa]

Week 13

This week’s face-to-face class started with Part 2 of our quiz, continuing from last week’s online exam. The SUS-related problem-solving section was manageable, but due to time pressure and not having a scientific calculator, I wasn’t able to answer everything completely.

After the quiz, we had a discussion on Software Quality Management. It was a solid session—our instructor emphasized how crucial this is for maintaining standards in software development. We wrapped up after the discussion.

Looking forward to improving next time, especially with preparation!

[danpamisa]

Week 12

This week, we didn’t have face-to-face classes and instead had to take Part 1 of our assessment online. It included 48 questions with a 45-minute time limit. The online setup was due to the Lenten holiday, so everything was done remotely. I was glad I managed to pass the quiz. Later, Sir Carl updated us through the group chat that Part 2 will be done on-site, so I’ll need to prepare for that.

[danpamisa]

Week 11

This week, our instructor provided learning materials and video lectures to support our studies. It also marked the beginning of our final assignments for the second semester in our SDE course. We had both individual and group tasks to complete, which were submitted both digitally and as handwritten copies. The individual tasks were manageable, and I was able to apply the lessons from the provided materials. The group work also went smoothly, with good coordination and teamwork.

[danpamisa]

Week 10

Week 10 was our Figma prototype presentation day. Despite nerves, We prepared a backup version of our design to address potential gaps, though it remained unfinished by presentation time. At 6 PM, we presented to Sir Carl, but he stopped us after the second slide, asking us to revisit and present later. Exiting the room felt awkward—groups from other sections waited outside, and we regretted our rushed slides.

[danpamisa]

Week 9

Week 9 is centered on midterm exams divided into three sections: multiple-choice question on core concepts,identification for labeling system diagrams, and analysis diagnosing workflow inefficiencies. While challenging, the structure emphasized both foundational knowledge and applied problem-solving. Though a few questions slipped past my preparation, the exam underscored the importance of balancing speed with accuracy under pressure.

[danpamisa]

Week 8

Week 8 introduced a Figma prototyping workshop, a session I’d looked forward to for weeks. Unfortunately, overlapping schedules forced a tough choice: my CAD (Computer-Aided Design) class clashed directly with the event. Missing the workshop was frustrating—Figma’s collaborative tools are critical for our upcoming UI/UX projects.

[danpamisa]

Week 7

The second midterm quiz . I studied thoroughly, but a few concepts still slipped my grasp. Part 1 (multiple-choice) showed improvement, and Part 2 (system Diagram) felt stronger—I answered nearly all questions, missing just one or two.  

While not perfect, comparing this to Week 4’s quiz revealed progress. Sometimes growth isn’t about flawless scores, but about refining how you approach problems.  

[danpamisa]

Week 6

Week 6 focused on system diagrams a critical tool for mapping project workflows. Visualizing processes through flowcharts helped our team align on how to structure tasks logically—no more guessing games!

We also had project proposal consultations, though I couldn’t attend due to personal commitments. Despite this, one of our group’s proposals was approved, but with adjustments: Sir Carl advised narrowing the scope to ensure feasibility. It was a reminder that ambition must balance with practicality in software development.

[danpamisa]

Week 5:

We started with a lighthearted icebreaker game. Quick thinking wasn’t my forte; others buzzed in answers before I could even process the questions!

Later, we dove into user experience (UX) critiques. Sir Carl showed us website screenshots, and we played detective: spotting design flaws like confusing navigation, cluttered layouts, or unreadable fonts. Our task? Diagnose the issues and suggest fixes. It felt like solving puzzles where the stakes are happy users!  

[danpamisa]

Week 4:

Midterms arrived, and Week 4 hit hard with a two-part quiz on Topics 1 and 2. Part 1 was multiple-choice—let’s just say my score wasn’t something I’d proudly say. Part 2? Even tougher: identification and analysis questions that left my brain feeling like a buffering video.  

[danpamisa]

Week 3:

Week 3 threw us a plot twist: Sir Carl had to attend an event, so class was canceled. But the learning didn’t stop!

1. Survey : Each of us drafted 5 survey questions for two project proposals. Bonus challenge: writing a formal approval letter for Sir Carl to sign.

2. Empathy Map: In pairs, we interviewed each other to create **user empathy maps**—a visual tool to understand stakeholders’ needs. Even though it was a paired activity, submissions were individual, pushing us to reflect deeply on our insights.  

[danpamisa]

Week 2:

The second week of our Software Development Engineering (SDE) journey kicked off with a much-needed energy boost. After a quick round of introductions , we dove into the role of a Software Analyst, a skill that’s crucial not just for our upcoming projects but for our future careers.  

A 30-minute sprint challenge! Sir Carl split us into groups and handed us a PDF with a real-world business problem. Our mission: brainstorm a solution and present it in a PowerPoint. Surprisingly, we pulled it off—proof that pressure *can* breed creativity.