This week’s learning reflections will be short as we really didn’t
do much. We finished our first team sprint and had our reflections meeting as
well as doing our daily scrums. I feel like I am finally getting used to the
whole Scrum thing and like it and believe as a team we are utilizing it well
and in the long run it will only help us get better as a team. I think that we
have had positive results so far and look forward to what the future holds for
us. I think we have good continuity and will learn a lot from each other and
about the development process this semester.

I have to say that I enjoyed these two chapters, I think in part because they are on stuff that I need work with and don’t have too much experience in them, well the test driven development (TDD) anyways. I find it interesting reading about coding experience from someone who has been coding since punch cards and to see how much the skill has evolved. I used to have a Commodore 64 and was familiar with the Apple 2 machines and programming in Basic. It is awe inspiring to see how much the languages have grown and power of systems increase since then. Well back on subject and TDD. I do not have really any experience outside of some TDD examples I have done for class and reading about it, but I can see how it can be great. I think it may be hard for me to get used to as though it makes sense to me in theory, putting it to work in practice is another story. I like the 3 laws of TDD and imagine it is going to take some getting used to writing tests before writing any actual code, and sticking to it. I can see the benefits for sure. The thing that I like is that it seems to force you to write smaller parts of the whole and in the end you end up with not only a bunch of smaller modules, but you also have the tests to go along with them and the confidence that what you have will work. The other plus is that when you add code or update, you are only doing it to smaller parts of the whole so it is easier to track the bugs when something does break I would think. It is crazy that his FitNesse program takes only 90 seconds to run and has 90% test coverage with only 17 bugs in his list. That there seems to me like proof in the pudding on TDD. As I said before, this is something I will have to work on and gain confidence with and take his advice on courage. I really like the statement, “When you have a suite of tests that you trust, then you lose all fear of making changes.” For now, I will just work on following the three laws of TDD.

This chapter’s subject in my opinion is so very important, practicing. He hits the nail on the head here. You can’t better if you aren’t practicing your art. I certainly need more of it and don’t do enough, but I am working on it and I plan on using some of the techniques in this chapter to help with that. I enjoyed how he puts it together with martial arts terms. I will be working on the Katas that he linked and other items. I don’t really think that I can write a whole lot about practicing as I think it speaks for itself. Without practice you get stale and lose your touch. I really like some of his ideas on picking a new language to practice with and finding an open source project to work with. I believe that all of these ideas will help to make me a better programmer as long as I put them to work and keep up what I have been doing. I am passionate about this and sometimes feel like I am behind the curve, but I just keep plugging away and learning more every day.

Clean Coder Chapters 5 and 6

Chapter 5:

I have to say that I enjoyed these two chapters, I think in
part because they are on stuff that I need work with and don’t have too much
experience in them, well the test driven development (TDD) anyways. I find it
interesting reading about coding experience from someone who has been coding
since punch cards and to see how much the skill has evolved. I used to have a
Commodore 64 and was familiar with the Apple 2 machines and programming in
Basic. It is awe inspiring to see how much the languages have grown and power
of systems increase since then. Well back on subject and TDD. I do not have
really any experience outside of some TDD examples I have done for class and
reading about it, but I can see how it can be great. I think it may be hard for
me to get used to as though it makes sense to me in theory, putting it to work
in practice is another story. I like the 3 laws of TDD and imagine it is going
to take some getting used to writing tests before writing any actual code, and
sticking to it. I can see the benefits for sure. The thing that I like is that
it seems to force you to write smaller parts of the whole and in the end you
end up with not only a bunch of smaller modules, but you also have the tests to
go along with them and the confidence that what you have will work. The other
plus is that when you add code or update, you are only doing it to smaller
parts of the whole so it is easier to track the bugs when something does break
I would think. It is crazy that his FitNesse program takes only 90 seconds to
run and has 90% test coverage with only 17 bugs in his list. That there seems
to me like proof in the pudding on TDD. As I said before, this is something I
will have to work on and gain confidence with and take his advice on courage. I
really like the statement, “When you have a suite of tests that you trust, then
you lose all fear of making changes.” For now, I will just work on following
the three laws of TDD.

