DEV Community: Tinotenda Mhedziso

Debugging Adventure Day 1: What to Do When Your Code Doesn’t Work

Tinotenda Mhedziso — Wed, 15 Jan 2025 11:14:34 +0000

During your coding quest, you encounter a formidable enemy—an unexpected bug in your project that brings everything to a halt. What do you do?

You have three initial choices:

Toss your computer out the window and rage quit.
Start sprinkling logs or print statements everywhere.
Calm down and retrace your steps.

Option 1: Toss your computer out the window

In a fit of frustration, you decide that enough is enough. You hurl your computer out the window, hoping to banish the bug once and for all.

--Intelligence
--Stamina

Result:


function gameOver()
{
console.log("Game Over: Bug wins. You lose.");
}

Insight:

Rage quitting doesn’t solve anything. Time to respawn and try again.

Option 2: Sprinkle logs or print statements everywhere

You decide to log everything you can. Whether it’s console.log, print(), or trace(), you add them at key points in your code. Soon, your terminal or console is flooded with output.

Next Steps:

Examine the logs for clues. You realize one variable isn’t what you expected—fixing it makes the code work!
Try running it again. It works! But wait… you add a new feature, and suddenly, a new bug appears.

Insight:

Logging is a great way to trace issues, but don’t overdo it. Once the bug is fixed, clean up your logs.

Option 3: Calm down and retrace your steps

You take a deep breath and decide to approach this calmly.

You carefully check recent changes—maybe something broke after your last edit.
You read through any error messages and try to understand them.

throw new Error("Resource brain not found. Please try turning it on and off.");

throw new Error("TypeError: Expected logic, but received chaos.");

throw new Error("Permission Denied: You do not have clearance to understand this code.");

throw new Error("404 Error: Bug not found, but don’t worry, it’s lurking somewhere.");

You decide to isolate parts of your code and test smaller chunks independently.

While retracing, you spot a typo. You fix it, and your project runs perfectly! For a moment, everything feels right in the world. ++Intelligence

But wait… when you try adding a new feature, the project breaks again. Another bug has appeared!

Do you:

Add more logs? (Go back to Option 2)
Use a debugger to step through the code?

Using a Debugger

You switch tactics and decide to use a debugger. You set breakpoints, step through the code, and watch how values change. After a few minutes, you find the issue—a misplaced condition. You fix it, and the feature works!
++Intelligence

Insight:

Debuggers are great for finding subtle issues. Use them to step through complex code.

A New Bug Appears!

You fix one bug, and another one takes its place. This time, it’s more stubborn. Frustrated but determined, you press on.
--Stamina

You have three choices:

Ask for help on a developer forum.
Take a break and return later.
Keep bashing your head against the keyboard until it works.

Option 1: Ask for help on a developer forum

You craft a question and post it online, but you rush through it, providing little context and no reproducible example.

throw new Error("Stack Overflow: Too many recursive thoughts. Try calming down.");

Result:

Your question is ignored or gets sarcastic replies. You feel even more frustrated.

function gameOver()
{
console.log("Poor communication leads to dead ends.");
}

Respawn and try again: This time, you post a detailed question with proper context. A helpful developer points out that you missed initializing a variable. You fix it, and things start working again!

Option 2: Take a break and return later

You decide to step away for a bit. After a walk and a snack, you return with fresh eyes.
++Stamina

You scan through the code and immediately notice a mistake—something you overlooked earlier. You fix it, and your project works perfectly!

Insight:

Breaks help you see things you missed when frustrated.

Option 3: Keep bashing your head against the keyboard

You refuse to give up and keep testing random fixes without a clear strategy. Hours pass, and you make no progress. Eventually, exhaustion sets in.
--Intelligence
--Stamina

Result:

function gameOver()
{
console.log("You have been struck with the Burnout effect.");
}

Insight:

Persistence is great, but without a clear plan, it leads to frustration. Take breaks when necessary.

Final Victory

After fixing multiple bugs and pushing through the frustration, your project finally works. You’ve conquered the bug, added new features, and learned valuable debugging skills:

Stay calm and retrace your steps.
Use logs or print statements to trace errors.
Leverage debuggers for complex issues.
Ask for help when needed—clearly and concisely.
Take breaks to maintain clarity.

