Monthly Archives: January 2017

The Clean Coder Chapters 1 & 2 and Week 1

The Clean Coder, Chapters 1 & 2
After reading the first 2 chapters I felt like I had read my
own experiences over the past twenty something years. I wasn’t a programmer or
in anything to do with computers, but the more I read and learn about this field
the more I find that even though I was doing something different, a lot of the same
issues happen no matter where you are.
In the first chapter on professionalism he talks about how
it is easier to be a nonprofessional because they don’t have to take
responsibility for the job they do. That got me to thinking about the term. No
matter what job or jobs I have had I always tried to do them as a professional.
I think the term work ethic could be used to describe professionalism as well.
You get out what you put in. I felt like I had been in similar situations as I
read the chapter. He seemed to go through something everyone must go through at
some point in life. I enjoyed how he learned from his errors and passed wisdom
on. The lessons learned from releasing the product without properly testing and
it went south. This was all to save face and look good because it went out on time,
but then the backfire. Though you think you are saving time, in the end you
lose time and man hours when if it had of been done right the first time a lot
could be prevented.
I like his take on the do no harm function as well. We can’t
be perfect, but we must be responsible for our imperfections and should always
be trying to get our error rate approaching zero and expect QA to find nothing
wrong. If that is the thought process you should genuinely be surprised when
they do find a flaw. I have been in the situation where I half assed something
to get it done on time and was not surprised in the least when it failed.
Wasted time and hours when I should have just done it right the first time.
I really felt like his work ethic and knowing your field hit
the nail on the head as well. They gave me something to try and think about. I
like the time breakdown. It humbled me actually when he was talking about the
first 40 are for the employer and 20 aside for me. I had never thought of it
that way and it humbled me. He set up some very realistic ideas on how to
utilize time. As far as knowing the field, I feel like I have a lot to do. I
know I am just getting started, but I didn’t realize just how much there is to
just know for the basics. I picked up a copy of the gang of four design
patterns books to increase my learning on that end and plan on just plucking
away each day to increase my chops.
Overall I gained a great deal from chapter one and plan on
reading it again. I wish I had come across this sooner.
Chapter 2 and saying no brought back many memories as well.
I think a lot of people in general have issues with saying no and want to just
get along and cause no waves. I am one of those, well was. I do not like to say
no because it is uncomfortable for sure, but that was because of the way that I
said no. I usually offended someone because I didn’t think before I spoke. I
have changed. He makes some great points on how to and not to approach
situations. His role playing scenarios were ones I have been a part of myself
to some degree. I was one of those people that used to say I’ll try and had
never thought boss would think of that as a yes I can get it done on time. It
makes sense though because I’ll try is like beating around the bush.  Overall there were a lot of good points that
can be used no matter where or what job you are doing. I am sure that once I
get into the field that I will be practicing my version of saying no and this
book will come to mind.
Week 1 learning
I am still trying to process everything that I have gone
over this week and am still in the process of going over it. The first couple
weeks of the semester are the hardest for me. I try to make a schedule of my
time so I can manage everything. I am excited for this one though as it is my
last undergrad semester and a long time coming. I have been going through some
Angular 2 tutorials to get a grasp on how it works, and using the node package
manager and other tools. I think it is going to be a lot of fun to learn and
use and I hope to become proficient with it.
The Open MRS project is overwhelming to me so far, but that
is I guess because I am just getting into what it is all about. I tried the
demo and like the functionality and can’t wait to get my hands dirty. I think
it is great that so many folks are collaborating on this records system that
can help so many people around the globe. I am eager to get started in this
journey and hope that whatever we do this semester has an impact in the years
to come. I know I am going to have a lot of challenges, but I welcome them with
open arms.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

The Clean Coder Chapters 1 & 2 and Week 1

