Worcester State University Computer Science Department
- The Clean Coder (Week 1)
- Reflection (Week 1)
- Week 1 Capstone
- The Clean Coder: Chapters 1 & 2
- Spring 2017 Introduction
- CS 448 Intro
- Welcome back to more required blogs!!
- Clean Coder Chapters 1+2 Week 1
- Professional Team
- The Clean Coder, Chapter 1 and 2 (Week 1)
- Week1: Introduction
- A Test Post for Capstone
- Clean Code – Chapter 1 and 2 (Week 1)
All posts syndicated from other blogs are the property the original author, are subject to the copyright and licensing terms of that blog, and are used here with permission of the author.
All posts original to this blog are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Author Archives: Trevor
This week I spent most of my time figuring out what was left to finish in our eutester repository. I also used a lot of screenshots from github for my powerpoint presentation. I worked with Nate, Coady, and Marcos to put together our final project. We all put together screenshots and code samples from the […] Continue reading
This week I tried to download a fresh repository and none of my credentials worked. I have been unable to access the new repo to make further changes, so I’m not sure if I will be able to make anymore pushes by the end of the semester. My group has managed to get a decent […] Continue reading
Today I continued working on the eutester directory. I made some changes to the machine.py file and I’m looking at a few others at the moment. The good news is that we are continuing to make progress on the repository and hopefully it will be finished in another week or so. The bad news is […] Continue reading
At the end of the last class, we decided to use the built in issue tracker for github to track our progress and also to make sure no two people are working on the same project at the same time. This way, each person can choose which file or which directory they would like to […] Continue reading
I just submitted my first patch of code! It only contained minor code changes including comments and moving code to a function instead of leaving it out in the open, however it seemed to help significantly. I used a short shell script written by Nate Doe to help me out in linking my local repository […] Continue reading
This week, I was actually able to not only add some documentation to the eutester code, but I actually made some small code changes. There were a few existing comments in the code that basically said “This code block needs to be moved into a function at some point,” so I went ahead and created […] Continue reading
This week was more looking through code and understanding what is going on than anything else. After we learned about the paramiko and boto modules that we needed to run the Python code, a lot of the code made more sense. We all want to have a pretty good grasp on the code before we […] Continue reading