Never had a blog before, so I'm not really sure how to start this. Here goes nothing!
Coming into 3081W, I was a bit nervous. Writing anything had never really been my strong suit. Syntactically, I was alright, but I was never very good at forming a cohesive argument or paper as a whole. Luckily, it seems like we will be writing a lot about Computer Science and 3081W related topics, so hopefully it won't be too bad. Some of the topics for 3081W are the Intended Learning Outcomes, of which some I know fairly well and a couple that I don't.
First off, the good news, the things I already know fairly well coming into the class. Writing effective comments is always something that I felt was an important part of programming, and is something that is frequently overlooked, or left to the end to be rushed through. This is because nearly everything we have done so far is just individually, and we know how it works, so we don't need to comment it that well. But, in the real world, whole teams of people will be working on one program. If that program is poorly commented, nobody will know how that program works, and will be unable to do anything to it or debug it if something goes wrong. Clear, concise comments allow everyone to under stand how your program works, I feel that I am pretty good at writing clear comments because nearly every programming class I have had has pushed it on me, so I started to do it. The more and more I did it, the more I was able to understand precisely how and why my program worked. So that, even after detailed comments weren't required, I still found myself doing them just because it helped me understand everything so much more.
However, there are a couple things I don't know and would love to learn much more about in 3081W. They are some tools for automation and documentation generators. These are tools that I have never really used in my Csci life, but are things that would be incredibly useful for me to know. Automation in particular is something that I really hope the class teaches me more about. Before, anything in the past I made, once it works, it was done. Turned in, and left alone. Nothing more had to be done with them. Automation was something that I never even thought about, but the more I think about things I will code in the future, it is something that is becoming more and more important, and my desire to learn about it is growing. Ideally, this class will give me a great introduction to it, and that I may learn more about it in the future.
Documentation is also something that has never been required of me to use so far for anything I have coded. For little things that I have done though, it isn't necessary. But, in the future, with bigger projects and more and more people working on things, documentation is going to be more important, and in greater volume. Something that could generate the documentation for me, is a tool that would be critically helpful for the rest of my life, and is another thing that I hope this class can introduce me too and dip my toe into the subject.
3081 should be a fun class, with a wide variety of things that will be done, and a lot of helpful things will be taught to me. Hopefully, I will be able to make use of these things to make me a better programmer.