Sprint 4: Reflection FanstasticFive

Our team continued working on NGPOC-184 issue. We changed up how the team should pick and solve issues.

Throughout Sprint4, I spent most of my time researching and trying to solve NGPOC-184 issue. I also tried to help one of the team member to connect to AMPATH test2 server. I received very helpful and informative links from Sudarshan regarding NGPOC-184 issue, but I still couldn’t come up with a solution for the issue. Although, Sudarshan was successful in solving the issue by himself with the help of AMPATH developer.

To increase our contribution to the AMPATH project, as a team, we decided to pick individual issues and try to solve it individually or with the help of chosen team members. Since Sudarshan contributed immensely to NGPOC-184 issue, he kept working on that issue. We tried looking for other issues, but they were all assigned. Couple days before Sprint4 ended, Dr. Wurst was waiting on get more issues from AMPATH team. Tan picked APTS-225 and is willing to let me work with him on this issue.

Sprint4 went by very quickly. We had small change of plans towards the end of the sprint, but everything else went great.

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 3: Reflection FanstasticFive

During Sprint3 I kept learning more and more about Angular2 because I still don’t have strong hold on the language. I got couple of tasks done successfully: I accepted invitation from Jira and successfully connected to AMPATH test2 server. Our group also picked NGPOC-184 issue, started researching and tried to solve it.

I watched couple of videos on Angular2 which extended my knowledge on Angualr2. I also started looking at the ng2-amrs code and tried to understand and navigate through the code. I spent most of the time on learning about Angular2 and navigating through the existing code. Our team started working on NGPOC-184 issue. We spent some time on figuring out when, where and how to approach the issue.  Sudarshan found an informative blog that pushed us to the right direction.

I do not know if it was the issue or it is just our team, but we still need to work on our communication. Most of the NGPOC-184 issue was handled by Sudarshan. The rest of team members spent most of the time on researching and trying to help. I remember Sudarshan saying that this issue is a one-man issue. So, it might have been the issue, but I’m looking forward to more collaboration with my team members.

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

Chapter 3 of The Software Craftsman is spent defining what is a Software Craftsman. The earlier parts of the chapter are spent on talking about the history of Software Craftsmanship, that is all very interesting but I’d like to discuss the Software Craftsmanship manifesto.

Not only working software, but also well-crafted software

Not only responding to change, but also steadily adding value

Not only individuals and interactions but, also a community of professionals

Not only customer collaboration, but also productive partnerships

So, lets take a look at this line-by-line. The first line states “Not only working software, but also well-crafted software”. I think we can all agree as some form of software developer this is the best thing to strive for. The question then becomes, how do we get here? Sandro makes a statement that is truly interesting. After describing what any good developer would know to be truly well-crafted software, Sandro states “In order to evolve applications, developers must not shy away from changing them.”. This statement is so intriguing to me because it simply makes sense. You can’t have evolution without change, and you want your software to evolve to “well-crafted”, right? Well in order to do that, you’re going to have to make changes to the code, sometimes that may be big. Other times it may be small.

The next line says we should be steadily adding value to the project. This is again something that no one can refute as a good thing. However, I think as developers, we many times find it hard to “Leave it cleaner than we found it”. As you are reading this I can almost guarantee that you are thinking back to a time where you made a bug fix, but that bug fix made things just a little bit messy. I am sure whatever reason you had for putting in that bug fix messy like that was valid. However, this starts becoming an issue when everybody working on the project adds some messy code here and there. Eventually the system becomes maintainable and it’s an unfortunate side-effect to us being humans. However, as software craftsmen we need to strive to not get caught in this net and constantly clean up the code.

The next line says we need to be a community of professionals. I really like this piece. I’ve worked with people on both ends of the spectrum (not in the software field). On one end there are people out there who will give you the bare-bones, need-to-know information to get the job done. I am unsure as to why anybody would want to do this. Flip the coin and I’ve worked with people who are delighted to share their knowledge and understanding of the given subject matter. I think mentor-ship is incredibly important. If no one ever mentored a young developer and didn’t pass down the knowledge that’s been attained over their long career, then the young developer is going to fall into all the same pitfalls that has plagued software development for years.

