The Software Craftsman Chapters 7 & 8

This week I read Chapters 7 and 8 in The Software Craftsman by Sandro Mancuso.

Chapter seven is titled “Technical Practices”. This is almost a continuation of the last few chapters where the author discussed how it was not enough to only adopt agile and the procedures that come along with it. There needs to be a balance with those procedures as well as the technical background to be able to implement those procedures well. Something that most people do not do and end up creating more problems for themselves in technical debt like i had discussed in my previous blog posts. Specifically the chapter talks about XP Extreme Programming and the history behind it. Extreme programming has a lot of big names behind it which in my opinion is enough to give it a second look. If people like Robert Martin are endorsing this so vigorously than there must be something to it. XP shortens the feedback loop and provides practices that make agile all it can be with things like Test Driven Development and pair programming. These practices have proved time and time again that they are more than effective however no one will adopt them. Well not no one but in my experience the vast majority of developers barely know what TDD is never mind how to really practice it. He talks about how the lack of these practices could be hard to sell and that is why things like SCRUM are easily pushed down peoples throats. In my opinion XP is a very useful way of programming.

Chapter eight is titled “The Long Road” and it was an amazing chapter. I know i say this a lot so bear with me but this really opened my eyes about my own future and career path. He talks in the beginning about not knowing where we are going, or in other words where we want our career to go. I am in this boat right now as i want a job but i do not really know down the line where i want my career to end up, what technologies i really want to work with or anything else for that matter. The author provides the reader with a number of solutions if this is the boat that you are in, something that i have taken note of. The rest of the chapter then talks about your job as an investment into your career. People often find themselves in a job and then just doing what they need to get the next promotion or advancement and forgetting about what they truly wanted out of their career. Depending on the different points in your lives that  may differ, whether its more time with family, more time on certain technologies ETC. . However it is important to always keep your career in mind and look at your job as an investment into that career and to always keep learning and make sure that your job fits the idea for your future and allows you to still pursue that, otherwise it might be time for a new job.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman (Chapters 11 & 12)

I found this chapter 11 really interesting and useful. Most of the scenarios that the author describes I have experienced.

The author mentions that before talented developers accept a offer they consider the financial offer, autonomy, mastery, purpose, productive partnership, talented and passionate people, and a good working environment. Of all the factors involved, I think working with talented and passionate people is the most important. I know what it feels like to work with unpassionate people. Working with unpassionate developers is not very productive and can be quite irritating. The only reason that I am a Software Engineer is because I LOVE Computer Science and I LOVE the craft of developing software. It is hard to work with other developers on creating software who do NOT share the same LOVE. You would not grow as a developer if you stick with unpassionate developers.

The author then talks about interview anti-patterns. The following are the interview anti-patterns mentioned in the chapter: don’t be a smart-ass interviewer, don’t use brainteasers, don’t ask questions to which you don’t know the answers, don’t try to make the candidate look like a fool, don’t block the internet, don’t code on a piece of paper, don’t use algorithms, and don’t conduct phone interviews. I have experienced all of these anti-patterns on my interviews for a year now. I would love to share some of my experiences, but unfortunately I don’t think it would be wise to do it.

The most important thing to understand from this chapter is that you as a software engineer are not a slave to your employer.

Chapter 11 is all about how important the morale of a team is. Low morale can destroy a company; and unmotivated people do a lousy job. A company must bring the best out an employee.

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 5 & 6

This week I read chapters 5 and 6 in The Software Craftsman by Sandro Mancuso.

Chapter 5 is titled “Heroes, Goodwill, and Professionalism. This chapter reminded me a great deal of the material in Clean Code by Robert Martin. The main point of the chapter was around learning how and when to say no. The author discusses all the negative effects saying yes can have when you know that you will most likely not be able to finish. As a graduating developer this is something that is really important to learn because it will be better for me to say no i cannot complete x task in that amount of time, however i can do Y, instead of saying yes and not being able to stay true to my word. Saying yes is often the easier path but being able to say no and stand by that is very important in this profession. The author talks about instead of saying yes, you can say no and provide the manager with options of how you can both move forward. This is the most professional option to take and ends up being beneficial for  both the developer and the managers.

