ACCESS DLSU

Let the good times roll, ID 126! 🎉🎭🎷

ACCESS is incredibly thrilled to welcome you to FROSH WALK 2026: PARADA ANIMO! 🎊✨

As you make your way down the Frosh Walk, know that you are entering a community eager to share this transformative experience with you. Get ready for a week of movement, inclusivity, and unforgettable connections that bring us all closer together. 💃🕺

Welcome, ID 126! Let the parade begin! 💚🎇






Pub by: Justin Pallasigui
Caption by: Evan Punzalan

As per FW-IMC Approved: FW26-0053

Get a sneak peek into the world of programming and discover which language matches your passion!

Whether you want to build AI recommendation systems and automate cybersecurity with Python (the secret behind Netflix and Spotify 🎵), or create interactive, real-time web experiences with JavaScript, there’s a path for you. Dive into the foundational structure and styling of HTML & CSS to craft stunning, user-friendly interfaces, or take direct control of hardware, automotive systems, and operating systems like Linux with C. If speed and high-performance are your goals, C++ is the engine behind blockbuster games like Fortnite and Valorant, as well as lightning-fast financial trading systems.

No matter your interest, coding is the key to turning your innovative ideas into reality! ✨

Find your coding path and start building the future! 💻





Caption by: Aaron Dionisio
Pub by: Charles Rodley Mercado

As Per CSO-PNP Approved: OPA-08883

ACCESSing Reviewers: MXSIGFN - Long Quiz #3 ⚡📡

Master the essentials of Fundamentals of Mixed Signals and Sensors with our reviewer designed to help you understand concepts, breakdown problems and prepare you smarter.

🔗 Access the reviewer here: https://accessdlsu.com/

Level up your learning with ACCESS 🚀





Pub by: Fia Lansangan
Caption by: Johann Huang

As Per CSO-Approved: OPA-07020

Transmission Unlocked! 📡 Did you get through the final stage, debuggers? 👀

Check out the solution key for Level 3: Runtime Errors – The Code Just Crashes Out. ✨👾

Here’s the moment you have been waiting for. This is when your code executes… and then crashes in an unexpected way. It’s nothing more than a value that has reached its maximum, causing the crash of everything else. ⚠️💥

Take a look at the problem analysis below and see if you can spot the error before it causes a crash. 🧠🔍

From syntax errors, logic, and runtime errors, this was your last challenge. Stay sharp, engineer 🚀💜





Caption by: Jerome Cruz
Pub by: Fia Lansangan

As Per CSO-PNP Approved: OPA-08789

Final transmission… 🚀 Are you ready for the finale?

Welcome to Level 3: Runtime Errors — when the code just stops, and you’re left staring at the screen to ACE your debugging skills! 👾💻

You’ve made it through every challenge so far. You caught syntax errors, fixed logic flaws, and pushed your problem-finding habits further each day. But now, you’ve hit the final test… the one that doesn’t warn you, doesn’t bargain, and doesn’t really give second chances. It just runs… and then everything sort of collapses. ⚠️🔥

Ever heard of the Ariane 5 Flight 501 failure? Read more below on how a $500 million rocket self-destructed in a span of 37 seconds after its liftoff. That’s the danger of runtime errors: they don’t show up until it's too late.

That’s why this level feels a bit different. This is where systems fail while they’re still running, and not after the fact. This is where assumptions crack in real time.

The Challenge:

We’ve intercepted a Python program that looks steady—until it stumbles over a value it wasn’t built to manage. Right at that moment, the program crashes. Your task is to track down the failure, pinpoint exactly what triggers it, and determine why it occurs during ex*****on. More than that, connect it to the real-world situation it represents. 🔎

This is the last challenge. The final level. The ultimate test of how you think like a debugger. ⚙️





Caption by: Jerome Cruz
Pub by: Fia Lansangan

As Per CSO-PNP Approved: OPA-08788

Transmission decoded! 📡 The truth behind the silent bug is finally here!

The answer key for the Level 2: Logical Errors challenge has arrived! ✨👽
Did you catch the invisible flaw? The conversion formula was inverted! To convert pounds-force to newtons, you must MULTIPLY by the conversion factor (4.44822), not divide. 🧮

🔴 Before the fix: 500 / 4.44822 = ~112.40 N. The program falsely reports ""Thrust is within safe limits.""
🟢 After the fix: 500 * 4.44822 = ~2224.11 N. The program correctly triggers ""WARNING: Thrust exceeds safe limit!""

Just like the real Mars Climate Orbiter, the danger wasn’t a system crash; it was a wrong number that looked plausible enough to trust. The ultimate debugging habit to build? Always check if a program’s output matches an independent estimate, not just whether it runs! 💥🛸

Join the conversation: Have you ever had a program run smoothly but return the wrong result? What was your ""aha"" moment? Share it below! 👇





Caption by: Aaron Dionisio
Pub by: Fial Lansangan

As Per CSO-PNP Approved: OPA-08787

ACCESSing Reviewers: DSIGPRO - Long Quiz #3 📈🎛️

Master the essentials of Digital Signal Processing with our reviewer designed to help you understand concepts, breakdown problems and prepare you smarter.

🔗 Access the reviewer using the link in the comments

Level up your learning with ACCESS 🚀





Pub by: Fia Lansangan
Caption by: Johann Huang

As Per CSO-Approved: OPA-07020

Every pixel in sight👀, stored away in every BYTE👾

Let’s take a look back at the moments and memories in BYTE: Beyond Your Technical Expertise 💻

The shared knowledge and insights given by our speakers not only brought wisdom 🧠 but a sense of motivation and hope 🤍 for the future endeavors of our CpE students 👤

See you in the next adventure 🚀





Pub by: Yohann Rigo
Caption by: Sidney Tan

As Per CSO-PNP Approved: OPA-08803

Incoming transmission… 🛸 But this time, the code isn’t crashing it’s lying to you.

Welcome to Level 2: Logical Errors for ACE Your Debugging Skills! 👾💻

Have you ever wondered how a program can run perfectly, show zero errors, and still cause a $125 million disaster? In 1999, NASA’s Mars Climate Orbiter was lost in the Martian atmosphere. There was no crash and no error message. The program ran flawlessly. It simply gave the wrong answer because one team calculated in metric units (newtons) while the spacecraft's software expected imperial units. 🚀📉

The Challenge:

We have intercepted a Python code snippet in the images below. It compiles and runs without any errors, but it’s hiding a deadly logical flaw. 🔎
Can you spot the reasoning error? Analyze the code, trace the math step by step, and tell us: What should converted_thrust actually be, and where is the logic failing? Drop your findings in the comments! Good luck, debuggers! 🌟👽





Caption by: Aaron Dionisio
Pub by: Fia Lansangan

As Per CSO-PNP Approved: OPA-08786

Transmission decoded! 📡 How sharp was your radar, debuggers?

The answer key for the Level 1: Syntax Errors challenge is finally here! ✨👽

Read the breakdown below to see if you managed to catch all 4 glitches hiding in the code. We also explained why these tiny syntax errors, such as missing semicolons or unmatched brackets, can cause data compilation errors and system crashes. 🚀💥

Compare your analysis against the official log, and keep your minds sharp. We will see you for an even trickier Challenge! 🛸💜





Caption by: Evan Punzalan
Pub by: Fia Lansangan

As Per CSO-PNP Approved: OPA-08785