This final line in the manifesto, is essentially stating: In order to succeed you will need to act as a professional. It also talks about the flip side of your manager needing to act as a professional and expect you to act as a professional. We should want to strive to produce the best possible products we can and in doing just that, I think a lot of the time the customers or the employers are more willing to work with you through issues. They are able to see past you as their employee or contractor and begin to see that developing software is a partnership. In order to create good software there needs to be professionalism on both sides of the coin.

 

 

Chapter 4 talked about attitude of the software craftsmen. More so the chapter discussed our attitude towards pursuit of knowledge. The pursuit of knowledge should be a personal burden and not a burden you try and place of your employer. It is your sole responsibility to continuously improve skills and knowledge as a craftsman.

Many of the ways to improve this were discussed in an earlier blog covering “The Clean Coder” book. I won’t re-hash something I’ve already discussed. But as a brief summary, some good ways to extend your knowledge is through books, blogs, podcasts, training events, seminars, meetups and coding challenges.

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

Sprint 4 (3/9/17 – 3/28/17) Learning Reflection Blog

We are almost done with resolving our first issue as a part of the AMPATH team. Spring break was during the ending half of this Sprint so not much work was done during the break. Although the overall progression is pretty slow, it’s moving along at a decent (decent for an amateur scrum team) pace so I’m not complaining. Besides the first issue that we are close to completing, I started looking at another reasonably do-able issue from the Sprint Backlog so I am excited to start working on that issue once the next Sprint cycle begins. We don’t really have much to show for considering we haven’t completely “resolved” any issues yet and it’s been about three months already but it’s better than nothing. Like they say, slowly but surely!

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 Craftsmanship (Week 8)

This blog post will revolve around chapters 3 and 4.

Chapter 3 starts of with a more in depth explanation of what the title of the book means (The Software Craftsmanship). In the book, the author gave his take on what being a software craftsman is.

 Software craftsmanship is a long journey to mastery. It’s a mindset where software developers choose to be responsible for their own careers, constantly learning new tools and techniques and constantly bettering themselves. It is about putting responsibility, professionalism, pragmatism, and pride back into software development.

I like the part where the author had stated that a a software developer chooses to be responsible for their own careers. I believe that if you want to be a good developer, one should constantly be learning and keeping up with the trends and technologies.

Chapter 4 talks about what kind of attitude a software craftsman should have. One of the most important thing in this field is to be responsible. You as a developer must keep your self up to date with technology trends in order to stay relevant. The author then goes on to give us some tips on how we can keep up with the trends.

  • Reading books, blogs, technical websites
  • Keeping a blog to document and track progress

The last thing that the author talks about in this chapter is about time management. As we grow older, we find that time is not on our side. The author reminds us that there is always time to practice. We just have to limit our time with certain activities.

 

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

The Software Craftsman (Chapters 3 & 4)

Chapter 3 of the Software Craftsman book answers the question: what is a software craftsman? The book gives many definitions; the two that I like are:

  1. Software craftsmanship is a long journey to mastery. It’s a mindset where software developers choose to be responsible for their own careers, constantly learning new tools and techniques and constantly bettering themselves. It is about putting responsibility, professionalism, pragmatism, and pride back into software development.
  2. Software Craftsmanship is about professionalism in software development.

The rest of the chapter is about the history of software craftsmanship and the software craftsmanship manifesto. The manifesto is sort of like a guideline of what software craftsmen ought to do.

  1. Not only working software, but also well-crafted software.
  2. Not only responding to change, but also steadily adding value.
  3. Not only individuals and interactions, but also a community of professionals.
  4. Not only customer collaboration, but also productive partnerships.

Chapter 4 is about the attitude a software craftsman must have. Our careers are in our hands not in our employer’s hands. It is our duty to improve ourselves. I totally agree with this statement. I personally have access to O’Reily Safari Books and it a really good resource. There are many good video courses and live training courses. I signed up for the Design Patterns Boot Camp course that starts this Wednesday and I also watched Uncle Bob’s SOLID principles videos on his website. When I enter the professional world I plan to attend more live training courses.

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 Chapter 3 & 4 (3/28/17)

Comparing “The Software Craftsman” book to the “Clean Coder” book, there is a good amount of material that overlaps from one book to another. Chapters 3 and 4 introduces the idea of what software craftsmanship is and the attitude behind being successful at it.

