This is so cool, my first post for CS-348. Stay tuned for more posts like this

From the blog CS@Worcester – Code Craft by Kyle Tucker and used with permission of the author. All other rights reserved by the author.

Hi my name is Thanas Lara and this is my first post on my brand new blog. I have officially started the course of Software Process Management and am excited to add more to my knowledge of computer systems and software in general.

From the blog CS@Worcester – Thanas' CS Blog by tlara1f9a6bfb54 and used with permission of the author. All other rights reserved by the author.

This blog will be about my progression and learning I do with the material used within the class and how I use it in class projects, as well as how I use the material with my own personal projects.

From the blog CS@Worcester – CS Blog by Mike and used with permission of the author. All other rights reserved by the author.

September 7, 2024

This is the first blog post on my website. I will be documenting my computer science journey as well as interesting new developments in the tech world.

From the blog CS@Worcester – The Science of Computation by Adam Jacher and used with permission of the author. All other rights reserved by the author.

This is my first blog post for my course CS-348, Software Process and Management! Quite exciting!

~Michael Clark

From the blog Mike's Byte-sized by mclark141cbd9e67b5 and used with permission of the author. All other rights reserved by the author.

This will be my blog for the CS-348 Software Process Management course.

From the blog CS@Worcester – Year #3 by gchude and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Year #3 by George Chude and used with permission of the author. All other rights reserved by the author.

What is a debug duck?

Hello and welcome to my blog. Refer to me as the debug ducker. The purpose of this blog is to detail my computer science journey and maybe some other stuff if possible. As of now, I am a going into senior year and ready to graduating so I’ll be documenting tons of stuff.

Now my name. It sounds silly right, but the name is based on a code debugging technique that is an coding industry practice.

The basics are that you’ll need a rubber duck or anything inanimate, and when you run into a code problem you need to debug try explaining what the code does to your duck, tell it what programs you’re running within the code, and the purpose of the code. The idea is that when you explain and go over the code with the duck, it’s supposed to help you catch what’s wrong as you explain it.

I used to do this back in high school and found it helpful. I remember my other peers doing the same thing, and they found it helpful as well. Though I haven’t used it as I progress my programming career, the technique stuck with me. Mostly because it sounds silly talking to a rubber duck but don’t knock it till you try it. So whenever you encounter a coding problem, talk to a rubber duck or any inanimate object about it and see if you can catch any errors.

From the blog CS@Worcester – Debug Duck by debugducker and used with permission of the author. All other rights reserved by the author.

I’m excited to kick off this blog as part of my journey through Computer Science. Throughout the semester, I’ll be posting regularly as part of assignments from my professor. These posts will cover a variety of topics, from programming projects and tech insights to reflections on my learning process.

Whether you’re also in the field or just curious about tech, feel free to follow along! I look forward to sharing my experiences and growing through these discussions.

Stay tuned for more!

From the blog CS@Worcester – Coder's First Steps by amoulton2 and used with permission of the author. All other rights reserved by the author.