Week 6: The Clean Coder, Ch. 11 & 12

In chapter 11 of The Clean Coder, the author writes about pressure. Everyone handles pressure in there own way it can be a deciding factor in determining how professional some on is. A true professional should be able to keep calm under pressure, they should maintain the the ability to make decisions without panicking. I personally don’t mind working under pressure especially in the context of class assignments. This turns out to cause issues for me as I tend to wait until the last moment to start an assignment. I then use the pressure to force myself to focus. On some group assignments I have noticed how others react differently. In one example, I was working in a group with two others, one who procrastinated like myself and on how started panicking while we still had a week and a half. In this situation I really saw how pressure affects people differently. I have also watched some people react in extreme ways. At the small Internet company I worked at one of the employees had called out. Because of this I and another employee were asked to help with shipments. I knew how many shipments needed to go out and how much time I needed. I told the other person that I could handle it myself and not to worry about it. At one point my coworker started to help claiming I would not finish in time. Within a few minutes she started to panic and rush, this cause the packing process to become a mess. It came to the point where just decided to give up and ended up leaving the office early. I finished the packing with 45 minutes to spear. In many situations it is probably better to just avoid pressure. Many of the ideas in earlier chapters can aid in this, for example, not committing to a deadline you know is too short.

Chapter 12 was all about collaboration. I believe this is a very important topic in the field of computer science as most developers work in a team. I can see how working on a team can difficult and rewarding at the same time. There has been several times I have been working on a project and found myself stuck, in these situations it is good to have a team or at least a partner. Sometimes I just need a bit of help getting past a issue, other times the simple act of explaining the problem was enough for me to come to a resolution. I think the most important element with in a team is trust. For a team to function efficiently each member must be able to rely on the others.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman, Chapter 9 & 10

For this week, I read Chapter 9 Recruitment and Chapter 10 Interviewing Software Craftsmen, from the book title The Software Craftsman by Sandro Mancuso. Chapter 9 takes a look at the picking process of hiring the best developers. Best developer’s identification is that developer must be passion for the craft. Chapter 10 explains the interviewing process that works both ways, the interviewer (who represents the company) and the interviewee (potential hiring candidate) looks for compatibility with each other. The interviewer checks whether the candidate is best fit for the company and the interviewee try to find out whether the company is best fit for him/her.

Chapter 9 explains in detail on attracting software craftsmen to a company. It also walks the reader on a journey on how to craft a job description. I feel like this chapter is the best read for anyone who would like to recruit or looking for the best developer for his/her company or organization. After reading this chapter, I would recommend this sole chapter reading to anyone who carries out the recruiting or hiring process at a company or organization. I believe the author did a fantastic job on covering and perfecting attracting and putting out description for a target and ideal candidate for a job.

In chapter 10, author covers the interviewing part of the hiring process. One emphasis of the author that I liked was when the author explains asking questions in the interview. According to the author, interview should not be only the company asking questions from the potential candidate, but rather the question process should be from both sides. If the candidate is a craftsman, then he/she must have questions for the company too. This way the company and candidate will insures that they both are best fit for each other.

This was very informative read especially on the job description and interviewing.

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

The Software Craftsman, Chapter 7 & 8

For this week, I read Chapter 7 Technical Practice and Chapter 8 The Long Road, from the book title The Software Craftsman by Sandro Mancuso. Chapter 7 explains adoption of extreme programming (XP) like Test-Driven Development (TDD), pair programming, refactoring, simple design, and continuous integration. Chapter 8 explains how to approach job choice and what it takes to have a job/career where you would be happy.

In chapter 7, the author describes and explains all aspects of extreme programming. For example, Test-Driven Development (TDD), pair programming, refactoring, simple design, and continuous integration etc. The best thing that I learn from this chapter was when the author states “Being pragmatic is one of the best quality that a software craftsman can have.” This explains that professionals are not limited to following certain practices and processes where they would always receive optimum results. But rather, as professionals we need to keep looking and searching for ways of doing our jobs better and satisfying the needs of our customers. Whatever it takes, at the end of the day what matters are happy clients. We should follow any practice that we believe will give us this result and we should be accountable for whatever decision we make and always take responsibility for the outcomes.