The most important and useful piece of information from these two chapters was the idea that “clients don’t pay professionals to learn; use your own time and money to get better at what you do.” We as professionals get paid for the skills we have to offer so it makes sense that it is our responsibility to keep our skills sharp and up-to-date. If not, we slowly start to become irrelevant and people will no longer rely on us because our skills aren’t as sharp as it used to be. If you want to be paid good, then you better have a good skill set to show for; don’t expect a promotion if you have nothing new to offer to your employer. Think about it, why would anyone pay you more money for doing the same amount / quality of work?

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

Chapter 3 covers the topic of what exactly software craftsmanship is. The author generalizes it by stating its putting responsibility, professionalism, pragmatism, and pride into software development. He then goes on a long walk through of how software craftsmanship came to be and the history behind it. Basically software craftsmanship has been around since 1999 however it never really gained traction until about 2009 when the Manifesto was published online. The Software Craftsman Manifesto outlines four main values of a developer: 1) Not only working software, but also well-crafted software. 2) Not only responding to change, but also steadily adding value. 3) Not only individuals and interactions, but also a community of professionals. 4) Not only customer collaboration, but also productive partnerships. The author concludes with the main idea that software craftsmanship is a lifestyle and mindset of professionalism in software development and always striving to provide the best service to clients.

After reading chapter 3 I thought there were some really good points but I did think the history was a little drawn out for the reader. I agree with the manifesto the author laid out however everything he mentioned seemed to be common sense. It is also something that must be embraced by the entire business for it to be effective. While one developer could be a craftsman, it takes everyone to follow the manifesto for it to truly work and give the client the best experience possible. My favorite idea from this chapter was the ‘craftsman swap’ where developers from different companies would trade places and act as if they were a developer at another company for a week. This is a great way for teams to get an idea of what they could do better and sheds some light on how other companies are operating. Both teams benefit and can adopt the best practices from the combination of two teams. I can however see where competing companies may not want to have their competition directly working with their team to gain any kind of competitive edge. Overall, I think the Manifesto for craftsmanship holds good points any developer should be following and sets a higher standard for developers everywhere.

Chapter 4 covers the topic of attitude being a software craftsman. The author makes a point to make it clear that we as individuals are responsible for our own careers and continued learning. While it’s nice to work for employers who invest in their employees we are ultimately responsible for keeping ourselves trained and up to date. He goes on to talk about all the different ways we can keep up on our training so that we are always learning. First he mentions reading material in the form of books, blogs, or technical websites. The author does mention even beginner developers should keep a blog to document and track their progress. Next he talks about ways to practice. When practicing a problem it’s important to focus on how the problem is actually being solved and not just writing code that works. Katas which are short coding exercises or doing personal pet projects are also some suggested ways to get good practice in. Lastly the author touches upon time management. Many times we tell ourselves we are too busy but he insists to make time. We can do this by limiting habits like TV watching or social media use. He does make a point that there needs to be a good work life balance but to own your own career you must manage time wisely and keep your skills sharp outside of normal working hours.

After reading chapter 4 I noticed a lot of commonalities mentioned from Robert Martin’s Clean Coder. I strongly believe it is an individual responsibility to continue software learning at any career stage. Out of the ways mentioned I find myself following social media and blogs the most. With the speed that tools and technologies come out, blogs tend to have good early information and usually tutorials to help you learn. One thing I’m not sure I fully agree with is the Pomodoro Technique. While I think it may be useful for someone who’s off track, setting timers and keeping such a rigid schedule does not seem sustainable. Personally I know I would keep checking the time remaining which would hinder my focus. In conclusion my career will surely benefit from personal learning and proper time management skills.

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

Chapters 1 and 2 Software Craftsman

Chapter 1

One of the first things I noticed in this chapter and it
made me cringe is how people seemed to have thought back in the early 90’s in
how they measured seniority by how cryptic your code was. I am sure it wasn’t
everywhere but I remember people back then talking like that. How anyone ever
thought that was cool or what not is another issue for another time I guess but
wow memories come flooding back, not because I was a coder in the early 90’s
but I knew some and hung around them and I remember hearing stuff like this. I
laughed a few times as well in this chapter, especially when he was talking
about adding abstractions and design patterns all over the place and how today
it would be called overengineering and stupidity. It is amazing just how far we
have come I guess. He hits the nail on the head though in talking about choosing
your passion for work and what makes you happy. I see it in a lot of the young
folks today talking about oh how much money this and that, but never hear them
talking about finding something they would be happy doing. I never thought much
like that, of course I would like to make a lot of money, but if I am not happy
making it what’s the point?
I like his take on seniority as well and how it is transient
and relative. I think too many people in general judge seniority in numbers of
years and not quality of product. I have been many a place and seen people with
2 years of experience blow someone away that had 10. It is true though however
that there really is no senior or junior developers unless you reference what
senior or junior is as pertaining to a certain language I guess. It is
interesting to see how things evolve over the years in what our
responsibilities are or will be once employed. We need to be a sort of jack of
all trades in the sense that we will be doing many roles as we evolve up the
ladder. I am looking forward to see what the rest of the book has to offer.
Chapter 2

