First blog post!
Hi! I’m Camille, this is my blog I guess!
CS348 and CS343
From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.
Intro Post for CS-343
Hello, my name is Giovanni Casiano and am a senior at Worcester State University majoring in Computer Science. I am looking forward to learning as much as I can during this course.
From the blog CS@Worcester – Giovanni Casiano – Software Development by Giovanni Casiano and used with permission of the author. All other rights reserved by the author.
Software Architecture
Hello again,
My name is Anthony Cao, and I will continue to use this blog to document my education in software development and what it has to offer. I am taking another software class that will correct the way I write code, making it more efficient.
From the blog CS@Worcester – Cao's Thoughts by antcao and used with permission of the author. All other rights reserved by the author.
Introducing A Bostonians Blog
This is my blog, A Bostonians Blog. I couldn’t think of a better name than this but this blog is my personal space to share insights, experiences, and discoveries as I progress through my coursework, particularly focusing on Computer science at Worcester State University.
From the blog CS@Worcester – A Bostonians Blogs by Abdulhafeedh Sotunbo and used with permission of the author. All other rights reserved by the author.
Hello!
I’m Joanna P. and I’ll be using this blog to talk about my journey though learning computer science.
From the blog CS@Worcester – My Journey through Comp Sci by Joanna Presume and used with permission of the author. All other rights reserved by the author.
Blog Set-Up
Hello World, my name is Santiago Donadio and this is my first blog post.
I am currently taking CS348 – Software Process Management with Professor Wurst.
From the blog CS@Worcester – Programming with Santiago by Santiago Donadio and used with permission of the author. All other rights reserved by the author.
Introductory Post CS-343
This is my CS 343 Blog
From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.
Let me tell you who I am
To begin, my name is Oanh Nguyen. At this point and time, a student at the university of Worcester State. I major in computer science and minor in business administration. Another thing to add is that I’m currently taking ‘Software Constr, Des & Archit’ and many further blog will be related to this class. Which will be tagged accordingly.
While I’m not particularly great at programming, I enjoy problem solving and those moments where I succeed in getting a project done. The reason I choose to major is because there was a ‘Discrete Structure’ class I took in the past and I enjoyed it great. I wished to take a further step in that direction, although I do not know where it will take me.
It’s nice to meet you, who is reading this. Thank you.
From the blog SoftwareDiary by Oanh Nguyen and used with permission of the author. All other rights reserved by the author.
CS-343 Introduction
This blog page will be used to discuss my findings and research throughout my courses. This will be a gateway to look back on and view how much improvement I have made or even the different technologies I used previously.
From the blog CS@Worcester – Cinnamon Codes by CinnamonCodes and used with permission of the author. All other rights reserved by the author.
Testable Code Is A Skill That Should Be Learned Early
The Finale of CS448
Learning how to write tests for code has been what really made my education feel like it has come full circle. It has really provided a deeper understanding and a boost to my confidence while writing code. There has been countless times where during this course i would be kicking myself. Just wishing i had learned some things sooner, before all of the other big projects and homework assignments.
Every new computer science student comes in and starts cranking out code and programs. Over the years you are also introduced to a variety of things, one example that comes to mind is truth tables.
Before ever diving into the world of software testing, those tables, while logically making sense. Never really seemed to be fully applicable to what i was doing. For instance a program you are writing might have branches or loops with certain conditions, and you will notice the similarities regarding the true and false conditions and there outcomes.
However, this type of logic directly relates to being able to map out test cases. The following example is from a homework assignment that helps really illustrate the connection.
Once we began writing out our test cases in this fashion is where everything “clicked” in regards to past classes based on logic that i didn’t fully appreciate the value of.
With this connection also came the experiences regarding test driven development (see past blogs). While writing your first hello world program, it is quite obvious how simple it can be. It would be possible to expand upon to have testing make sense, but once someone has been exposed to creating multiple methods and classes. It is my belief that learning how to test them, even if it seems simple and silly, would go a long way.
Mocks and stubs could be slightly tricky for a new student of course, but learning how to just make a stub could go a long way.
Another portion i wish i had picked up sooner is called a define-use path. Being able to have a diagram directly depict the flow of a program can help so much while working through the thought process while developing and testing.
In conclusion learning and understanding how software testing works boosted my confidence in programming exponentially. Even while learning JavaScript on the fly having zero experience i found myself needing to use the same principals i had been taught through testing. In fact, i would jokingly argue, TDD felt backwards because we were taught how to program backwards! Or maybe that is the point?
From the blog Mikes CS Journey by Michael St. Germain and used with permission of the author. All other rights reserved by the author.