In chapter 8, I like when the author breaks down job choice base on three criteria: autonomy, mastery, and purpose. Craftsman must look and consider these three things before choosing a job. I believe that this is a good criteria to have, but to be able to choose based on these criteria, individual needs to overcome a lot of obstacle and challenges. You need tremendous focus and determination in order to excel and expand your knowledge and skills.

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

The Software Craftsman, Chapter 5 & 6

For this week, I read Chapter 5: Heroes, Goodwill, and Professionalism and Chapter 6: Working Software, from the book title The Software Craftsman by Sandro Mancuso. Chapter 5 explains the need and urgency of when and how to say “No”? Chapter 6 explains the effects of technical debts on companies and stabilization of existing code, and improving it.

In chapter 5, author explains one of the hardest thing to say in general which is saying “No”. As a professional, one must have the courage to say “No” when he/she does not think that his/her client or boss is not being reasonable or does not understand the scope of what he/she is demanding. As a professional it is our duty to stand up for ourselves and make people around us aware of the entire situation as transparently as we can. Always, be clear and careful at your decision and commitments. Be sure what you have been asked and what you are committing is achievable. I believe saying “No” is one of the hardest thing about being a professional and I hope that I don’t have to be the first one to say “No” as I am stepping into the real world. I wish that I see my senior say it first then I will follow.

Chapter 6 was my favorite chapter because it talks about a topic most software developers and companies ignore to pay attention to once they complete a job or project. I believe for any successful software company or business needs to constantly work on its old code and try to make it better in order to increase its adaptability. Companies need to hire craftsmen to refactor its existing code. I like how the author puts in the book, “rather than construction, programming is more like gardening.” this quote explains that rather than keep producing new code every time, it is more efficient to make existing code better so it is more adaptable. It can save companies time, money, and maintenance in the long run.

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

The Software Craftsman, Chapter 3 & 4

For this week, I read Chapter 3 Software Craftsmanship and Chapter 4 The Software Craftsmanship Attitude, from the book title The Software Craftsman by Sandro Mancuso. Chapter 3 describes what Software Craftsmanship is? Chapter 4 put emphasis on the importance on how to keep learning and develop yourself over time?

In chapter 3, author defines a software craftsmanship. One of the definition that I liked was when the author stated that “Software Craftsmanship is about professionalism in software development.” This definition explains what software craftsmanship or field craftsmanship should be all about. Software Craftsman must care about his/her clients and help them achieve whatever they want to achieve, always try to make himself/herself better at his/her craft, learn from other in the field, share his knowledge and best-of-all mentor less-experience individuals in the field.

In chapter 4, author put focus on learning by yourself and make the right and wise decision for yourself. Just like in The Clean Coder book this author also suggests that you should never rely on your employer to give you all the training and resources in order to improve your knowledge and skills. You should take charge and responsibility for your own learning, and develop your skills by yourself over time. Author offers many useful strategies to improve and keep yourself up-to-date with the changing industry. I personally like all these suggestions from The Clean Coder book and have implemented some already.

Both chapters were very enlightening in order to be successful in the software industry. I have already plead to follow all these suggestions from the previous book.

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

Sprint 6: Reflection FantasticFive

Sprint 6 was the last sprint of the class so we came together as a team and try to work together this sprint. We picked APTS-306 issue and later, APTS-340 issue from the Backlog.

APTS-306 description was not clear so asked for more clarification. Here is the description of APTS-306 issue:

“Users are requesting if “Patient Newly Enrolled in Second Line” indicator can be added under list of indicators used in clinic dashboard and data analytics”

We contacted the assigned AMPATH developer to the issue on JIRA (Robai). She got back to us with a little explanation, but referred us to AMPATH developer (Brain) that was in-charge of that part of the project. Brain took about a week to respond and in his respond told us that APTS-306 has been handled by APTS-238 issue, APTS-238 issue was already solved.

We did not have much time to work on another issue, but still we searched Backlog for an easy fix issue. Sudarshan picked APTS-340 issue to be a good issue to be consider in the remaining time. Here is the description of the APTS-340 issue:

