The Software Craftsman 1 & 2

Chapter 1: Software Development in the Twenty-First Century

Due to the ever-changing nature of software development seniority is not exactly the best way to check someone’s skills. The field itself needs more flexible coders and having skilled individuals that know nothing about new and upcoming techniques is the opposite. I definitely agree with the way the author approaches the topic of seniority and its lack of correlation to skill set. I do not have much experience in this field in a job sense but abstractly it makes sense.

Chapter 2: Agile

The agile method is one way for businesses to obtain the flexible nature looked for when trying to be competent. But this can be a bad way to think about it because in practice companies tend to give attention to the processes and the meeting but forget that they still need good software craftsmen and craftswomen to turn out good software. If you adopt the meeting but not the necessary mastery then you will still have bad software but get to go to scrum meetings. This to me is a clear cut way to look at agile. Like in one of the scrum books that detailed a story about indigenous people trying to get plans to come back it makes sense that having meeting does not always get you the things you are looking for.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Reflection Sprint 6 (Final Sprint)

There are a lot of things that I was hoping to accomplish during this class some were just pipe dreams, some were attempted, and some actually got done. We will get to that at the end, but first the last sprint review.  During this sprint, we were hoping to finish and commit our bug fix. Unforchanatly this was not the case. Due to work and other classes projects and assignment we were unable to accomplish this feat. So instead of talking about what could have been, I will detail our thoughts on this issue and some potential ways of accomplishing this.

We ran into a bit of a wall again during this sprint. At my internship, I learned that they use a module for messaging the user that every part of the web app can use. This is what I was looking for in our capstone project but I was thoroughly stumped. I couldn’t figure out how the web app was sending info to the users some were using inline text in the HTML files, but others were calling it from the database I believe. So using what I learned from earlier to ask for help I asked for help. Well, this proved to be a huge waste of time because I received no answer. So I delved into the problem myself. We were looking for a universal module that handled messaging that we could call to display the message. What I came up with was trying to use the display error message module but this only lead to a large red box within the edit contacts page. Then I started to try and implement an observer pattern where the edit contacts page would be the subject and the contacts page would be an observer. So when something changed within the edit contacts module the contacts page would open small HTML box that would supersede the other divs and have a line of text “contacts have been saved”. Unforchantly I could not finish this within the sprint.

Leaving this class I have gained some helpful knowledge. First and most importantly I have gained some knowledge with web development and I would like to look more into this as a possible direction for my future career.  Secondly, I had a lot of fun using angular 2 and learning javascript. Lastly but equally important I have learned of some great tools that can aid in development like slack, trello, web pack, and web storm.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Reflection Sprint 5

Sprint 5 was when the team split. As in split into pairs to tackle the 3 different issues we pulled down. The first was the original button problem, the next was an issue having to do with a colored box that appeared next to patients to show status aka dead/ alive, the last issue was the one that I was working on which had to do with displaying a message when contacts were saved. So kyle found the function called to save the contacts. This already put us to a good start. As a test, we placed a javascript alert into the function to see if it was, in fact, the right function. The test was a success when web pack compiled with our added change the alert box appeared. Alright, this was fine but this alert was not within the web app so we decided it was not the right way to accomplish this. Another way that we approached the fix was to recreate the box that was shown when the edit contact button was clicked. Unforchanatly we did not accomplish this within the sprint and it had to be put on the backlog until the next and final sprint.

At the end of this sprint, we are heading into finals territory and papervile. What I  mean by this is that other classes are starting to assign final projects, papers, and exams. This means we will have less time during our last sprint to actually accomplish a fix for this issue. I hope to push a fix to the product because it will be a very good thing to point to for experience for a future job.

If I were to do this sprint over again I would start working on the issue sooner. This has been an ongoing problem for me throughout college, procrastination.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman: Chapters 15 & 16

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 13 & 14

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

Chapter 7 addresses a number of technical practices such as TDD, pair programming, SCRUM and their usefulness in improving our software delivery process. These agile methodologies are about delivering value to customers in the shortest time frame possible. Even though these practices are very effective in the software development process, it is difficult to convince manger to adopt them. Many companies do not use these practices because they fail to identify why they need them, when to use them, or simply does not believe that they are effective. It is not easy to get developers to adopt to these practices because there is a learning curve and it will take some time to understand. To figure out which practices to use, first we must know what area we need to improve and what we are trying to achieve.