After reading this chapter I look at agile a new way. I
never gave much thought to the name until now. The definition of agile is “able
to move quickly and easily” hence the methodology being quick and short
feedback loops. I think that it is awesome that these guys got together and
basically changed the way we think and do. Doing things in short iterations
like this makes for smooth flow in my opinion and less of a chance of failing.
I love the first line of the manifesto, “Individuals and interactions over
process and tools”, it is quite the revelation to me and how I like to think.
It makes so much sense I wonder why it wasn’t done a long time ago. I mean if
everyone is involved and working together and “communicating” it is common
sense that thing should go smoother. Keeping people out of the loop on projects
makes for a mess that sometimes can’t be cleaned up. He is right in saying though
it doesn’t work unless there is a full transformation with everyone on board. I
mean that is like anything though in my opinion, you can’t half ass stuff or
you end up where you started and doing it all over again. It takes work, but I think
once the work is put in and results are seen it is a no brainer I would think.
The embracing of software craftsmanship is needed and I am beginning to like
that term. We are craftsmen and like craftsmen we should strive to become
better each day and utilizing the tools we can accomplish this.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Chapters 1 and 2 Software Craftsman

Chapter 1

One of the first things I noticed in this chapter and it
made me cringe is how people seemed to have thought back in the early 90’s in
how they measured seniority by how cryptic your code was. I am sure it wasn’t
everywhere but I remember people back then talking like that. How anyone ever
thought that was cool or what not is another issue for another time I guess but
wow memories come flooding back, not because I was a coder in the early 90’s
but I knew some and hung around them and I remember hearing stuff like this. I
laughed a few times as well in this chapter, especially when he was talking
about adding abstractions and design patterns all over the place and how today
it would be called overengineering and stupidity. It is amazing just how far we
have come I guess. He hits the nail on the head though in talking about choosing
your passion for work and what makes you happy. I see it in a lot of the young
folks today talking about oh how much money this and that, but never hear them
talking about finding something they would be happy doing. I never thought much
like that, of course I would like to make a lot of money, but if I am not happy
making it what’s the point?
I like his take on seniority as well and how it is transient
and relative. I think too many people in general judge seniority in numbers of
years and not quality of product. I have been many a place and seen people with
2 years of experience blow someone away that had 10. It is true though however
that there really is no senior or junior developers unless you reference what
senior or junior is as pertaining to a certain language I guess. It is
interesting to see how things evolve over the years in what our
responsibilities are or will be once employed. We need to be a sort of jack of
all trades in the sense that we will be doing many roles as we evolve up the
ladder. I am looking forward to see what the rest of the book has to offer.
Chapter 2

After reading this chapter I look at agile a new way. I
never gave much thought to the name until now. The definition of agile is “able
to move quickly and easily” hence the methodology being quick and short
feedback loops. I think that it is awesome that these guys got together and
basically changed the way we think and do. Doing things in short iterations
like this makes for smooth flow in my opinion and less of a chance of failing.
I love the first line of the manifesto, “Individuals and interactions over
process and tools”, it is quite the revelation to me and how I like to think.
It makes so much sense I wonder why it wasn’t done a long time ago. I mean if
everyone is involved and working together and “communicating” it is common
sense that thing should go smoother. Keeping people out of the loop on projects
makes for a mess that sometimes can’t be cleaned up. He is right in saying though
it doesn’t work unless there is a full transformation with everyone on board. I
mean that is like anything though in my opinion, you can’t half ass stuff or
you end up where you started and doing it all over again. It takes work, but I think
once the work is put in and results are seen it is a no brainer I would think.
The embracing of software craftsmanship is needed and I am beginning to like
that term. We are craftsmen and like craftsmen we should strive to become
better each day and utilizing the tools we can accomplish this.

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.