Chapter 6:

This chapter’s subject in my opinion is so very important,
practicing. He hits the nail on the head here. You can’t better if you aren’t
practicing your art. I certainly need more of it and don’t do enough, but I am
working on it and I plan on using some of the techniques in this chapter to
help with that. I enjoyed how he puts it together with martial arts terms. I
will be working on the Katas that he linked and other items. I don’t really
think that I can write a whole lot about practicing as I think it speaks for
itself. Without practice you get stale and lose your touch. I really like some
of his ideas on picking a new language to practice with and finding an open
source project to work with. I believe that all of these ideas will help to
make me a better programmer as long as I put them to work and keep up what I
have been doing. I am passionate about this and sometimes feel like I am behind
the curve, but I just keep plugging away and learning more every day.

Clean Coder Chapters 5 and 6

Chapter 5:

I have to say that I enjoyed these two chapters, I think in
part because they are on stuff that I need work with and don’t have too much
experience in them, well the test driven development (TDD) anyways. I find it
interesting reading about coding experience from someone who has been coding
since punch cards and to see how much the skill has evolved. I used to have a
Commodore 64 and was familiar with the Apple 2 machines and programming in
Basic. It is awe inspiring to see how much the languages have grown and power
of systems increase since then. Well back on subject and TDD. I do not have
really any experience outside of some TDD examples I have done for class and
reading about it, but I can see how it can be great. I think it may be hard for
me to get used to as though it makes sense to me in theory, putting it to work
in practice is another story. I like the 3 laws of TDD and imagine it is going
to take some getting used to writing tests before writing any actual code, and
sticking to it. I can see the benefits for sure. The thing that I like is that
it seems to force you to write smaller parts of the whole and in the end you
end up with not only a bunch of smaller modules, but you also have the tests to
go along with them and the confidence that what you have will work. The other
plus is that when you add code or update, you are only doing it to smaller
parts of the whole so it is easier to track the bugs when something does break
I would think. It is crazy that his FitNesse program takes only 90 seconds to
run and has 90% test coverage with only 17 bugs in his list. That there seems
to me like proof in the pudding on TDD. As I said before, this is something I
will have to work on and gain confidence with and take his advice on courage. I
really like the statement, “When you have a suite of tests that you trust, then
you lose all fear of making changes.” For now, I will just work on following
the three laws of TDD.

Chapter 6:

This chapter’s subject in my opinion is so very important,
practicing. He hits the nail on the head here. You can’t better if you aren’t
practicing your art. I certainly need more of it and don’t do enough, but I am
working on it and I plan on using some of the techniques in this chapter to
help with that. I enjoyed how he puts it together with martial arts terms. I
will be working on the Katas that he linked and other items. I don’t really
think that I can write a whole lot about practicing as I think it speaks for
itself. Without practice you get stale and lose your touch. I really like some
of his ideas on picking a new language to practice with and finding an open
source project to work with. I believe that all of these ideas will help to
make me a better programmer as long as I put them to work and keep up what I
have been doing. I am passionate about this and sometimes feel like I am behind
the curve, but I just keep plugging away and learning more every day.

Clean Coder Chapters 5 and 6

Chapter 5:

I have to say that I enjoyed these two chapters, I think in
part because they are on stuff that I need work with and don’t have too much
experience in them, well the test driven development (TDD) anyways. I find it
interesting reading about coding experience from someone who has been coding
since punch cards and to see how much the skill has evolved. I used to have a
Commodore 64 and was familiar with the Apple 2 machines and programming in
Basic. It is awe inspiring to see how much the languages have grown and power
of systems increase since then. Well back on subject and TDD. I do not have
really any experience outside of some TDD examples I have done for class and
reading about it, but I can see how it can be great. I think it may be hard for
me to get used to as though it makes sense to me in theory, putting it to work
in practice is another story. I like the 3 laws of TDD and imagine it is going
to take some getting used to writing tests before writing any actual code, and
sticking to it. I can see the benefits for sure. The thing that I like is that
it seems to force you to write smaller parts of the whole and in the end you
end up with not only a bunch of smaller modules, but you also have the tests to
go along with them and the confidence that what you have will work. The other
plus is that when you add code or update, you are only doing it to smaller
parts of the whole so it is easier to track the bugs when something does break
I would think. It is crazy that his FitNesse program takes only 90 seconds to
run and has 90% test coverage with only 17 bugs in his list. That there seems
to me like proof in the pudding on TDD. As I said before, this is something I
will have to work on and gain confidence with and take his advice on courage. I
really like the statement, “When you have a suite of tests that you trust, then
you lose all fear of making changes.” For now, I will just work on following
the three laws of TDD.

Chapter 6:

This chapter’s subject in my opinion is so very important,
practicing. He hits the nail on the head here. You can’t better if you aren’t
practicing your art. I certainly need more of it and don’t do enough, but I am
working on it and I plan on using some of the techniques in this chapter to
help with that. I enjoyed how he puts it together with martial arts terms. I
will be working on the Katas that he linked and other items. I don’t really
think that I can write a whole lot about practicing as I think it speaks for
itself. Without practice you get stale and lose your touch. I really like some
of his ideas on picking a new language to practice with and finding an open
source project to work with. I believe that all of these ideas will help to
make me a better programmer as long as I put them to work and keep up what I
have been doing. I am passionate about this and sometimes feel like I am behind
the curve, but I just keep plugging away and learning more every day.

Clean Coder Chapters 5 and 6

Chapter 5:

I have to say that I enjoyed these two chapters, I think in
part because they are on stuff that I need work with and don’t have too much
experience in them, well the test driven development (TDD) anyways. I find it
interesting reading about coding experience from someone who has been coding
since punch cards and to see how much the skill has evolved. I used to have a
Commodore 64 and was familiar with the Apple 2 machines and programming in
Basic. It is awe inspiring to see how much the languages have grown and power
of systems increase since then. Well back on subject and TDD. I do not have
really any experience outside of some TDD examples I have done for class and
reading about it, but I can see how it can be great. I think it may be hard for
me to get used to as though it makes sense to me in theory, putting it to work
in practice is another story. I like the 3 laws of TDD and imagine it is going
to take some getting used to writing tests before writing any actual code, and
sticking to it. I can see the benefits for sure. The thing that I like is that
it seems to force you to write smaller parts of the whole and in the end you
end up with not only a bunch of smaller modules, but you also have the tests to
go along with them and the confidence that what you have will work. The other
plus is that when you add code or update, you are only doing it to smaller
parts of the whole so it is easier to track the bugs when something does break
I would think. It is crazy that his FitNesse program takes only 90 seconds to
run and has 90% test coverage with only 17 bugs in his list. That there seems
to me like proof in the pudding on TDD. As I said before, this is something I
will have to work on and gain confidence with and take his advice on courage. I
really like the statement, “When you have a suite of tests that you trust, then
you lose all fear of making changes.” For now, I will just work on following
the three laws of TDD.

Chapter 6:

This chapter’s subject in my opinion is so very important,
practicing. He hits the nail on the head here. You can’t better if you aren’t
practicing your art. I certainly need more of it and don’t do enough, but I am
working on it and I plan on using some of the techniques in this chapter to
help with that. I enjoyed how he puts it together with martial arts terms. I
will be working on the Katas that he linked and other items. I don’t really
think that I can write a whole lot about practicing as I think it speaks for
itself. Without practice you get stale and lose your touch. I really like some
of his ideas on picking a new language to practice with and finding an open
source project to work with. I believe that all of these ideas will help to
make me a better programmer as long as I put them to work and keep up what I
have been doing. I am passionate about this and sometimes feel like I am behind
the curve, but I just keep plugging away and learning more every day.

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that.