“When adding “HIV” treatment program when user selects “date enrolled” and “date completed” it throws the following error “date enrolled or date completed should not be in future””

APTS-340 issue was a bug that needed to fixed. Sudarshan asked for more details on the issue from AMPATH team. We got a respond and were told that this bug has been already handled by another issue.

Throughout Sprint 6, we attempted two issues: APTS-306 and APTS-340. Unfortunately, both issues were already solved by other issues.

Take away from Sprint 6 was that we worked as a team. We communicated and collaborated highly through Slack and in-person to work on these issues. Now, we feel much more comfortable working and trusting each other. I believe the reason is that through the process of working together in this class we found out a lot about each other’s personalities. Each other strengths and weaknesses. I feel like working in a team is much more challenging than working individually. I learned that responsibility on individual in working in a team is much higher than working on your own because when you are assigned a task in a team, your team counts on you to deliver that task in time. If you cannot deliver that task then entire team’s delivery process delays which does not only make you look bad, but the entire team is a victim of that judgment. This was a good lesson learn for getting into the real-world.

I just want to say that it was a pleasure working with all my team members and getting to know them. Best of luck guys!!!

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

Sprint 5: Reflection FantasticFive

Team members decided to pick our individual issues and if some members want to work together on an issue that is fine. Sudarshan worked on NGPOC-184 issue, Tan worked on APTS-225 issue, and me and Angelito picked APTS-305 issue from the Backlog to work on. Towards the end of Sprint 5, we picked APTS-214 issue while waiting for AMPATH developers’ response on APTS-305 issue.

In the beginning of Sprint 5, I had lots of work due in my other classes. During Sprint 5, I needed to turn in lots of assignments and had to take three exams. I had managed to focus on this class while taking care of my other classes. Me and Angelito picked APTS-305 issue from the Backlog to work on. In the process, Sudarshan also helped us. The issue description was:

“ users suggested having an additional column of order type in  lab orders under Data Analytics ” Patient Requiring Viral Load Test” The additional column to display  order type e.g Viral Load,  DNA PCR and CD4”

So, we thought it is just a simple touch to the code. All we had to do was make a column with a name “Patient Requiring Viral Load Test”. We made the column and were done in just 15 minutes, but the simplicity of the issues was too good to be true. So, we decided to confirm it from the AMPATH team. While Angelito communicated with the AMAPTH developer; Sudarshan and I went on and picked another issue (APTS-214) from the Backlog.

APTS-214 issue description was:

“Currently user does not get any message to be sure that the locator map has been saved successfully and also the user can clear any existing map without a warning message that the changes made is not revertible.”

We needed some help on this issue. So, Sudarshan asked for more explanation on APTS-214 issue from AMPATH team.

We had a respond back on the APTS-305 issue from the AMPATH developer and she said that there was another ticket (APTS-229) issued on this same issue, and it has been solved by APTS-229 ticket. We had to dropped this issue.

Also, we had a respond for APTS-214 issue too. AMPATH team suggested that this issue needed to be taken care in another sprint. For now, we need to hold-on on this issue. We had to discard APTS-214 issue too.

In Sprint 5, we attempted four issues: NGPOC-184, APTS-225, APTS-305, and APTS-214. Sudarshan successfully pushed NGPOC-184 issue to the AMPATH repository and was accepted after some obstacles. Tan is working hard on APTS-225 issue. Me, Angelito, and Sudarshan worked on issues: APTS-305 and APTS-214, but we had to dropped both of the issues because one was already solved and the other was too early to implement or work on.

Sprint 5 turned out to be a pretty good sprint for our team because first, we got to solved the NGPOC-184 issue. Second, we acted more like a team than individuals working at the same table. Third, our communication had gotten so much better than the beginning of the semester. I believe our team is really “gelling” together. I am proud of all my team members. Go FantasticFive!!!

From the blog Software Learning and Development – Haider Hussain by hhussainsite and used with permission of the author. All other rights reserved by the author.

The Software Craftsman chapter 11 & 12

