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.

The Software Craftsman: Chapters 5 & 6

Cahpter 5 resembled Chapter 2 from Robert C. Martin’s book The Clean Coder which has many of the same themes as this book. This chapter mostly covers the fact that as a professional you occasionally need to say no. If you don’t say no when you should say no, things can get ugly quick. I won’t talk too much on the reasons why here because I talked about it in more detail here.

I do want to talk briefly about one thing that was said in this chapter. With good managers, there should never be a “us and them” attitude. This could never be more true and I recently experienced the downside to an “us and them” attitude. I was on a job with the the VP of Stack Testing in Bridgeport, CT. We were working as contractors for a fairly large power generation company, we’ll call them “Big Guys”. So Big Guys have so many power plants that instead of contracting companies like us to do their stack testing, they have an entire team of internal stack testers. However, an issue came up where Bug Guys’ stack testing team didn’t have some special analyzers that my company has. This equipment is very expensive and very complicated to use. So we arrived on site and immediately the upper management of Big Guys made us feel threatened. The upper management made multiple comments about how if we screwed up even the slightest bit that they were going to throw us off site and hire a different contractor. That was the first sign this was going to be a rough few days. Anyways, we ended up meeting Big Guys stack testing team, we’ll call them “Little guys”. All of the stack testers from Little guys were incredibly nice and welcoming to us. They were excited to have us on site and really excited to see our equipment in action.

After a 16 hour day of testing along side Little guys, we started seeing some trends. Big Guys management kept referring to the testing that was happening as “Your tests”(Directed towards Little Guys), like somehow Little Guys are requiring them to test when the reality it that the State of Connecticut was the one requiring THEM (Notice the beggining of the Us and Them mentality). Then we noticed that Big Guys were not giving Little guys any information until the very last second. Each time they did this the sent Little guys into a frenzy getting ready for the next test. Same things like this kept happening throughout the day.

We arrive on site the next day to find out that after the previous day, Little guys were upset and disgruntled about the previous days happenings. They began venting to myself and my boss. The “Us and them” mentality become so apparent when they started go against what Big guys were telling them to do. Towards the end of the second day, Big guys told little guys on their last hour of tests to pause their tests. Big guys eventually told us why they paused the test and the reason was completely strange. They had us pause for reason that were 100% unrelated to what we were doing at that moment. Little guys made a unilateral decision to continue testing so they could leave before 7 pm. Obviously Big guys were furious when they found out and there was a yelling match (Thankfully neither my boss nor I were present for) between Big guys and Little guys. The moral of the story is if they had not had this us vs. them mentality I am almost positive the days would have been smoother and we there definitely would have been less contention.

 

Chapter 6 talks about Craftsmen as gardeners. I really appreciate this visual. There certainly is a difference between someone who plants and someone who gardens. Someone who plants prepares their base, digs their holes and plants their plants and then moves on. If you do this as a gardener then you will quickly find your plants getting choked out by weeds or overgrowing other plants. This is not okay. One of the most interesting points made was the mindset of developers thinking the didn’t have enough time. I never realized it, but I have done this. Multiple times. Working on small projects I could have saved my self countless hours if I had simply taken the time to create unit tests. I see that now. I know that now. But I still don’t always do it. Why? “CAUSE I THERE’S NO TIME FOR THAT!!”. Really? Really, Tyler? Don’t you remember last time you said that? You spent hours debugging a simple logical error that could have been found in seconds using unit tests. ….Yeah, I still skipped unit testing to push features “faster”. This is something I am trying to break for sure and this chapter was a good reminder that it’s a time saver for everyone if I simply write unit tests and take the time.

Guess what, Tyler. There. Is. Time. Write Unit Tests!

I have the written on a sticky note on my monitor at home.

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

The Software Craftsman: Chapter 5 & 6

Chapter 5 of The Software Craftsman basically talks about dealing with pressure and deadlines as a professional and not always being the “hero”.  As a software developer you aren’t a superhero and you don’t need to say yes to everything asked of you.  In fact, a huge point this chapter made was learning to say “no”.  This topic of saying “no” is something that we read about in the last book, The Clean Coder.  Although saying “no” may seem to be rude or unprofessional, it is actually the professional thing to do.  In the field of computer science, there is pretty much always something that needs to get done.  This doesn’t mean that you always need to be the one to do everything.  It is great to work to your full potential and get a lot done, but when you start saying you’ll do things you don’t have the time to do, it can get bad quick.  It is better to have good quality work rather then quantity.  Overall, I enjoyed reading this chapter.  Even though we already learned about this topic from the other book, I enjoyed reading the author’s personal stories on this matter.  He really went through hell trying to be the hero all the time, but luckily he came to his senses.