Chapter 8 is titled “The long Road”. This chapter is perfect for aspiring developers because it talks about what to look for when choosing our careers. It summarized the career requirements into three things autonomy, mastery, and purpose. Having a successful career is not easy; we must figure out where we want to be and work hard to get there. We must treat every job as an investment to craft the career that will makes us happy. And if you are among the ones that do not know where they want to be, this chapter has a lot of suggestions to create options that can help decide the next step. Things like attending conferences, blogging, studying new things, and networking with other developers and business-people can open a lot of doors. Our career is important and carefully crafting it is the best way to reach where we want to be.

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

The Software Craftsman Chapter 5 & 6

Chapter 5 of The Software Craftsman titled “Heroes, Goodwill, and Professionalism” essentially covers the communication between the client and the programmer.

There is a limit to satisfying the clients needs. From their perspective, they are not aware of how difficult and elaborate the process for a software project is. They usually have a demand and expects immediate and accurate results because after all that is what they pay us for. However, how we handle situations like this in this field is what determines our level of professionalism. It is our job to communicate with our clients and say “no” when they have unrealistic requests. We need to be upfront on what is possible, what is not, and set realistic deadlines so we can have enough time to work with no pressure. If we fail to communicate, then we end up looking unprofessional.

Chapter 6 is title “Working Software” and it is about keeping the quality of our software as polished as it can be. We must never sacrifice quality for the sake of meeting a deadline; that is bad practice. Our software must be written well enough to adjust to changes, otherwise we will become “hostages of our own software”and that will hinder the business progress. This makes perfect sense because as technology advances, our software needs to be able to adapt quickly. Adding new features should be implemented into with ease if we have good quality software. I like how Sandro relates code to a garden. He mentions that ” with basic and regular maintenance, the garden will always look great but if we neglect it, even for a short period of time, it will require much more effort to make it look good again”. I think this comparison accurately describes how we should treat our code. The same thing can happen to our code if we neglect it; it will deteriorate or loose quality and will require more work to regain quality.

 

 

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

Sprint 6 Reflections

In this sprint no bugs were able to be solved. Not much was done as the semester is coming to an end. Instead of working on bugs or learning more about Angular 2 etc, we have been discussing the final project. I have not learned anything new and plan to work on the final project.

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

Software Craftsman ( Chapters 13 & 14)

Chapter 13 is all about creating a culture of learning at your company. Here are some of the things that the author thinks can be done to improve the morale and create a culture of learning:

  1. Start a book club.
  2. Have a tech lunch.
  3. Have group discussions.
  4. Conduct group code reviews.
  5. Have hands-on coding sessions.
  6. Start internal communities of practice.
  7. Encourage pet-project time.
  8. Engage with external technical communities.

Creating a culture of learning and motivating developers is important for a company as it directly impacts the code developers write. Ultimately, this depends on the developers; hiring passionate developers and providing them with a good environment would improve the innovation of the company.

Chapter 14 is about how to convince skeptics into adopting new practices or changing the culture. The first step according to the book is to identify the type of skeptics. The following are the types of skeptics the book talks about:

  1. The uninformed.
  2. The herd.
  3. The cynic.
  4. The burned.
  5. The time crunched.
  6. The boss.
  7. The irrational.
  8. The indifferent.
  9. The wronged.
  10. The inept.
  11. The ivory-tower architect.
  12. The insecure.
  13. The fanboy.

The chapter goes on and on about how to convince these skeptics to adopt something. Overall, what I got out of this chapter is that I must be good at what I do, I must communicate clearly, and I must establish trust to drive change.

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 13 & 14 Blog (5/2/2017)

Thanks to chapter 13, this is now going to be my quote of the week (maybe month): “bad tests are worse than no tests at all”. Am I the only one that’s blown away at how beautifully true that is? I hope not.

Anyways, I enjoyed the author’s take on creating an environment and culture of learning within the workplace in this chapter. It’s quite simple really; people tend to be more passionate and driven about their work when they don’t feel as though it is “work”. Remember as a kid how you always hated to do chores or clean your room? Well, if you hated doing those things, will you be excited or looking forward to having to do it every single day? Probably not. Now take that example and apply to developers in the workplace. If developers don’t like or enjoy writing tests, most likely they are not going to look forward to doing it. Even if they end up having to do it, you can almost guarantee that they are going to put minimum effort into it. Creating a culture of learning fixes this problem because if you can get developers to love what they are doing or learning, they are going to love doing their “job”.

On a smaller side note, chapter 14 was a fun chapter. It describes all the possible types of developers you might encounter that opposes the idea of new tools or practices and ways of going about convincing them to give the new tools/practices a chance. I feel as though I am going to subconsciously assign all my colleagues one of the titles mentioned in this chapter when I get my first real-world job as a developer (hahaha)

Random but relevant ending remark: You know, in a strange way, it kind of feels heroic to be a software craftsman. They’re like the Superman of Software Development…

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.