This week we discussed design smells (which I find endlessly amusing from a name standpoint), as well as the concept of design patterns. As a whole, design patterns are something that I had never thought of before now, though it makes perfect sense in retrospect. Programmers often run into the same kinds of problems or requirements for a project, so it makes perfect sense that we would have a set of designs that help to alleviate some of the problems surrounding them. I've always been one to writer code from scratch, or look up how to set something up in a basic sense, but these more abstract concepts aren't something I had put much thought or research into. The article I've chosen to read for this week is "The Problem with Patterns" from A List Apart ,which is a blog that specializes in having many writers from the Computer Science industry comment on various issues and topics. I figured that it would be a good idea to look at some of the problems with patte...
Hello I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn't null, and it won't take more than the inventory has). I think I really came into my own near the end of my time in this class, I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn't say at the start. Though if I had to pinpoint something that didn't work very well, I definitely ...
Hello! With the semester wrapping up pretty quickly, and our last homework assignment being to design an in-class assignment, I've been doing some brushing up on JUnit testing. Specifically, assertions, which are the crux of how JUnit tests work, by telling a given test what qualifies as a pass or fail. The assignment me and my groupmates designed revolved around the use of various different kinds of assertions, ones that we didn't cover heavily in class. As such, this week my blog of choice to read revolves around, what else, JUnit testing. Specifically, the article comes from Medium, who I've looked at before, and who seem to be quite the useful resource on covering both broad and specific computer science topics. I wanted to take a look at this specific article, mostly because I wanted to see some of the other topics involved with JUnit that we didn't cover in class. I intend on running Linux on my main PC once the semester ends, and seeing how to install JUnit o...
Comments
Post a Comment