Camille's Cluttered Closet

 Hello!   This week marks the first week of sprint 2 proper, and as such I've been tasked with writing about my experiences with sprint 1. First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I'll have a link to the merge request at the bottom of the page. I think our group functioned pretty well during our class meetings, there isn't that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively.  I think in terms of things that didn't go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I ...

 Hello!  I've had a bit of assigned reading to do for my capstone course, ans as such, I thought it would go the way of most readings of that ilk; incredibly dry and ungodly boring. But surprisingly I had a pretty good time with Apprenticeship Patterns by Dave Hoover and Adewale Oshineye.  The text captures something that I find to be incredibly important to the process of becoming a career programmer, the ability to be flexible. Much of my time spent learning to program has consisted of how to do things, but never why or when we should do them. Sometimes it feels like I have a fairly full toolbox, but I don't have the required knowledge to apply my tools in ways they weren't explained to me in. I'll admit, this is more of a personal failing I feel, but the point still stands.  Chapter 1 and the introductory paragraphs to Chapter 4 really stood out to me the most, as Chapter 1 goes into detail about what it means to be a craftsman, and an apprentice. It highlights th...

 Hello!   I'm still Camille and this is still my blog, I guess!   CS443

 Greetings!  This week during class, among other things, we learned about semantic version numbers. As the name implies, the process of determining what kind of version goes to what kind of version number is quite complicated, and requires some level of thought, which I admittedly hadn't done before now. The MAJOR.MINOR.PATCH format for changes does seem rather useful and straightforward, but actually figuring out how to classify changing how a print command prints to the console seems like a lot of work. I always had this notion in mind that developers kind of just picked versions numbers at random, or at least sequentially, I didn't know there was an actual structure behind what appears to be a simple string of numbers. I feel like with writing these posts I have a tendency to view other blog posts that completely contradict, or speak about the shortcomings of what we learn in class. I don't mean to be a cynic, I just want to be aware of what can go wrong when using such ...

 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...

 This week in class, we discussed what goes into licensing a piece of software, along with copyright law. If I am being perfectly honest, this wasn't what I was expecting to study in this class, though it makes sense, in a way. Licensing, as I have learned, is a very important part of software development, and knowing who owns what, and defining who can do what with your code ties in pretty well to the other topics we've been discussing in class. As such, I've taken a look at an article 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've chosen the article: " Considering Open Source Licenses", which talks about one of the things most interesting (and confusing) to me in terms of licensing, Open Source Licenses. One would think that making software open source would be as simple as declaring it as such. However, in the real world, it's a little more complic...