The Software Craftsman Chapter 15 & 16 Blog (5/9/2017)

Growing up, I always thought you had to choose between making a difference in the world and having a career that pays really good. As it turns out, after reading this book, you can have both; as a software craftsman! I really enjoy reading this book throughout all of its chapters. There was definitely a good amount of valuable information but it was written in a way where a lot of important concepts were constantly echoed throughout the book; such as being passionate about what you do, always leaving the code you work on cleaner than when you first started and of course, realizing that its bigger than just you.

Reflecting back, I used to have the mindset of never wanting to share or collaborate with anyone else because I felt as though it was my code, and my code only. Now, I just chuckle at how ignorant and unknowledgeable I was. If there was only one concept I could retain from these readings, (not including passion) it would be the ideology that software projects are not just about us and our egos. To become better software developers (and better people overall) we have to think about the bigger picture. We have to make sure that the foundation of the code we create and work on is sturdy; that it will not come crashing down when we, the current developers, are no longer around.

I think one of the reasons why people shy away from legacy code is because the previous developers has created such a crappy foundation of code that we are afraid of moving or changing any piece of code due to the fear that everything is just going to come crashing down. But, it doesn’t have to continue to be that way. We have the power to change that way of thinking because we have the power to change the way we code!

From the blog CS@Worcester – Tan Trieu's Blog by tanminhtrieu and used with permission of the author. All other rights reserved by the author.

Software Craftsman ( Chapter 15 & 16)

Chapter 15 was all about the benefits of writing quality/expensive code vs. average/cheap code. It is a myth that quality code is expensive. According to the book, often managers must choose between producing quality products which take time to produce and average code that does not take much time to produce.  It is the duty of software craftsmen to produce clean quality code that is inexpensive.

Overall, what I learnt from this chapter is that quality code is not expensive. The lack of skills on the part of the developer is what makes quality code expensive. Developers must do their best to produce quality code which is inexpensive.

Chapter 16 was about what it means to be a software craftsman and how to have a successful carrier. The #1 word that summarizes what it means to be a software craftsman is passion. Software craftsmen are passionate developers and they love what they do. Being a software craftsman means that you much constantly learn and improve your craft/skills. You are in a journey to mastery. Mastery of software development is a long hard road. Every carrier decision you make must be in order to move you forward in your goal to mastery. And also, as mentioned in the previous chapters a job is a mutually beneficial relationship. Both the employer and the employee must get the best out of the relationship.

To sum up, I learnt about what is takes to develop quality/inexpensive software and what it means to be a software craftsman from reading these chapters.

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

The Software Craftsmanship Chapter 13 and 14

Chapter 13 talks about the learning culture and it states that Jr. Developers are lead to have this notion about becoming a manager is the outcome of all of their hard work. Lets say a Jr. Front End Developer has a passion for building front end applications. He/she could become a manager in the long run, but if there is a true passion for it, another career goal is to turn that Jr. Title into a Senior title.

Chapter 14 was a little interesting. It talks about the different types of developers that you might encounter. As we all know, there are a ton of ways to get a job done in programming and everyone has their own way of doing something. A person might see that this is the only way to do something, but your way is more efficient, you must walk them through your code so they can see why your way or your thinking would be the better option in this situation.

 

 

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

Software Craftsman 13-14

Developers need to continue to learn to be competitive especially in computer science since new technology and tool sets are constantly being developed.  To help facilitate learning, there should be a culture of learning in the company. If everybody in the company is complacent in just using the same tools or not learn anything new, it does not encourage anybody to go on and learn new stuff.

Learning new ideas lead to try and drive technical changes. This might be simple in a  start up company but at older companies, departments and bureaucracy can lead to huge resistance on change. Not only do you have to try and convince your co workers and your boss. Your boss may have to convince your department, your department may need to convince even higher in the company in important issues. Sometimes order comes from higher-up and there is no way to change the opinion of that.

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

Software Craftsman 11-12

Sometimes companies hire the wrong type of person for their position. It can be hard through phone interview to get a feel about a candidate. Sometimes a person that seems to be knowledgeable can have a bad work ethic or may no mesh with the company well. They might not even have the same goals as the company and may just use this opportunity as a stepping stone.