Chapter 6 is titled “Working Software”. This chapter was also similar to clean code by Robert Martin, and he is making some of the same points that uncle Bob made. This chapter specifically talks about things like technical debt. He tells a story of how when working on a new feature a developer would rather finish the feature quickly and add a lot of work to the technical debt because he isnt implementing it well the first time instead of actually taking the time to fix his mistakes. This is the issue he discusses, how a large number of developers are more concerned with getting things done quickly then making well written code, and this in turn adds a large amount of technical debt that takes much much more time to tackle then just implementing well the first time around. It is much better to take the time the first time around to write tests and well written code then to have to go back and make changes and refactor a large amount of code because it was rushed through the first time.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 11 & 12 Week 13

The first section of the reading discusses how you as the interviewer should conduct the interview and what type of questions to ask. This chapter basically tell you what not to do when interviewing a potential employee. This such as don’t ask brain-teasers, don’t ask them to code on paper, don’t block the internet and dont ask questions you don’t know the answer to. Basically you want them to feel like they are in a work environment.

The next chapter is about keeping up the moral in the office. Low moral will cost the company money, developers will not work as well if they’re moral is not high enough. You need to keep you employees happy, you can’t MAKE them happy but you can do your best to keep the office in a general sense of content. You want your employees to have passion for the work that they’re doing and not think of it as “just a job”. A few things you can do is have daily meetings or bringing in developers that are very passionate to help bring out the passion in the other developers.

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 3 & 4

This week i read chapters 3 and four of The Software Craftsman by Sandro Mancuso.

Chapter 3 is titled “The Software Craftsman”, and goes into much detail explaining what this term means to the author as well as to the rest of the computer science community. He gives a short definition of the term as “Software Craftmanship is about professionalism in software development”. He talks about the debate as to whether software engineering is a craft, trade, engineering, science or art, which i think is an interesting debate. He then goes on to talk about why he thinks it should be considered a craft. This is something i completely agree with and reading this helped me to really grasp how amazing our field can be. Developers who really care about their career should consider themselves craftsman, and always strive to put forward quality work and improve themselves. The author talks about how software craftmanship should be a mindset and something that we devote ourselves to and i could not agree more.

Chapter 4 is titled “The software craftmanship attitude”. So far this is my favorite chapter in this book. The author starts out by asking the question “Who owns your career?” and then discussing that point in detail. It is not the responsibility of the company to further your development as a craftsman, they are not responsible for your career, that is up to you. He then goes on to discuss the many many ways that one can furhter their own skills and keep themselves up to date in this field. These include things like books, blogs and kata something that Robert MArtin was also a strong beleiver in. I enjoyed this chapter because it provided me with a great deal of ways and ideas to further my own skill set, and i look forward to owning my career. This is something that i think many people do not understand. It is not enough to go to work and code then come home and do nothing, you need to further your own skills.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

Sprint 6 Learning Reflection Blog (4/25/17)

This was officially the last sprint for this semester! It flew by a lot quicker than I thought it would. Even though each sprint was approximately two weeks long, it certainly did not feel like it. It felt especially short because it would take our group about two sprints for each issue so the time seemed very short and at times, we wished the sprint was longer because we wanted to be able to finish an issue within one sprint. Overall, we were only able to resolve one issue. For this entire sprint, we spent a lot of time choosing issues to work on. We would choose one issue that looks promising, contact a member of the AMPATH team for clarification or for assistance on how to fix the issue, and a team member would contact us back and tell us that the bug or feature has already been resolved in another issue. This happened to us 4 times! After the second time, it began to get annoying because we were wasting so much time on issues that were already solved!

If there was anything I learned from this sprint it would be how important it is to properly manage and maintain the issue tracker. AMPATH and companies in general can save a lot of time and headache with better issue management. If each issue was thoroughly examined, there wouldn’t be any unnecessary issues that are asking for fixes to something that another issue is already addressing. There shouldn’t be two issues that are asking for the same fixes; that’s counter-productive!

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.

