blog_01

I think I know this topic better than others.

Writing Effective Comments

In 1902, I learned Java. When I wrote source code for the first time, I really hated writing comments. Because I thought it was wasting my time. Sometimes I got errors because I wrote / instead of //. However, after getting used to it, I changed my mind. I didn't know when I wrote 20~30 lines source code, but After half semester, especially after learning inheritance, I realized how comments help to organize source code and make me to read source code easily. When I wrote game sour code named ship war, I made a bunch of functions and it was huge source code I ever made. I felt like I should organize all these functions before I get lost. So, I started writing simple comments for each functions. Whenever I needed to check previous function I made, I simply checked the comment and it was really helpful. Although I had to delete or reduce some comments since I wrote so many things, it saved my time.

I know a little bit, but it makes me confused all the time.

Debuggers

When I took csci 2021, one lab asked about debugging. I think it was bomb lab. I couldn't understand what professor or ta said, but I tried to solve this lab problem. It was so confused. I'm still confusing about debugging... One of my friends is working as a hardware programmer. I don't know this is right term, but I think it will be related to debugging. He said there are many computer programmers working with software programming, but few people is working with hardware programming, so many companies are looking for hardware programmer. That's why I should know more about debuggers.