Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Chapter 3

I am finding it hard to get into this book. So far it seems
like a re-write of the Clean coder but with different wording. I hope I am
proven wrong as I progress further but so far I am kind of disappointed. Do we
need a chapter devoted to talking about whether the skill of programming is a
craft, trade, engineering, science, or an art and five definitions and
metaphors for software craftsmanship? I can’t believe there are debates over
this to be honest, I mean I was always taught that when you work you do your
job to the best of your ability and put in an honest day of work for your pay.
I think it should be common sense that no matter the profession, you should do
it with pride and professionalism. Does it matter what you label it? I agree
that there needs to be meetings like the Agile summit and all that to talk
about practices and techniques that can help to improve coding efficiency as
well as end product results as this happens with most trades and professions.
New strategies are implemented and such, but work ethic and professionalism
should be a given in my opinion. I guess there are folks out there that don’t
know about this or maybe don’t care how their code or work looks as long as the
paycheck keeps coming in, but I have found that these types usually don’t hold
jobs long. Maybe I am being over critical, I just think the chapter was a bit
much.

Chapter 4

This chapter is a bit better than the last, there are a lot
of good points here and I feel a bit bad about condemning the book previously,
but I am writing about my feeling on the book as I go and that is how I felt
about chapter three. I enjoyed how he opened in the first couple of pages about
the talk with his friend and his response to him after he told him how he hadn’t
been promoted and how the company hadn’t sent him to seminars and such. “Who is
in charge of your career?”, what a great comment and so true. I have met many
people who have this attitude that the company owes them and should see how
good they are and send them here and there. Well I got news for you, that is
not how the world works. I hear it here at school and I too am sometimes caught
up in the I wish we learned this or that and then come to my senses and realize
that I have the tools to learn this stuff myself and that is how you get
better.

There are many good points in this chapter. I am still in
awe at how much there is out there to learn and the tech changes it seems
daily. There is always something new to learn and a lot of this is new to me,
not the learning part but the technology. I would have never thought about
following blogs before coming back to school. I do have to work on who to
follow however as there are so many out there. I am slowly finding a niche. I
am slow to Twitter and social media and could use some work in that area. I am
not sure why, maybe an age thing or I just haven’t tapped into its full
potential yet.

The rest of the chapter is well done as well, but I am not
going to go on and on, but it is, in my mind one of the most important things
in this field, practice. If you aren’t practicing your craft, you lose a step.
I didn’t know about katas until I read the clean coder and will one day give
them a try. There is no excuse to not practice these days. The word though can
throw you off though as some folks despise practice as it reminds them of the
horrendous drills you had to do in sports and such. Coding practice though is
much more fun as there are so many ways you can hone your skill set. Open
source, katas, projects, etc. Choose something you like and it is a heck of a
lot better.

Well this learning reflection is going to be short as spring break got in the way and well I was lazy over the break and didn’t accomplish as much as I would have liked. I will say that this whole experience so far has been decent, but has had its challenges to me. It has taken a while to get to where we are at and when we finally got issues the semester is half over so that is kind of frustrating, but like with anything in life, things don’t always go as planned. We have been working on an issue to do with logging out while you are editing a form and it is not saving your data. The whole team has been assigned to separate parts of this and my part was to figure out the routing to use when it was all said and done. Upon looking into the issue though I cannot do the route until someone else does their part so I was kind of at a standstill in a sense. I have become more familiar with the projects code though and I happy about that. After discussing the issues we found out that we were looking at the issue wrong and were now waiting on the folks at ampath to get back to us. I will quote a team member as to what we need to work with no, “So the actual problem with the code is that the confirmation dialogue is being run asynchronously using an observable. Which means as soon as the observable is made it is being returned regardless of whether you have clicked accept or not. Which means the value that’s returned by canDeactivate is neither true nor false which is what glitches out the routing. Supposedly, if you make the return value of canDeactivate, Observable<boolean> it’ll wait for the returned Observable to complete before judging the activation but for some reason that’s not working.”

So what initially seemed to be straight forward has proved to be a bit more challenging as we get further into the proverbial can of worms and are now trying to come up with a plan of attack at this. I like how this is unfolding though as I am learning a lot even though it doesn’t seem like we have done a whole lot we are still learning about what problems and issues can arise while tackling a bug and the process of working together as a team as well as using electronic communication and the various tools at our disposal to solve the issue. I am confident that this issue will be solved now that we have a direction to go in and I am looking forward to tackling the next challenge. We are going to be pairing up and doing some pair programming for the next issues. I have never done this in practice and am looking forward to it. I have read enough on it and it seems like a good way to do things.

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.