Chapter 11 is titled “interview anti-Patterns”. This chapter talks about the wrong processes to go about conducting an interview as a developer. They should avoid doing things like being a smart-ass interviewer, using brainteasers, asking unnecessary  questions, and trying to seem superior in knowledge. After we’ve worked hard to find a qualified candidate, the last thing we want to do is steal the opportunity they have to shine. We want to convince them that our company is the best they can work for, because a good developer will also be looking for a company that is best for them.

Chapter 12 talks about the cost of  low morale and how unmotivated people seem to represent that very well. Unmotivated people tend to destroy companies because this can change the motivation of other workers significantly. I believe that the attitude of the people you work with can have a huge impact on the way you work; they can either motivate you or suck the morale out of you. In this chapter we learn that people become like that and that is mostly due to companies beating the passion out of developers. Manager and agile coaches are the last people to motivate developers because they are demanding and punctual about everything. The only person that can motivate a developer is another developer. Not just any developer, but a software craftsman that every team needs.

 

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

Week 5: The Clean Coder, Ch. 9 & 10

Time management is a topic that spans all fields. I would argue it is one of the main keys to being productive. There were several items that stood out to me in chapter 9. Two of the biggest were about meetings and what the author called “Focus-Manna”. Working as a system administrator I couldn’t guess how much time I wasted in either pointless meetings or in meetings where the reason for the meeting had nothing to do with me. Most of the time I was forces to sit in the meetings by my supervisor and explaining why I did not need to be in the meeting was almost alway fruitless.

Time estimation is also a topic that applies many fields. Before returning to study computer science I went to school for cabinet making and carpentry. In the program there was a course dedicated to estimation. This course included the estimation of time(which is directly linked to cost) and material. One of the first things we were told as inexperienced estimators was to come up with the best estimate we could and then double it. Prior to taking this course I had been working in the field for about 2 years and found this to be pretty accurate. Now in the field of computer science I see the same issues with time estimation. I believe the root of most estimation issues is the tendency to over simplify the tasks. I like the point the author makes about making clear this is an estimate and not a commitment. One thing I learned in while working is to stand you ground on. Many times I would be working on a project and the supervisor would ask “How much longer until completion?”, I would then give an estimate of what I thought it would take me, the supervisor would then say “Well it shouldn’t take that long.” and proceed to explain why there time estimate is so much shorter. If I agreed that I should be able to complete the task within the shorter period of time I would almost never finish on time.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Sprint 6 Reflection

This reflection wraps up the final sprint. At the beginning of the sprint I was excited, we had a full description of the issue, knew the requirements, and had decided where to move the button. During the end of the last sprint I worked on adding a new item to the top menu, this was very easy. I ended up putting a place holder in the menu. The next task was to look into the how to only allow the button to be seen if there was a drafted form, this was also easy as the was the original behavior of the button. With the first to tasks seeming rather easy my focus changed to what needed to be done to move the button. I used grep to look through all the files and made a list of files I thought needed to be altered. Once I had this list, I decided to try removing the button from its current location, this cause issues. When I removed the single line containing only an open and close tag for the button, the entire site stopped working. After a short discussion with a member of a different team I realized the element I removed was responsible for some of the routing. My next aim was to determine what I needed to do to import the back to drafted form module in to the main dashboard module where the top menu bar was held. I tried several things to move the button and its code but with each attempt I found it caused a new issue. One of the problems I thought I had caused was the button no longer brought you back to the drafted form. In fact, when you clicked the button, it prompted you with a message saying there was an unsaved drafted form, re you sure you want to continue. This message was clearly out of place as the whole reason for clicking the button was to bring you to the drafted form. On top of the message being out of place, clicking either yes or no destroyed the form and left you on the current page. Not being able to pinpoint what I had done to cause this problem I decided to pull from the original AMPATH repository. After doing that, I realized the issue was not my fault but an issue the main project had.  I had on other team member try on his computer just to rule out my machine as the cause I opened a bug report in JIRA.

Over all I have enjoyed my experience working on a Scrum team. The on regret I have is not being able to fully commit my time to this one project. Once I have graduated, I do plan to continue working on the AMPATH project. It is nice working on an open source project that will impact the lives of people around the word.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.