The Clean Coder, Chapters 1 & 2
After reading the first 2 chapters I felt like I had read my
own experiences over the past twenty something years. I wasn’t a programmer or
in anything to do with computers, but the more I read and learn about this field
the more I find that even though I was doing something different, a lot of the same
issues happen no matter where you are.
In the first chapter on professionalism he talks about how
it is easier to be a nonprofessional because they don’t have to take
responsibility for the job they do. That got me to thinking about the term. No
matter what job or jobs I have had I always tried to do them as a professional.
I think the term work ethic could be used to describe professionalism as well.
You get out what you put in. I felt like I had been in similar situations as I
read the chapter. He seemed to go through something everyone must go through at
some point in life. I enjoyed how he learned from his errors and passed wisdom
on. The lessons learned from releasing the product without properly testing and
it went south. This was all to save face and look good because it went out on time,
but then the backfire. Though you think you are saving time, in the end you
lose time and man hours when if it had of been done right the first time a lot
could be prevented.
I like his take on the do no harm function as well. We can’t
be perfect, but we must be responsible for our imperfections and should always
be trying to get our error rate approaching zero and expect QA to find nothing
wrong. If that is the thought process you should genuinely be surprised when
they do find a flaw. I have been in the situation where I half assed something
to get it done on time and was not surprised in the least when it failed.
Wasted time and hours when I should have just done it right the first time.
I really felt like his work ethic and knowing your field hit
the nail on the head as well. They gave me something to try and think about. I
like the time breakdown. It humbled me actually when he was talking about the
first 40 are for the employer and 20 aside for me. I had never thought of it
that way and it humbled me. He set up some very realistic ideas on how to
utilize time. As far as knowing the field, I feel like I have a lot to do. I
know I am just getting started, but I didn’t realize just how much there is to
just know for the basics. I picked up a copy of the gang of four design
patterns books to increase my learning on that end and plan on just plucking
away each day to increase my chops.
Overall I gained a great deal from chapter one and plan on
reading it again. I wish I had come across this sooner.
Chapter 2 and saying no brought back many memories as well.
I think a lot of people in general have issues with saying no and want to just
get along and cause no waves. I am one of those, well was. I do not like to say
no because it is uncomfortable for sure, but that was because of the way that I
said no. I usually offended someone because I didn’t think before I spoke. I
have changed. He makes some great points on how to and not to approach
situations. His role playing scenarios were ones I have been a part of myself
to some degree. I was one of those people that used to say I’ll try and had
never thought boss would think of that as a yes I can get it done on time. It
makes sense though because I’ll try is like beating around the bush.  Overall there were a lot of good points that
can be used no matter where or what job you are doing. I am sure that once I
get into the field that I will be practicing my version of saying no and this
book will come to mind.
Week 1 learning
I am still trying to process everything that I have gone
over this week and am still in the process of going over it. The first couple
weeks of the semester are the hardest for me. I try to make a schedule of my
time so I can manage everything. I am excited for this one though as it is my
last undergrad semester and a long time coming. I have been going through some
Angular 2 tutorials to get a grasp on how it works, and using the node package
manager and other tools. I think it is going to be a lot of fun to learn and
use and I hope to become proficient with it.
The Open MRS project is overwhelming to me so far, but that
is I guess because I am just getting into what it is all about. I tried the
demo and like the functionality and can’t wait to get my hands dirty. I think
it is great that so many folks are collaborating on this records system that
can help so many people around the globe. I am eager to get started in this
journey and hope that whatever we do this semester has an impact in the years
to come. I know I am going to have a lot of challenges, but I welcome them with
open arms.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

The Clean Coder Chapters 1 & 2 and Week 1

The Clean Coder, Chapters 1 & 2
After reading the first 2 chapters I felt like I had read my
own experiences over the past twenty something years. I wasn’t a programmer or
in anything to do with computers, but the more I read and learn about this field
the more I find that even though I was doing something different, a lot of the same
issues happen no matter where you are.
In the first chapter on professionalism he talks about how
it is easier to be a nonprofessional because they don’t have to take
responsibility for the job they do. That got me to thinking about the term. No
matter what job or jobs I have had I always tried to do them as a professional.
I think the term work ethic could be used to describe professionalism as well.
You get out what you put in. I felt like I had been in similar situations as I
read the chapter. He seemed to go through something everyone must go through at
some point in life. I enjoyed how he learned from his errors and passed wisdom
on. The lessons learned from releasing the product without properly testing and
it went south. This was all to save face and look good because it went out on time,
but then the backfire. Though you think you are saving time, in the end you
lose time and man hours when if it had of been done right the first time a lot
could be prevented.
I like his take on the do no harm function as well. We can’t
be perfect, but we must be responsible for our imperfections and should always
be trying to get our error rate approaching zero and expect QA to find nothing
wrong. If that is the thought process you should genuinely be surprised when
they do find a flaw. I have been in the situation where I half assed something
to get it done on time and was not surprised in the least when it failed.
Wasted time and hours when I should have just done it right the first time.
I really felt like his work ethic and knowing your field hit
the nail on the head as well. They gave me something to try and think about. I
like the time breakdown. It humbled me actually when he was talking about the
first 40 are for the employer and 20 aside for me. I had never thought of it
that way and it humbled me. He set up some very realistic ideas on how to
utilize time. As far as knowing the field, I feel like I have a lot to do. I
know I am just getting started, but I didn’t realize just how much there is to
just know for the basics. I picked up a copy of the gang of four design
patterns books to increase my learning on that end and plan on just plucking
away each day to increase my chops.
Overall I gained a great deal from chapter one and plan on
reading it again. I wish I had come across this sooner.
Chapter 2 and saying no brought back many memories as well.
I think a lot of people in general have issues with saying no and want to just
get along and cause no waves. I am one of those, well was. I do not like to say
no because it is uncomfortable for sure, but that was because of the way that I
said no. I usually offended someone because I didn’t think before I spoke. I
have changed. He makes some great points on how to and not to approach
situations. His role playing scenarios were ones I have been a part of myself
to some degree. I was one of those people that used to say I’ll try and had
never thought boss would think of that as a yes I can get it done on time. It
makes sense though because I’ll try is like beating around the bush.  Overall there were a lot of good points that
can be used no matter where or what job you are doing. I am sure that once I
get into the field that I will be practicing my version of saying no and this
book will come to mind.
Week 1 learning
I am still trying to process everything that I have gone
over this week and am still in the process of going over it. The first couple
weeks of the semester are the hardest for me. I try to make a schedule of my
time so I can manage everything. I am excited for this one though as it is my
last undergrad semester and a long time coming. I have been going through some
Angular 2 tutorials to get a grasp on how it works, and using the node package
manager and other tools. I think it is going to be a lot of fun to learn and
use and I hope to become proficient with it.
The Open MRS project is overwhelming to me so far, but that
is I guess because I am just getting into what it is all about. I tried the
demo and like the functionality and can’t wait to get my hands dirty. I think
it is great that so many folks are collaborating on this records system that
can help so many people around the globe. I am eager to get started in this
journey and hope that whatever we do this semester has an impact in the years
to come. I know I am going to have a lot of challenges, but I welcome them with
open arms.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

