0
I lied in last week's blog entry, this is my last blog class-related blog entry. We had the test on Friday, it wasn't too bad. In fact, I think the only questions I made mistakes on were the UML questions. I didn't even think about studying UML specs, I studied all the quizzes, all the lecture code, and re-read the notes, but I completely blanked on the UML stuff. I guess I should've helped more in the UML Diagram part of the project. Do subclasses need the diamonds??? Arrowheads... Who knows, maybe I got those questions right, it's interesting how the only way to know is to see the TA. Not necessarily a bad thing, but a bit of a change from the norm.
About UML, I've actually heard that UML has a bad reputation in the "industry". Of course, this was only anecdotal, but I've heard of interviews where they didn't like the interviewee bringing up UML. Apparently there are programs that write your code for you based on UML. And interviewers think that is bad.
But I'm getting off track... summer here we come! Now that I'm done with the class I can finally celebrate summer break. Too bad I have 10 days instead of 3 months. Oh well, the 6 hours of upper-division CS credit I earned is well worth it.
CS 373 :: Software Engineering was quite a class. Definitely not your ordinary CS undergrad course. The quizzes were pretty tough, considering we had one every class. I find it amazing that 65% of Downing's students receive a B or A considering 20% of the grade is from these quizzes. The tests weren't bad. The first 2 projects were fine, if not a bit overwhelming at first. But projects 3-5 were something else entirely. I can't remember EVAR working that long on single projects. There was one week with two 8-hour sessions during the week and one 8-hour session on that weekend. And that is with all 5 group members working continuously.
The fact that I'm typing my last extra-credit blog entry on a Sunday night after the last test will tell you something. This isn't your typical CS homework-project-test course.
Bottom line, I learned A BUNCH, probably the most I've learned in any CS course. The knowledge I have about Python (and to a lesser degree Haskell) would sufficiently fill a 3 hour course. Therefore, I highly recommend taking CS 373 with Downing (in case any prospective students Bing'ed the course and found this blog entry). Get ready for an intense course, but know that earning an A isn't out of the question as long as you keep at it.
And just so we're clear, the title of this entry should be hummed as a trumpet sound, like Miles Davis in the Porgy and Bess soundtrack, not sung like Sublime's version.
When I press submit I'll get some points through my new (e32) Points Per Blog ibEconomy plug-in. Go me.
About UML, I've actually heard that UML has a bad reputation in the "industry". Of course, this was only anecdotal, but I've heard of interviews where they didn't like the interviewee bringing up UML. Apparently there are programs that write your code for you based on UML. And interviewers think that is bad.
But I'm getting off track... summer here we come! Now that I'm done with the class I can finally celebrate summer break. Too bad I have 10 days instead of 3 months. Oh well, the 6 hours of upper-division CS credit I earned is well worth it.
CS 373 :: Software Engineering was quite a class. Definitely not your ordinary CS undergrad course. The quizzes were pretty tough, considering we had one every class. I find it amazing that 65% of Downing's students receive a B or A considering 20% of the grade is from these quizzes. The tests weren't bad. The first 2 projects were fine, if not a bit overwhelming at first. But projects 3-5 were something else entirely. I can't remember EVAR working that long on single projects. There was one week with two 8-hour sessions during the week and one 8-hour session on that weekend. And that is with all 5 group members working continuously.
The fact that I'm typing my last extra-credit blog entry on a Sunday night after the last test will tell you something. This isn't your typical CS homework-project-test course.
Bottom line, I learned A BUNCH, probably the most I've learned in any CS course. The knowledge I have about Python (and to a lesser degree Haskell) would sufficiently fill a 3 hour course. Therefore, I highly recommend taking CS 373 with Downing (in case any prospective students Bing'ed the course and found this blog entry). Get ready for an intense course, but know that earning an A isn't out of the question as long as you keep at it.
And just so we're clear, the title of this entry should be hummed as a trumpet sound, like Miles Davis in the Porgy and Bess soundtrack, not sung like Sublime's version.
When I press submit I'll get some points through my new (e32) Points Per Blog ibEconomy plug-in. Go me.