The Software Craftsman Chapter 11 & 12 Blog (4/25/2017)

Chapter 11 was a good follow-up chapter to chapter 10’s interviewing software craftsmen. After reading this chapter, i gained a better understanding of what type of company I would want to work for. The books makes an excellent point by stating that interviewers should test candidates according to the things they value and to what is important to the projects instead of asking close-ended questions that anyone can answer by googling the question. Although I haven’t been through a huge amount of interviews, I can tell that most companies care about the “technical skills” rather than the passion of a developer. I don’t know about you but I rather be a developer that doesn’t know much but is passionate and willing to learn, than a technically-knowledgeable developer who does not care much for improving his skill set.

Also, here’s the summary to the idea and basic solution of low morale. Bored developers become lazy. Lazy developers become unmotivated developers. Unmotivated developers start to not care about their jobs. When developers don’t care for their jobs, the company makes no progress. When the company makes no progress, employees feel as though they are not developing and are not making a difference. When employees feel this way, their morale dangerously drops very low. So, basically if you want to stop this vicious cycle, don’t become one of those developers who becomes “bored”. How do you do that? Invest in yourself, constantly sharpen your skills, and be a software craftsman. That way, you will always be learning new ideas and talents; there’s no way you could get bored from that!

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.

The Software Craftsman Chapter 9 & 10

Chapter 9:

This chapter talks about big companies and their recruitment process. The process itself is flawed. Many problems such as not knowing the people themselves, but just searching through resumes using keywords. These people getting hired might not even be too good at what the company is looking for. This makes it harder to find more dedicated and passionate people who really care about what they do and their jobs rather than people who are just trying to do the bare minimum and make money. This makes it hard for companies to care about their clients’ cultures and values. That is why they should be used as a last resort. It also retells us how we should never think one developer is better than another, just because they have been in the field for longer. Only passion can drive innovation, it can not be taught. I can agree with this because the smartest people, the ones that are the best at their work are always outliers.

Chapter 10:

This chapter talks about the interview process from both the perspective of the interviewer, and the interviewee. It tells us how we can tell a lot about someone, by the way they give their interview and how they act in it.  It can tell you how they feel about others and even where they place themselves among them. We can learn if they want the job just for the money or if they even care about what they are doing. Because if they answer questions like a robot, like some sort of test, they aren’t really a good candidate. You need to find a person that can hold a good conversation that is trying to figure out if this job is right for them or not. This shows that they are interested in benefiting the company as much as they want to benefit themselves. A good partnership between the company and themselves where they actually enjoying working and not dread coming in everyday.

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 1 & 2

I have just begun reading The Software Craftsman by Sandro Mancuso. This seems to be a very interesting book from the first two chapters. The first chapter is titled “Software Development in the Twenty-First Century. This chapter basically just talks a bit about the authors experience as a developer and outlines what the book as a whole will be about. He talks about the modern developer something which i think is very interesting and most people do not really understand. Modern developers are no longer only people who just write code. That is not what they do even though that is all some people want to do. They need to be able to work on a team and understand multiple different business practices. There is much more to software development as a whole then just sitting down and writing code.

The second chapter is titled “Agile”, and it essentially outlines what agile really is as well as how the profession and business’ have reacted to Agile. This chapter helped me to grasp a better understanding of what Agile really is and what it means for a business or a team to be Agile. It talks about how agile is all about feedback loops and the more feedback you get the more opportunity you have to react to that feedback. It says “Agile does not solve any problems; it exposes them” This is very important, agile isn’t something you can adopt and have everything magically fixed. It will however expose all of your problems as they are happening (feedback loops) so that you can fix them for future iterations. The author then goes on to discuss companies who have only half adopted Agile policies and failed as a result. In order to be successful you need to be both competent technically as well as adopting all the procedures of agile. All in all it was a very informative chapter and i am excited to be able to practive agile on a development team in the future.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman: Chapters 11 & 12

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