Sprint 5 – Learning Reflection

Sprint 5 began with our solution to NGPOC-185 was pulled into Ampath.  We also started work on some new issues we assigned ourselves from JIRA.  In accordance with what we decided last week we picked two issues, one for each group of three.  Our group picked APTS-254 which was described as “User are requesting when a patient switches to 2nd Line the Viral Load Pop-up reminder should not pop until the patient has used the 2nd Line Regimen for 6 months.”  Just as we did with NGPOC-185, we decided the best course of action was to attempt to recreate the issue and then find where in the code the issue was located.  Neither individually nor as a group could the issue be recreated so we determined that we needed additional clarification on the issue.  I wrote a message to Ampath, but it took awhile to get a response, delaying our progress.  Before the sprint ended, we did get a response.  Apparently the issue was located in the ETL Rest Server, which we did not have before.  They directed us to the repository, but even with this new information we were unable to recreate the issue.  We will continue to work on this issue next sprint.

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

The Software Craftsman, Chapters 11 &12

Chapter 11 was mostly for people that are the interviewer at their company. It basically went over what an interviewer should and shouldn’t do to a potential candidate. For example, brainteasers don’t work to attract good developers, and doing anything that makes a potential partner look like a fool will make it so they don’t trust working for you. Again this is a chapter that isn’t helpful to me right now, but the information in this book may be more helpful further down the line in my career.

Chapter 12 talked about how to low morale can kill productivity and passion in developers, and also talked about how to bring passion back into a company. Mancuso talks about how, after awhile, some developers just give up on projects and become lazy because they just see their job (as he put) as “just a job.” This type of thinking definitely becomes an issue because then people are not meeting deadlines and can lead to wasting tons of company money. However, I don’t see an issue with wanting to make sure that you have hobbies and time that are separate from your work life. As long as you maintain a balance between the two it should be fine because I believe that if you fill everyday with the same thing, that will burn you out faster than anything else might. He then goes onto say how to bring back motivation to a low morale team. I like his idea of talking with people at the end of the stand-up meetings about new things they found. This not only gives people the opportunity to discover new posts or websites they have never heard of, but it also brings the team closer together.

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 Chapters 13 and 14

 

Chapter 13 is about the culture of learning. In this chapter, the author says that junior developers are lead to believe becoming a manager or architect is their natural career progression, but it all depends on what the developer likes, if they truly have a passion for programming they can always progress to a senior developer. The chapter goes on to list some things that can be done to create a culture of learning. Learning from others and sharing experience is important when trying to produce a culture of learning. The part where the author said that not career paths for a software developer are the same stood out to me because there is a lot of truth behind it. It all depends on the person’s wants and aspirations in determining their career path.

Chapter 14 is about driving technical changes. The chapter talks about how driving technical change is a hard thing to do. In order to be successful in doing this, we need to understand how to deal with all the different types of people we will need to interact with. Everyone has their own opinions, it is a matter of getting them to your way of thinking and showing them why your solution is the best solution for the problem. preparing yourself for the other peoples points of view is also critical if you plan on making a change. This way you can counter their arguments when they come up.

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

Sprint 4 – Learning Reflection

To start our fourth sprint we divided the NGPOC-185 issue into distinct parts so that everyone on our team could dig their hands into the issue.  We broke the task into six parts and everyone picked a piece they thought they would do best.  I was going to take everyone’s individual piece and combine them into the final solution.  Unfortunately, we were mistaken.  Our solution was incorrect because our approach was all wrong.  Over Spring Break one of the members of our group determined that the solution was much more simple than what we were attempting.  Once I returned from Spring Break, I had a chance to review his approach.  Apparently we were looking at the wrong thing and once we received some clarification the solution came together in a couple of days.

Screen Shot 2017-05-08 at 9.54.16 PM

Screen Shot 2017-05-08 at 9.54.30 PM

With our solution complete, we determined that these issues were not as complicated as we originally thought, and broke our group into groups of three.  This way we can complete twice as many issues per sprint.

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

The Software Craftsman Chapters 11 and 12

Chapter 11 is about interview anti-patterns. it talks about the interviewing practices that tend to lead to the wrong candidates being hired. One of the things that this chapter mentions is to not make yourself look smarter than the person that you are interviewing. You want to seem like you are their equal. Even though you may be smarter than them, you are still able to learn something from them. Conducting phone interviews is not the best way to interview candidates because it is hard to get a read on peoples skills and worth ethics. 

 

Chapter 12 is about the cost of low morale. When a company is struggling to get products out it is probably because your employees have low morale. Sometimes managers don’t talk to their developers so it can be hard for them to know what the manager wants from them. Also, when a manager doesn’t get on a personal level with their developers it almost feels like they are just your boss and not a friend. It is much easier to work for someone that you like rather than someone who you can just call your boss. Managers keeping developers motivated is important when it comes to producing results. 

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

Sprint 3 – Learning Reflection

