Sprint Reflection 4

We didn’t do much over this sprint because of spring break. I was working almost everyday and didn’t get to see my team at all. When we came back we were finally able to come together and talk about the response we got for the button problem that we solved and pushed. We were met with a new set of requirements to change what we had fixed to better accommodate everyone. We want to make sure we have everything they want with our fix this time before we push it. We also picked new problems to work on with our team members in smaller groups. I think we are much better as a team now.

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.

The Software Craftsman Chapter 1 & 2

Chapter 1:

It talks about how just because you might have been a developer for a long time, doesn’t mean you are better than anyone else. No one person can say their skills are better than someone else’s because they have been working for a longer time, it doesn’t define their talent or knowledge. And with the times changing, companies want people who not only can code well, but can also help out in other parts of the field. Now, people want more things faster with better quality. And usually its integrated with everything else. I can relate to this because I understand that even if you work in the same place for a long time doesn’t mean you have the most experience. Someone new could come in and be way more experienced.

Chapter 2:

Seventeen influential people in the coding industry got together to share ideas and try to better their methods and techniques. What they came up with was agile development. It helps companies stay up to date with evolving soft wares and applications and the risks in involving them. With this type of development came problems. These people didn’t get the results they wanted, being agile actually ended up hindering their process. I can relate to this because to be great developers starts with being craftsmen at our craft. And to be good craftsmen, we have to master technical practices and constantly deliver quality.

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.

The Software Craftsman: Chapters 7 & 8

Chapter 7 covers the topic of technical practices. The author explains that Agile methodologies help build the right thing but craftsmanship focuses on technical practices to the build the thing right. These practices are referred to as Extreme Programming and have been considered part of Agile since 2001. The problem is that many companies did not adopt Agile’s technical practices for a number of reasons including they weren’t shown the business value of them. The practices mentioned by the author are as follows:

Automated Testing                                          Test First

Test Driven Development                             Continuous Integration

Pair Programming                                         Refactoring

All of these practices provide business value in the form of shorter feedback loops, cleaner code, improved system knowledge, or increased maintainability. The author goes on to say that all developers including managers should be held accountable for the practices they adopt and even more the ones they choose not to. Lastly the author reminds us the importance of pragmatism in being a software craftsman. Developers should always look for ways to doing their job better. It’s the developer’s job to adopt the right practices which provide the best business value and provide maximum customer satisfaction.

After reading chapter 7 there are definitely some good takeaways for my future development. Primarily I think it’s important to remember that it’s important to continuously look for ways to add value to your environment. While there might be a learning curve in adopting new practices, focusing on the business value in the future should suppress any doubts. While I don’t think every project needs to adopt every practice of Extreme Programming, I do think there is at least one practice that every project can and should adopt. At this point in my software development knowledge I would be hesitant to join a team in the future that was not practicing some sort of automation testing or TDD. It has been brought up so frequently by major role models in the programming world that I don’t think I could settle for anything less.

Chapter 8 covers the topic of the long road of a career to mastery. The author explains that it’s important to take control of your career and break it down into small iterations like you would a program. After each iteration, re-revaluate short term and long term goals and make sure your career is in alignment. If you’re not sure about your future then it’s time to create new opportunities to open doors for yourself. These can include attending tech events, blogging, or presenting at a conference. One thing to keep in mind is that your career is an investment. Maintaining and improving technical knowledge will always ensure a software craftsman is never too far from a job opportunity with the stability and security they need. The author goes on to say that aside from money there are three things which should motivate a developer in their career: autonomy, mastery, and purpose. He also warns the reader not to get caught up too much in a career inside a company. This can cause a shift away from personal goals and towards just getting the next promotion. He mentions that this is a common path to having under qualified and outdated managers. In conclusion a developer must understand where they want to be in their career and focus on reaching their own goals over a company.

After reading chapter 8, I think there is some really good advice to remember for my future career. I really liked his statement that knowledge is forever. I truly believe that if you maintain your skills and knowledge you will always be prepared for what life may throw at you. I do believe this chapter was aimed more for developers who have at least several years of experience. As someone who is just entering the field, I can’t be too stringent on the specifics of my first job. While I would not take a job doing something I absolutely hate, I think that you need to make a little more sacrifice in the beginning so that you can dictate the path of your career as you gain experience. Lastly I fully agree with valuing a personal career over any career within a company. If at any time it seems like you need to sacrifice your future goals to stay with a company then it is probably time to leave. This chapter was a good reminder that we are all responsible for our own path.

 

From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.

Software Craftsman 5+6 Week 10

Heroes, Goodwill and Professionalism:

This chapter consists of several personal stories that leads to the idea for the need to learn how to say “no”. Do not push yourself past your limit. Always saying no is not professional however there’s a happy medium where you will not overdo yourself.

Working Software:

Working software is not the end point. It’s the constant fight against the threats that you can not see. The chapter covers a common Agile anti-pattern, the Unit Test task card, and explains why it is a bad practice. Also goes on to define legacy code. Legacy code is essentially code that gets inherited by a team or programmer from somewhere else (external or internal). Almost every company has legacy code to an extent and there has a to be a professional attitude around that idea to deal with it.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Software Craftsman Chapters 3 and 4

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.

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

Software Craftsman Chapters 3 and 4

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.

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

Software Craftsman Chapters 3 and 4

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.

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

Software Craftsman Chapters 3 and 4

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.

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

Software Craftsman Chapters 3 and 4

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.

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

Software Craftsman Chapters 3 and 4

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.

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