The Clean Coder Chapters 1 & 2 and Week 1

The Clean Coder, Chapters 1 & 2
After reading the first 2 chapters I felt like I had read my own experiences over the past twenty something years. I wasn’t a programmer or in anything to do with computers, but the more I read and learn about this field the more I find that even though I was doing something different, a lot of the same issues happen no matter where you are.
In the first chapter on professionalism he talks about how it is easier to be a nonprofessional because they don’t have to take responsibility for the job they do. That got me to thinking about the term. No matter what job or jobs I have had I always tried to do them as a professional. I think the term work ethic could be used to describe professionalism as well. You get out what you put in. I felt like I had been in similar situations as I read the chapter. He seemed to go through something everyone must go through at some point in life. I enjoyed how he learned from his errors and passed wisdom on. The lessons learned from releasing the product without properly testing and it went south. This was all to save face and look good because it went out on time, but then the backfire. Though you think you are saving time, in the end you lose time and man hours when if it had of been done right the first time a lot could be prevented.
I like his take on the do no harm function as well. We can’t be perfect, but we must be responsible for our imperfections and should always be trying to get our error rate approaching zero and expect QA to find nothing wrong. If that is the thought process you should genuinely be surprised when they do find a flaw. I have been in the situation where I half assed something to get it done on time and was not surprised in the least when it failed. Wasted time and hours when I should have just done it right the first time.
I really felt like his work ethic and knowing your field hit the nail on the head as well. They gave me something to try and think about. I like the time breakdown. It humbled me actually when he was talking about the first 40 are for the employer and 20 aside for me. I had never thought of it that way and it humbled me. He set up some very realistic ideas on how to utilize time. As far as knowing the field, I feel like I have a lot to do. I know I am just getting started, but I didn’t realize just how much there is to just know for the basics. I picked up a copy of the gang of four design patterns books to increase my learning on that end and plan on just plucking away each day to increase my chops.
Overall I gained a great deal from chapter one and plan on reading it again. I wish I had come across this sooner.
Chapter 2 and saying no brought back many memories as well. I think a lot of people in general have issues with saying no and want to just get along and cause no waves. I am one of those, well was. I do not like to say no because it is uncomfortable for sure, but that was because of the way that I said no. I usually offended someone because I didn’t think before I spoke. I have changed. He makes some great points on how to and not to approach situations. His role playing scenarios were ones I have been a part of myself to some degree. I was one of those people that used to say I’ll try and had never thought boss would think of that as a yes I can get it done on time. It makes sense though because I’ll try is like beating around the bush.  Overall there were a lot of good points that can be used no matter where or what job you are doing. I am sure that once I get into the field that I will be practicing my version of saying no and this book will come to mind.
Week 1 learning
I am still trying to process everything that I have gone over this week and am still in the process of going over it. The first couple weeks of the semester are the hardest for me. I try to make a schedule of my time so I can manage everything. I am excited for this one though as it is my last undergrad semester and a long time coming. I have been going through some Angular 2 tutorials to get a grasp on how it works, and using the node package manager and other tools. I think it is going to be a lot of fun to learn and use and I hope to become proficient with it.
The Open MRS project is overwhelming to me so far, but that is I guess because I am just getting into what it is all about. I tried the demo and like the functionality and can’t wait to get my hands dirty. I think it is great that so many folks are collaborating on this records system that can help so many people around the globe. I am eager to get started in this journey and hope that whatever we do this semester has an impact in the years to come. I know I am going to have a lot of challenges, but I welcome them with open arms.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 1: The Clean Coder, Ch. 1&2

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Week 1 Reflection

