The Software Craftsman, Chapters 3 & 4

In the third chapter of Mancuso of The Software Craftsman, he goes over what it is to be a software craftsman and the basic manifesto of it. After reading The Clean Coder, a lot of this chapter just felt repetitive. The just repeated what “Uncle Bob” said in the previous book; make sure code is working, but also easy to maintain and predict, make sure code can cater to the clients/industries changing demands, but make sure the code stays clean and is designed for a long lifespan, make sure to help other developers in need to build a better community for everyone, and understand that software development isn’t only about producing code, but understanding who you are making the code for and why they need it. The one thing that I like about this book more than The Clean Coder is Mancuso acknowledges that some companies will only see software developers as assembly workers and sometimes you can’t change their way of doing things. In this case, Mancuso wisely advise that you start looking for another place to work if that is the case.

In chapter 4 of The Software Craftsman, Mancuso goes on the top of “Who should be the one to advance your career?” Just like “Uncle Bob”, Mancuso points out that it is every software developer’s responsibility for them to continuously teach themselves new technologies in their field and not the companies responsibility to train them. As I might have said before when reading the The Clean Coder, I think that it depends on the company you work. If you work for a company that uses proprietary software or coding language, I believe that the company is responsible for making sure their developers get proper training on what they are using or provide material for them to learn about it. However, this does not discount the fact that developers still need to keep up on new concepts or behavioral techniques that they need to develop on their own. What I did like much better then The Clean Coder was that Mancuso delved into some of the different ways software developers could acquire the knowledge they need to keep up to date on their careers. He also took the time to create a small list of where to start acquiring this knowledge, and how to properly view this different ways (ex. types of books vs blogs vs technical websites). After that it goes into what The Clean Coder already stated; make sure to create pet projects for yourself and find “katas” you can do everyday or free period, paired programming/learning from other developers, contributing to open source projects to practice, and he also repeats the same “make time outside of work to work on these things” and the “25 minutes of work/5 minutes of break” technique that Martin spoke about.

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 ( Chapter 7 & 8)

Chapter 7 is about the usefulness of technical practices and how to convince your peers on using some of those technical practices. This chapter talks about many things that I don’t think are very useful at this point of my carrier.

Chapter 8 is about what motivates us and how to build a career. The first section of this chapter starts out with a story of the author ( I think). The author had a dream of working in London and he figured the way achieve that dream is to become a software engineer.  He did not speak English at the time and his skills set was pretty basic. He however did not give; he kept working toward his goal until 10 years later he finally achieved his dream. He became a software engineer working in UK.

The moral of the story I think is that nothing comes for free and mastering a skill of achieving a goal takes time and hard work.

And also a software craftsman must always look for three things when choosing a job: autonomy, mastery, and purpose.

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 Craftsman Chapters 9 & 10

Chapter 9: Recruitment

When trying to find and hire new Developers there are some guidelines you should take into account. If your job listing is focused too much on listing technologies you use and years of experience needed with those technologies you may be attracting the wrong kind of Developers. Just because someone can tick all the boxes doesn’t mean they will be the right fit for your team.

When writing your job listing it is better to focus on what type of person will be the best fit for your team, emphasize the responsibilities they will be need to undertake when working for you, and talk about what type of environment a potential hire will be working in.

Following these rules can help you attract Software Craftsmen that will become valuable assets in the future.

 

Chapter 10: Interviewing Software Craftsmen

The interview process is used by both the Company hiring and the potential hire to ascertain whether the relationship they will forge will be beneficial for both parties. The Developer in the interview is trying to see if the Company he is applying to will help his career and reputation. While, the Company is gauging whether the Developer will be useful to their ends.

When conducting an interview the Hiring Company should make sure that a candidate is passionate about their job. They should look for the ways a candidate describes their past jobs. What successes they and what failures they overcame. The candidate should also be eager to learn about the Company they are trying to get into. They should ask pertinent questions that help show they are interested in the work they will be doing.

On the other hand, a perspective candidate needs to see whether the hiring company is really a place he/she wants to work at. You can start by finding out who the interviewer is. Hopefully the person interviewing you is another developer that, if you are hired, you will be working with. If the interviewer is reading off a list and not asking broad questions that may mean that they don’t really value your opinions and are just looking for a person that will follow orders.

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

The Software Craftsman 7 & 8 Week 11

The first part of the reading talks about adapting technical practices and getting other developers or managers on board. Just telling developers or a manager that your going to be using something like TDD might make them question that practice because it will end up taking longer. What should be done is ask questions like do we want this to be bug free or do we want the code clean. Then once they see the advantages talk about what technical practices to use.

The second part of the reading goes on to say that the goal of being a software craftsman is to find pleasure in your work. Purpose and mastery are ideal characteristics when looking for a job, but that cannot always be done. The more experienced you become the easier it is to find jobs like this. To find this you need to know where you are in your career and work to where you want to be, nobody else can do this for you.

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

Reflection: Sprint 4

To be honest, we didn’t had significant progress during this sprint. One of the reason was that we had a spring break during this cycle, and the other one is, we waited long enough to the get clarification on our issue. Regarding our NGPOC-183 issue, we tried to reach out developers on JIRA as well as on Slack we but didn’t got any reply.

Therefore, we ended up assigning new issue named APTS-296. The issue is “Add 24 and 36 Weeks Under Week Control in Return Visit Forms”. As of now, we as a team, got a strong understanding of this issue and know what need to be fixed. Hopefully this one shouldn’t take long.

We are in progress towards making our first change.

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

The Software Craftsman: Chapters 3 & 4

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

The Software Craftsman: Chapters 1 & 2

The very first chapter titled “Software development in twenty-first century” discusses about what seniority really means and also the new reality faced by developers in the twenty-first century. Seniority is transient and relative, there is no such thing as a senior or junior developer.

Mancuso argues seniority is not just about composing code or being exceptionally acquainted with a dialect or system. Developers need to know how to address clients, automate tests and deployment, and settle on mechanical decisions that may influence the whole business.

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

The Software Craftsman 5 & 6 Week 10

In the first section of the reading the book it explains how to learn to say “No”. Sometimes you’ll work with managers or clients that expect too much from you, it is not professional of them to ask you to do more than you can. If you know a workload is going to be too much for you to handle do not hesitate to say no. To be a professional you must know when to say no to a client. The client is trusting you and your expertise, so do not agree to something you can’t do just because they are paying you.

In the next section talks about not rushing during coding. If you rush during coding chances are the quality will depreciate. If the quality is not up to standards then the code will be extremely hard to change later on. So the best way to code is to take your time if you want your software to be able to be maintained in the future.

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

The Software Craftsman: Chapters 7 & 8

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

Software Craftsman Book Chapter 7 & 8 Blog (4/11/2017)

Although chapter 7 was mostly review of concepts I already learned, I do think it’s important to at least restate the idea of the “boy scout rule” and the “broken windows theory”, which was mentioned in chapter 7 because it’s an important mentality to be aware of. The boy scout rule is to “always leave the campground cleaner than you found it” and the broken windows theory states that “the bigger the mess is, the bigger it will become”.

Something that I did find helpful in chapter 7 however was the idea that we should not follow practices just because someone said so. Like with everything else, we should take all agile practices with a grain of salt because each practice can be extremely efficient in some cases, but rationally useless in other cases so it is ultimately up to us as the developers to know when to use what practice.

Chapter 8 mentions that there are 3 main things that a craftsman should look for in each job; autonomy, mastery, and purpose. I think it is every developer’s goal to find a job that fits these three qualities, because if you did, then you would now be doing something you love to do, rather than doing something because it offers large paychecks.

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.