Wednesday, August 31, 2011

FizzBuzz



Creating this program took me 5:36. I've noticed that I had a hard time imagining the output in my head. I spent too much time making sure my formatting and indents were correct. I actually finished writing the program at around 3:00, but it was wrong when I checked. Before I started writing again, I thought about how I should implement it by writing it on paper. It helps me to think. Before getting into the habit of stopping, I spent a lot of time thinking about how my method would work if I implemented it a certain way and not writing it down. I traced it in my head and I never got to do any actual coding or whenever I did, it was haphazardly.

Frankly, I have not learned anything new from this assignment or this class relating to software engineering. What I've learned so far is how to make myself look good instead of making good programs, which is pretty important, but it's not something that I believe I should spend class time on. Looking at the readings,specifically those related to fizzbuzz, I am lead to believe that being able to write a simple working program within a certain time limit gauges the quality of programmers. Doing this fizzbuzz exercise tells me that I am not cut out to be a software engineer how I am right now.

1 comments:

briceorbryce said...

I think the JUnit thing is pretty interesting. I remember in 111, 211, and 311 I ALWAYS had to run the program and interact with it in order to test the code. It got really irritating and repetitive after the 5th time or so.

Post a Comment