Chapter 6 discussed the issues with low quality software.  The author basically talks about how keeping up with the code base is very important.  Working code can easily turn into low quality and very bad code.  He discusses how many software developers will ignore the legacy code because they don’t want to deal with it.  However, that is a terrible attitude to have.  Putting off this problem is only going to create a bigger problem later on.  It is a much better idea to update the legacy code piece by piece so eventually the code will be working again.  This author made some very good points about working software and the attitude you should have towards it.  Personally, I would much rather just ignore legacy code and do something different.  However, this chapter made it clear that ignoring the problem is never the answer.  Keeping up with the code base and updating it with unit tests can make a huge impact on the overall product.  No one likes non-working low quality software.  From now on I will deal with situations like this piece by piece rather then facing a huge problem all at once.

 

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.

The Software Craftsman, Chapters 1 & 2

In chapters 1 of The Software Craftsman by Sandro Mancuso, it talks about how developers need to adopt to the changes that are constantly happening in the software field. It states that developers can no longer be only about coding. Instead they need to know about multiple different disciplines and techniques to be successful in the field now-a-days. This is nothing new to me. Lots of companies will not bother to look at your resume if you do not have at least some knowledge of different languages and frameworks, or even if you only have one degree. Also if a developer has no idea what the Agile process is, then they are going to have a hard time in this industry, so most of that part and the next chapter just seemed repetitive to me.

In chapter 2, Mancuso goes over what the Agile process is and how some companies fall into the trap of only transforming their process into a partial Agile process. Again there was nothing really new to this chapter for me. It’s already been driven in how the Agile process works, and how it’s not just making meetings and Sprints shorter, or how to deliver code and receive feedback faster. The other half is making sure that you produce code that is readable and can be easily changed if needed. If other developers are intimidated by the code that you are producing, whether that means that they don’t know how it works or if it’s badly written, then you need to go back and fix the code you are writing right then and there. If you neglect to do this, it means that that piece of code will most likely cause issues down the line because other professionals can not go back and easily change it if there is a issue that pops-up with the section that you’ve written.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

The Software Craftsman ( 5 & 6)

Chapter 5 of the Software Craftsman book was a very good read. It gives some very important advise on what it means to be a software professional ( not software slave ). The thing that I found really interesting was the fact that the author of the book used to work for a company that had him start work at 5:00am in the morning and end at 8:00pm at night. And sometimes he worked so late he had to sleep in his car! All for what? Nothing! Absolutely nothing, but being branded a bad software developer.

Sandro Mancuso ( the author) wanted to be seen as the hero who saved the project, the man who made the impossible happen and a great software developer. Instead, he got the opposite and being blamed for the failure of the software project.

The rest of the chapter gives some good examples of what it means to be a software professional. Being a software professional means telling the truth and being honest on what can and cannot be done. Being a software professional means knowing when to say no to a feature request from clients. Software professionals have ethics, and a code of conduct.

Chapter 6 of the book is about what make good software. The author talks about the many things that the software developer must do in order to develop good code. Most of the ideas that the author talks about is from, I think, the Clean Code book.  So there is nothing really new in this chapter.

Overall, the message that I got out of this week’s reading is that a software developer is a professional. The chapters elaborate on what it means to be a professional. And a software professional is not a slave.

From the blog CS448 – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.

Software Craftsman chapter 1 & 2.

The first chapter of software craftsman talks about how different being a software engineer is today. Knowing how to code is not sufficient to be considered a craftsman, we need to have the knowledge to aid a company in other areas as well. I can see how this is important because in the workforce we have to prove ourselves to be an asset to the company we work for. It is not just about mastering our craft, it is also about showing that we are flexible enough to learn new things and adapt to changes .  Like the book explains having experience in one area is not always the best route. Someone with less experience in the field maybe more knowledgeable in more areas. Chapter 2 Talks about the agile transformation which embraces processes and tools such as Scum and other methods. My experience with scrum has only been in my classes.  But i can see how practicing scrum and other tools alike really contribute to the Agile Manifesto.

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

The Software Craftsman 3 & 4 Week 9

In the first section of the reading first goes over what software caftsmanship is. It goes on to say that it is about a developer mastering his/her skill and being the best they can be while being professional and responsible. A craftsman will also look for partners to work with that are as professional as they are. It is also about having a good reputation, so projects being worked on are taken very seriously. Being a software craftsman is a lifestyle, not just a job.

The second section of the reading starts off by basically saying it is your responsibility as a professional to keep learning and keep up with current technology. It goes on to say that you own your career, no one else, so you must always be learning and practicing. Some companys may help you learn new things but it is not their responsibility and you would be lucky if they do.

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