This past sprint our class was assigned four issues on JIRA, an issue-tracking software. AMPATH set all of us up with our own login information so that we could view, assign, and comment on the issues.  The issue we wanted to work on was given to another group, so we ended up getting our second choice, called NGPOC-185.  The title of NGPOC-185 was “Logout not working when editing a form” and had the description “if you are in the middle of editing a form, but you decide to cancel and logout (may not be a practical case) , after accepting to cancel, it should log you out.”

As a team we determined that the issue was asking us to have a confirmation window pop up when a user tries to logout while they are editing a form.  So we figured our first step would be try to recreate the issue.  We booted up our local server and determined what the issue was describing.  Our next step was to find the code the corresponded to the issue.  After some searching we think we figured out where to begin.  We decided our best course of action was to read up on Materialize CSS and then attempt the issue next sprint.

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

The Software Craftsman Chapters 9 and 10

Chapter 9 is about recruitment. The author mentions how it is crucial for any software company to hire the best developers, and how this is hard to find sometimes. It also goes into detail explaining a typical job description and points out all the areas in which it can go wrong. When recruiters are looking for the best developers they should not be going on which ones have been doing it the longest. Sometimes it is hard to tell which candidate is the best developer. Finding developers that are passionate about what they do should be more important to a company than finding the best developer at the time. The developer that is passionate about their career will end up passing the developer that only cares about money sometime in the future. This chapter helps put into perspective the difficulties when going in to job searching. It shows that companies also have it hard when trying to find the best match for a position. 

Chapter 10 is about interviewing software craftsman. An interview is essentially a business negotiation. It is not just about finding a job and making money. More importantly it is about finding the best suiting job for YOU and the company. It is important that during interviews you do not let them do all the talking, you need to take the floor and ask them questions. A good interview can be looked as a informal chat between developers, not a interview in which someone asks question and the other answers. Eventually it can come to an pair programming interview where you need to showcase your skills. It is important that you do not dominate and do not be dominated. You need to showcase your skills while taking input and figuring out the optimal solution. This chapter is very important to be especially because I have started with the interview process in a couple companies. It shows me what I need to do in order to have a good interview and shows me what I should not be doing. 

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

The Software Craftsman Chapters 7 and 8

 

Chapter 7 is about Technical practices. This chapter focuses on a variety of technical practices and goes into how useful hey are. It also talks about the right thing versus the thing right. A large section of it is about Extreme programming. Test Driven development, continuous integration, pair programming and refactoring are all important practices a software developer should all be using. Also the author talks about how important it is to fic issues before they come up. This helps cut back on the time it would take to go back and fix the code when you are focusing on a different part of it. I think extreme programming is a useful practice that everyone should be using. It covers all aspects of programming and makes sure that the code is maintainable and usable.

Chapter 8 is about the long road. It discusses that you need to be focusing on what you can do to improve you and your career instead of hoping for a promotion. He also talks about autonomy, purpose and mastery when it comes to living a happy life. One can see how these things are more important than money for some software developers. This chapter is important to me because I am a strong believer that your happiness is more important than money in most situations.

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

The Software Craftsman Chapters 5 and 6

Chapter 5 is about heroes, goodwill and professionalism. One of this chapters focuses is the idea of learning how to say no. The author tells a couple stories about how a manager was always pushing for more rather than working with his developers and how that was a unhealthy work environment. Part of being a software craftsman is being in charge of yourself and your own career, this may mean saying no sometimes. But this does not mean say no all the time, because this can be looked as unprofessional. A good manager will put themselves in your shoes to see if what they are demanding of you is reasonable. 

Chapter 6 is about working software. This chapter talks about working software and the fact that working software is not enough. There is always a threat of something going wrong later on when the software is not maintained properly and developed properly. Don’t skip steps when you are developing software. This may be hard for some people because deadlines are constantly being forced. If something happens that you are not able to reach a deadline, it is better for you to talk to your manger about it so you are making sure you are producing code to your best ability. I can relate to this chapter because i have fallen in the trap of just producing software that works, rather than taking all of the steps I should be in order to solve  the problem at hand. This can lead to a disaster somewhere down the road. 

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

The Software Crafstman Chapters 3 and 4

Chapter 3 is about software craftsmanship. Software craftsmanship is a long term journey to mastery. It is a mindset where software developers chose to be responsible for their own careers. This means that they have to learn new tools in order to stay competitive. It is not test driven development, clean code, or specific technologies. This chapter also goes over the software craftsman manifesto which is not only working software, but well-crafted software. Not only responding to change but steadily adding value. Not only individuals and interactions but also a community of professionals. Not only customer collaboration, but also a productive partnership. These are all things that the software developer should strive for in order to achieve the title of software craftsman. 

Chapter 4 is about the software craftsmanship attitude. It is important that we continue to learn and develop in our careers. Most of the time this means to not to rely on your employers to provide you with everything you need to succeed as a software craftsman, this may involve some separate studying. The chapter goes into detail explaining technology specific, conceptual, and behavioral and revolutionary categories for software developers. We should be constantly reading up on new things that we don’t know how to do, and making we stay up to date on the latest technologies. I think this chapter is very important to every software developer when it comes to self-growth. I believe this is a way that people should live their life, not just their careers. 

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