o-ni

o-ni

Tuesday, September 20, 2011

i'm not at all sure what i'm 'good' at, but loops and understandable code seem fairly easy.

i tend to get how to make my loops do what i want them to. it's the functions they use that can be a problem... (like fprintf) I don't usually have problems with the logic, just the occasional one off error. i don't tend to have trouble with this so i guess i know it.

Making my code understandable shouldn't be too hard ether, i just need the comments to become a habit. this isn't hard. i'm doing it already. ...though it does get cluttered occasionally.

i need to get better with hierarchy, the overall design of the code. just viewing the code as a whole and planning it out from the start.

i'm okay with tests i guess, but have no clue about debuggers. my only experience with debuggers is the bomb lab, and i really doubt i could ever use one in a real life situation. this is one thing i need to get out of this class.

4 comments:

Unknown said...

You mention writing clear code and designing a useful and easy to understand class hierarchy in your code. It appears from your writing that you view these as two separate entities, when, infact, they are the same process. Writing clear code is applicable on a lower level, but the thing that will have the biggest impact on the readability of your code is your class hierarchy.

Devyn Coveyou

Ian Henckel said...

Yes. Debuggers are your friend; don't be intimidated. Also, man pages and Google for things like fprintf. Having a clear structure in mind before diving into details like that helps you from getting too disorganized.

Christopher Jonathan said...

I'm agree that comments are necessary for making an understandable code. But there are many other things that can make your code more understandable. For example, you should write your variable name as a simplified term of the term. Not just use a, b, or n.

Christopher Jonathan

Unknown said...

The overall hierarchy of the code is one thing I've struggled with as well. I'd agree that planning out the code from the start will be very helpful, but also having a clear view of what the program needs to do. You need to be able to change the program around, due to changing requirements, without losing the overall hierarchy and style of the code.

-Will Myott