You’ve won the Debugging Adventure! Go forth, and may your future coding quests be bug-free (or at least, less buggy).

function victoryAchieved()
{
++Intelligence;
++Stamina;
level = 2;
console.log("You have been promoted to debugger level 2.");
}

Unlocking the Secret Gem Inside a Centered Div.

Tinotenda Mhedziso — Sun, 12 Jan 2025 17:37:41 +0000

If you’re just starting out on your web development journey, you’ve probably realized how frustrating CSS can be when you don’t fully understand what you’re doing. Cascading Style Sheets (CSS) is crucial for styling a web page, but things can quickly get overwhelming if you lack a solid understanding of UX principles or how color schemes influence the mood and usability of a website. Luckily, there are plenty of helpful tools and resources available to make the process easier, and after spending countless late nights perfecting my own designs... or I would like to believe, I’ve found some gems worth sharing.

Here are a few tools that can elevate your CSS skills and give your websites a professional touch:

1. Dribbble.com

View it Here

A Treasure Trove for Design Inspiration

Starting with design inspiration, Dribbble is a social networking platform where designers showcase their creative works. So, how does this help you as a developer? Well, even though you’re focused on code, understanding design is just as important. Dribbble can help spark ideas and activate your creative instincts. Browse through various designs, layouts, and themes—but don’t just copy what you see. Instead, use it as a blueprint to create something uniquely yours.

Pro Tip:

While browsing Dribbble, take note of how different elements are arranged, what color schemes are used, and how spacing affects readability. Try to replicate a design in your own style using HTML and CSS. This hands-on practice will help you master layout techniques. You can search for any design, ranging from Fitness website to a Game one.

2. Uiverse.io

View it here

Your Go-To Platform for CSS Components

Once you have a design idea in mind, the next step is to turn it into code. Whether you’re opening a new pen on CodePen (just type ‘pen.new’ in your browser), firing up Visual Studio Code, or—please don’t—reaching for Notepad (really please don't), you need components to build your UI. That’s where Uiverse comes in. It’s a fantastic platform that offers pre-built CSS components for buttons, cards, loaders, and more.

How to Use Uiverse:

Find a Component You Like: Uiverse has an extensive library of components designed by the community.
Copy the Code: Grab the HTML and CSS code for the component.
Tweak It: Adjust the styles to match your project’s look and feel.
Learn from It: Instead of simply pasting the code, break it down. Understand how each CSS property is used to achieve the final design.

Why It’s Worth It:

Uiverse isn’t just about copy-pasting components—it’s about learning how individual elements work. By tweaking the code, you’ll gain a deeper understanding of CSS properties, transitions, and animations.

3. Coolors.co

View it here

Nailing the Perfect Color Scheme

Design isn’t just about structure; color plays a huge role in setting the mood and guiding user interactions. Coolors is a color palette generator that helps you create beautiful and harmonious color schemes for your website.

Features to Explore:

Generate Palettes: Click through different combinations until you find one that suits your design.
Lock Colors: If you find a color you like, lock it and generate complementary shades.
Export Options: Once you’ve got your palette, export it as a CSS or PNG file.

Pro Tip:

Stick to a limited palette (3-5 colors) to maintain a clean, professional look. Use contrast wisely—high contrast for text ensures readability, while subtle contrast can add depth to your background elements.

4. Box-Shadow Generator

View it here

Mastering Shadows and Depth

Box shadows can add a lot of depth and realism to your design when used correctly. If you struggle with creating shadows that look just right, a box-shadow generator can be a lifesaver.

How to Use It:

Pick Shadow Settings: Adjust parameters like offset, blur, and spread.
Preview in Real-Time: See how the shadow looks on a sample element.
Copy the CSS: Once you’re happy with it, copy the generated CSS code.

Why It Matters:

Shadows can create a sense of hierarchy and focus on important elements. They also add a subtle 3D effect, making your design feel more polished and engaging.

Final Thoughts

CSS doesn’t have to be a nightmare. With the right tools and a bit of practice, you can transform your designs from basic to beautiful. Remember, mastering CSS is about understanding the fundamentals, experimenting with different styles, and always keeping user experience in mind. Let me know if you have used any of these tools or share any other tools our community should utilize. At the end of the day experience is the best teacher so stop rethinking things and just start styling today.