Hiring the wrong people can lead to bad morale. Struggling to get products out, leading to lower morale, leading to slower dev time. It is a downward spiral. Manager and developer conflict can also be a real issue as both sides can have conflicting interest on what is needed to be done.

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

Software Craftsman 9-10

Finding a great developer can be a challenge. It can take a long time to find one that’s the right fit for a company. A person can be great at interacting with people but may not have the best coding abilities. A person can also be a coding genius but will mesh with the team leading to a lower productivity than the former prospect. It can be difficult to find the best match for a position especially when many times you need to train the new people to their tool sets.

When you first start out, interviewing feels more like “I don’t care, I just want a job”. As you get more experience, interviews become more about a 2 way process. They confirm your skills and your fit to their team. You ask question about their company and what they want to do. Even new, it is important to try and ask questions about the company.

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

Software Craftsman 7-8

TDD and agile development is always talked about. Pair programming is always praised. However, sometimes those practices are just not feasible. Many times programmers will have multiple issues/projects they are working at once. Although you might have some time to collaborate with your co workers, chances are they are also busy and you are mostly asking questions instead of pair programming.

Extreme programming seems to work the best in some situations but not all. In extreme programming, the team self organizes around a problem then solves. However, there can be times where nobody wants to work on a mundane issues that can be critical to an operation. The manager then have to assign, and some projects may not work well under extreme programming.

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

Software Craftsman 5-6

Saying no can be difficult in a professional setting especially if you are new and your boss wants something. Managers that haven’t really programmed will keep trying to push new features or push frivolous features that takes a long time. There were time in my work where managers were pushing for extra features that ended up being not used by the end of the product cycle. Problem with is, unless you have some experience, you probably can’t say no.

This ties into deadlines, saying no can be hard especially if you are new. However, many people expect you to run into issue when you first start up and it does not hurt to ask. It is better to be delayed than write bad codes that will run into issues in the future. Unless it is a crunch time, then you have to get it done.

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

The Software Craftsman, Chapters 13 &14

Chapter 13 continues on the topic about how to keep people on your team motivated and interested in the software development field. I think this chapter has to be one of my favorites so far. All of the suggestions that are made about how to keep passion going in a team were interesting to go over, and just reading about them makes me want to give them a try. I think that my favorite idea, out of those suggested, was just switching projects for a few hours. This one is so simple and can be done a once a week, so it shouldn’t interfere with anyone’s work, but it is an easy way for team members to get invested in one another’s projects, and also encourage the learning and use of other softwares/ways of thinking in their own projects.

Chapter 14 mostly focuses on how to deal with different types of people that may end up on your team and how to encourage them to keep up with technical practices. I found that this chapter really just boils down to “know what you are talking about.” If you completely understand what you are trying to change, whether it is implementing TDD or trying to use a new language, the more you know about it the easier it is to explain it to everyone else. However, this doesn’t mean that everyone will except it just from your knowledge allow. Being able to also show your teammates and company how effective your change will be is also very important. In the end, to change the minds of the people that you work with, you want to make sure that you can clearly communicate with them, listen to what they have to say, and present these new changes in a way that will hopefully persuade most of your members to adopting them.

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

Sprint 6 – Learning Reflection

Sprint 6 marks the final sprint of our semester.  Our goal was to complete APTS-254 issue by the end the sprint.  The rest of our group ran into roadblocks and joined us in our endeavor.  We also hit roadblocks and needed more clarification.  Even though we found where in the code we needed to add the case, we weren’t positive about what the established reminders were doing.  So we determined that the only way we would be able to figure out exactly how these reminders worked was to recreate the scenarios in which they would appear.  Unfortunately, we were unable ETL server to work on our computers so we were essentially taking shots in the dark.

With all of this uncertainty, and the delayed response time from the people at Ampath, it was virtually impossible to accomplish anything of any substance.  In the end we were unable to complete our goal of finishing APTS-254, which means that we were only able to complete one issue this semester.  Perhaps I set lofty goals for our team, or maybe we underperformed, but one thing is for sure.  I can’t wait to spend way more time developing my own Angular 2 project.

From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.