This is the beginning of the software development capstone. We started the semester by forming the scrum teams we will be working in for the remainder of the semester. the class has been divided into 4 Scrum teams each with about 6 members.

 

In these teams we will be working on the open source software OpenMRS. OpenMRS is an open source medical record system that aims to provide developing countries around the world with a reliable tool for use in medical facilities with out the high cost associated with commercial options. We will be concentrating on the AMPATH project.

 

This week most of my time has been spent looking in to Angular 2. Angular 2 is a JavaScript framework maintained by Google. We will be using this throughout the semester as we work on the AMPATH project.

 

I believe this will be a valuable experience. Throughout the past three and a half years, all of the programs we have worked on in school have been very small in size. In contrast, OpenMRS is a much larger and will offer a good opportunity to experience having to jump into a large project, become familiar, and start developing.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Database Fundamentals: Core Concepts

NOTES FROM Database Fundamentals: Core Concepts Adam Wilbert 1. Understanding Database Storage Models What are databases? Databases are at the core of our modern technology and it’s important to understand exactly what they are and the benefits that they bring … Continue reading →

From the blog CS@Worcester – thewisedevloper by thewisedeveloper and used with permission of the author. All other rights reserved by the author.

Week 1: Reflections on Learning and Work Products

Just finished week 1 of my senior year capstone.  This week we started off by getting an overview of what the class is.  We learned about SCRUM and actually did some hands-on learning with that.  We were given a theoretical problem and then each took a role as either the customer, developer, or monitor in order to solve the problem.  This was interesting to me and I learned a lot, especially because I had never even heard of SCRUM before.  I really enjoy doing hands-on activities rather then listening to a lecture.

The big thing accomplished this week was being put into our groups that we will be working in all semester long.  Although the process of picking teams was a little shaky, it all worked out in the end.  We informed that we will be writing in Angular this semester.  I have never used Angular before, so I am beginning to work through some tutorials to get a grip on how the language works.  The only thing we have done as far as the actual work we will be doing is we were given the information to start looking through the openMRS project.  We were told we will be focusing on the AMPATH project specifically, so I have been reading up on that.  AMPATH delivers health services, conducts health research, and develops leaders in health care for both North America and Africa (mainly Kenya).  I am very excited to work on the AMPATH project, because it is for a good cause and it is a project that helps millions of less fortunate people who deserve the proper health care.

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

Reflection on Week 1

Our objectives this week was to learn how slack works, and to learn about openMRS and AMPATH. The OpenMRS community is a worldwide network of volunteers with a wide variety of backgrounds. Its goal is to build the worlds largest and most flexible tech platform to support the delivery of health care in places all around the world. I did a quick demo of the software and at first glance i had no idea what was going on, but after playing around with it for a bit i not have a basic understanding about how it works. Slack is a useful tool that we will use in communicating with our team. I played around with it and found out it has a lot in common with the “discord” application. The only thing it lacks is a voice speak option. AMPATH was created in response to the challenge of treating thosands of people that are HIV positive. AMPATH is expanding from an HIV focus to adress the critial need for primary healthcare in places across the world. 

I also started looking into Angular 2 and found out that it uses JavaScript and html which i have a basic understandings of.

From the blog CS@Worcester – Site Title by jonathanpaizblog and used with permission of the author. All other rights reserved by the author.

Reflection Week 1

The first week was basically just forming our teams and recognizing what we are going to be doing this semester. We were told told make slack channels for our teams and to study Open MRS, AMPATH, and angular2. We continued to share information on a joint document to help each other catch anything we might have missed. I am also trying to learn angular 2 using online tutorials. The way we ended up picking teams was kind of odd but it all ended up working out, I currently reside with Team ZOLINQ. We will be using SCRUM throughout the semester to try to keep on top of everything and I’m sure all will go well because we will follow its framework and keep communication as our priority.

From the blog CS@worcester – CS Blog by Gautam by csblogbyg and used with permission of the author. All other rights reserved by the author.