cSharpProject.Dispose()

Today we presented our C# projects in class. It was nice to see the various ways my classmates decided to solve the problems at hand. Each project was impressive and the different approaches allowed me to appreciate and take note of the alternate ways of solving problems.

During the course of the project, I found that I needed to revisit the uml diagrams created when designing the application. Throughout the design process I made adjustments to my classes and to the database design. To ensure I solved the problem according to the project's specifications, I made minor changes after coding and constantly referred to the requirements for the project. In summary, analysing the problem I needed to solve before designing and coding my application, allowed me to deliver a working system within a relatively short period of time while staying in scope.

System Development Life Cycle

We are about to enter our third week of C# and are plugging away at the concept of creating software from start to end. It is nice to see that we are being taught the programming language and the process of documenting each step of the development process hand in hand. I am appreciating what we have learned and looking forward to what we will be learning.

Can you see sharply?

I know, I try to be clever with my words; sometimes it is good and sometimes... not so much. I have been away from object oriented programming for the last 2 years, and I have to tell you it is not pretty. I am wrapping my head around developing within strict guidelines and I am happy about it; about as happy as anyone can be that has spent time swimming in a pool of non object oriented programming after being programmed (clever eh?) to program object orientatedly. I should mention that I also like to make up words, it helps to fuel my creativity.
Anyhoo it has been a week, my mind is almost out of it's bad coding habits.

More to come later....