Introduction to C programming/Lectures/Introduction
 |
This page may qualify for speedy deletion because: Page, along with the course is a stub as it's no longer maintained by the author. All useful document from this page has been merged to https://en.wikiversity.org/wiki/C_Programming/Introduction. "Debugging" and"Software engineering" have been merged to https://en.wikiversity.org/wiki/Introduction_to_C_programming for later cleanup/restructure. This stub page is needed to be deleted to clean up the "C programming" course so that students won't be confused by various stub courses If you disagree or intend to fix it, and you have not contributed to it before, you may remove this notice. If you have contributed before and disagree, please explain why on the discussion page, after adding {{hangon}} to the top of the . This will alert curators and custodians to your intention, and may permit you the time to write your explanation. Before deleting check the discussion page, what links here, history (last edit), the page log, and Wikiversity:Deletions. |
What is debugging?[edit | edit source]
Debugging is searching for mistakes in your program. No one is perfect, we all make mistakes. Despite having programmed for nearly a decade, I made several errors while writing the first few programs for this class. If you're going to program, you're going to need to learn to debug. This class will teach some basic debugging techniques and common mistakes along with the rest of the material. Don't treat this as a minor part of the class - you will generally spend more time debugging a program than you will writing it.
Software engineering[edit | edit source]
Software engineering is a set of habits and practices that help to make your code easier to read and understand. The easier your code is to understand, the fewer bugs it will have, and the easier they will be to find. It will also make it easier to maintain when you find a bug or want to add a new feature 6 months from now. Trust me, you won't remember how you wrote the code, no matter how much you think you will. Its always best to get into good habits early, so the class will try and teach you how you should do things, as well as just the syntax of the language. Remember, writing good code isn't just for yourself - it helps your coworkers and anyone else who ever has to work with your code.