Sprint 5 Reflection

Another sprint in the books, and this time, as a team, we all worked on one issue together. During this sprint, the main difficulty was finding the file that the issue was in. It took us a couple of days using many tactics to find the file. A teammate decided to go on Github to track down the problem by scouring through similar problems. We finally found the problem, but it was very outdated, and the file structure to find that file was no longer the same, but we had an idea of where to look in the current file directory. After hurdling this obstacle, we were faced with even more obstacles. The next obstacle consisted of finding out that the file our issue was in was not in the original OpenMRS source code. It was in the NPM install files that they tell us to run through the terminal. I believe that in order to hurdle this obstacle, we must contact the developers to see what they think.

 

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 9 & 10

Chapter 9 covers the topic of developer recruitment. The author makes an immediate claim that job board type sites with the traditional job description are a bad way to hire developers. Many job postings list an abundant amount of technologies that aren’t even required to do the specified job. This immediately filters out some really good candidates. Listing years of experience can also filter out good candidates because years is not necessarily a measurement of knowledge. The author goes on to say that many larger companies continue to get developers similar to their “bad” ones because they are relying on their poor recruitment process. Getting rid of generic job descriptions and avoiding the mistakes mentioned, gives access to a wider range of potential craftsmen. This can also remove any obscurity the recruiters have with not understanding the true technical aspects of the job and prevent keyword matching. Another piece of advice given is that companies should avoid financial compensation for employee referrals. It creates wrong motivation and incentive to recommend a potential employee. Working with talented people who improve the quality of the work environment should be compensation enough. It is suggested that companies should always be proactively recruiting. Getting involved in tech communities and user groups is a good and cheap way to gain exposure to potential talent. By building a pool of candidates for future employment, the hiring process can move much quicker. Lastly, the author suggests that you look for passion above all else when selecting a new developer. Someone who blogs, contributes to open source, or attends conferences will likely see the employment opportunity as more than just a job. In summary, if you are currently dealing with “bad developers” look to change the recruitment process to hire the people you really need.

After reading chapter 9 I found a lot of the author’s suggestions and advice to be helpful for my future. While I agree with his points, many companies still post job descriptions like the ones he called out. For people who are unemployed it’s not always easy to find the perfect place to work never mind go through a selection process for a company that isn’t even hiring right away. I strongly agree with the author’s comments about not listing years of experience on a job description. It can filter out people who are newer but more current with a technology and keep people who have done the same exact thing for “X” amount of years. One thing I have noticed looking for entry level software jobs is that companies post long lists of specific technologies for required skills. I think it’s more important that a candidate demonstrates the ability to learn new things. Having a coding assignment as part of the selection process can allow candidates to show their adaptiveness to new technologies as well as give a current sample of work. I have also seen job postings for entry level or junior developer positions that require a lot of experience or many technologies. I can’t imagine postings like this can get very many applications as they are not practical. While I agree with the ideas in this chapter, the hiring process in the United States is still far from adopting them as the new norm.

Chapter 10 covers the topic of interviewing from both the company and candidate side. The author gives a helpful reminder that an interview is not someone begging for a job. It is a business negotiation with the goal of creating a good partnership. As the demand for software developers is at an all-time high, candidates do not need to settle for anything less than a good partnership. From the perspective of the company giving an interview the author makes several points. In general it is best to focus on the candidate’s enthusiasm, projects, and achievements and not necessarily hard skills like a particular technology. He also says to favor those who ask questions showing genuine interest in the company and their role. Lastly it’s important to not only give a clear outline of the open position but to make sure it matches what the candidate is looking for.  The author also gives advice from the perspective of the candidate. He suggests to take the time in the interview to analyze everything about the situation. Learn as much as possible about the work environment, hiring process, and actual role you’d be filling. A good interview should also have some key elements to it. For one, the interview should feel more conversational and not like a scripted test. You can’t truly show or find passion and talent with questions requiring yes and no. It is also suggested that some form of coding be part of the hiring process. This could be a pair programming session or a pre-interview coding assignment for filtering. A software developer should also be a part of the interview process at some point. Developers interviewing developers is beneficial for everyone. In conclusion a good interview will form a productive partnership that both sides are enthusiastic about.

After reading chapter 10 I strongly agree with the interview advice given by the author. In regards to asking questions in an interview, I can’t imagine I’d be very interested in a role that I didn’t want to know anything about. I also think it’s important to remember how much time you truly spend at work. Most of your time is spent on the job so I think the most important point is that you can see yourself being happy going to work every day. While I think it’s important to analyze the logistics of the interview, many times people can be very nervous going into an interview which can hinder the execution of their interview game plan. I believe a good interviewer will get the candidate comfortable in a conversation before getting to the important parts. Lastly, as a soon to be developer I think it’s important to remember the abundance of jobs there are in the field. I can’t settle for something that I won’t be truly excited about. It makes for a bad partnership and violates all the advice given by the author as a software craftsman.

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

The Software Craftsman Chapter 9 & 10 Blog (4/18/2017)

Chapters 9 and 10 were especially interesting because it talks in depth about recruitment and interviews; and what better time to learn about those concepts than a senior graduating in 1 month! I found it so relatable when the author criticizes the job description of companies who are asking for qualities that are not even implemented at the workplace.

I would search for entry level software developer positions and one of the requirement for applying would be +2 years of career experience. Like, seriously?! I don’t understand how companies who are looking for entry level software developers are looking for candidates with +2 years of career experience. Correct me if I’m wrong but entry level does mean “introductory” or “basic” right?!

Chapters 9 and 10 encouraged me to not just follow the money, but rather, work for a company you feel passionate about, Work for some place where you feel you are being heard and can truly make a meaningful difference! There was a line in chapter 10 that completely left me mind-blown at how true it was. “During an interview, it is important to understand that we are not begging for a job. We are doing a business negotiation.” This made me realize that you, as a developer, have something to offer. You are not “asking” for a job, you are negotiating how much you believe your skill set can be worth to employers!

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.

Software Craftsmanship Chapter 3 & 4.

Chapter 3 of this book really translate what software craftsmanship is. It gave us a number of definitions including one from Wikipedia. Each definition shows a different perspective and what stuck out to the most was looking at software craftsmanship on a personal level. The book defines this as

a mindset where software developers choose to be responsible for their own careers, constantly learning new tools and techniques and constantly bettering themselves.

I see this being the most constructive definition or how software craftsmanship should be defined.  If we have this mindset then everything else like team work and professionalism should fall right into place. This also extends into chapter 4 because its about attitude and how software developers should represent themselves. No matter how much we rely on the workforce to gain experience, we have to realize that were in charge of our own careers and our advancement within it.

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

Sprint Reflection 5

We split into teams and it turns out that it was a good decision. This way we can tackle more problems than before. We are working on three separate issues. We are close to being able to push for our current issue but not just yet. Working on the button to fit into a better location is our priority because we have already made it so that it stays in place, even if the page is being scrolled. We are planning to put it near the top. It should be finished by the end of the sprint with the requirements the developers wanted.

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

Chapter 7:

This chapter talks about many technical practices and how useful they are. It also talks about how developers struggle to convince others to adopt certain practices because they are unable to explain the usefulness of them. Even though they might be useful for one reason in an area doesn’t mean they will also be useful in another. Also adopting new practices is always a struggle. It takes time to get adjust and get used to a new way of doing things and reforming habits. We also get into the importance of fixing new problems and bugs that occur as fast as we can to try to reduce the pain that we will have to deal with later. Making sure every time a change is made, that everything still works together is important. It helps save time and makes you much more efficient. Most of all we need to know what section we are trying to improve ourselves in. Because without that, you wouldn’t even know what practice to use. I can relate to this because I didn’t realize that different practices could be better utilized in different situations and I thought I could have just stuck to one until a better one came out.

Chapter 8:

This chapter talks about the steps to make a career and advancing in it, not getting stuck at your job. Hoping for a new promotion instead of asking yourself if what you’re doing is still helping yourself grow and love your job with the want to gain knowledge and not just being an overqualified manager that doesn’t do anything new. These things fall into three sections, autonomy, purpose, and mastery. I can relate to this because I never want to get stuck at a job, especially one I didn’t like. A job where I wasn’t learning anything new or contributing much. I would want to keep moving if needed and find a new place where I would find that I contributed to more.

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.

Learning Reflection – Sprint 5

We successfully made the pull request and merged the NGPOC-184 branch to the AMPATH master branch. The most important thing that I learnt was how to squash commits. Overall, this was the most productive sprint we had so far.

The thing that I think could be done differently the next sprint is how we divide the tasks. We did not know how to divide the NGPOC-184 issue into tasks so that everybody could work on it. What I learnt is that each issue could be divided into the following tasks:

1) Research ( How to solve the issue ?)

2) Solve the issue ( Somebody writes the code and pushes the changes to group                                                     repo. Can be done collaboratively.)

3) Fix npm lint errors ( Somebody fixes the lint errors)

4) Squash commit and make pull request.

5) Inform AMPATH team to do QA tests.

I plan to divide our next issue into the tasks above. This way our issues are solved much faster.

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

Chapter 7 of The Software Craftsman discusses some important technical practices.  It also discusses the topics of pragmatism and accountability, as well as tries to help developers understand these practices.  Some of the practices that this chapter talks about is, automated testing, test driven development (TDD), continuous integration, pair programming, and refactoring.  Something that was interesting about this chapter was that it discussed how as a developer you need to figure out what practice you personally are going to adopt.  You don’t need to adopt every single practice, and that’s very important to remember. You need to figure out what works for you individually.  Of course following these practices will be beneficial to overall cleaner code.  However, that doesn’t mean that following all of them is the best way to do things.  I learned that keeping yourself focused on the business value will help to make sure things go smoothly for you.  Overall, this chapter wasn’t one of my favorite but it had some useful information.

Chapter 8 of The Software Craftsman is about the long road of your own career and your own happiness/success.  The author discusses how you need to focus on your own goals and your own path as a developer.  If you aren’t happy with your current status then it’s your own responsibility to change that.  You need to be willing to try new things and create new opportunities for yourself.  Keeping up with the latest technologies is very important and making sure you are at the height of your success.  However, at the end of the day you need to focus on your own goals.  As a developer you should never settle just because you are at a certain spot in your life.  You need to keep reaching to your goals and work hard to get there.

I really enjoyed reading chapter 8 of this book.  It made me think about my own personal goals in life.  I want to get to a place in my career where I can be a confident and independent developer.  Right now I tend to question and second guess a lot of the work I do.  My goal is to have enough technical knowledge and self confidence to be proud in the work I do.  This chapter reminded me how important it is to keep up with technology to make sure you are producing the best work possible.  Overall, I liked this chapter and I could tell that the author felt passionate about the things he said.  Your career is your own journey and you should always remember to make sure it’s exactly what you want.

 

 

 

 

 

 

 

 

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

The Clean Coder, Chapter 13 & 14

I read two chapters that are very important for starting a professional career in the software industry. Chapter 13 Teams and Projects, explained the importance of gelled teams for successful projects and to some degree for successful businesses. Chapter 14 Mentoring, Apprenticeship, and Craftsmanship, elaborates on the need for teaching, training, supervising, and reviewing new computer programmers coming into the software industry.

In chapter 13, the author talks about a very important aspect of working in a team that is known as “gelled team”. In my academic career, I have personally experience both gelled and un-gelled teams. I strongly agree with the author that gelling is important for teams to work together, collaborate and communicate. Once team is gelled then they can plan better, they can solve problem together, and get things done together on time. I worked in a team where all the team members got along very well and understood each other. The result was that we worked together, supported each other, covered for each other and in some cases demanded from each other which resulted in quality work and on time delivery. In another group, all the team members did not bond together ever since the formation of the team. It resulted in disparity, miscommunication and unfinished work which badly reflected on the entire team.

In chapter 14, the author covers a topic that every rookie in any field is desperately searching for. I personally believe that a person learns a great deal from his mentor. That is why finding a good mentor that will teach you and makes a craftsman out of you is very hard. I believe to find a good mentor one must be a great apprentice first. Apprentice must be honest, hard-working and full of positive energy. Apprentice also needs to be respectful to gain his mentor’s trust and confidence. Only a great apprentice can become a great mentor and a great mentor can become a great craftsman.

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 Clean Coder, Chapter 13 & 14

I read two chapters that are very important for starting a professional career in the software industry. Chapter 13 Teams and Projects, explained the importance of gelled teams for successful projects and to some degree for successful businesses. Chapter 14 Mentoring, Apprenticeship, and Craftsmanship, elaborates on the need for teaching, training, supervising, and reviewing new computer programmers coming into the software industry.

In chapter 13, the author talks about a very important aspect of working in a team that is known as “gelled team”. In my academic career, I have personally experience both gelled and un-gelled teams. I strongly agree with the author that gelling is important for teams to work together, collaborate and communicate. Once team is gelled then they can plan better, they can solve problem together, and get things done together on time. I worked in a team where all the team members got along very well and understood each other. The result was that we worked together, supported each other, covered for each other and in some cases demanded from each other which resulted in quality work and on time delivery. In another group, all the team members did not bond together ever since the formation of the team. It resulted in disparity, miscommunication and unfinished work which badly reflected on the entire team.

In chapter 14, the author covers a topic that every rookie in any field is desperately searching for. I personally believe that a person learns a great deal from his mentor. That is why finding a good mentor that will teach you and makes a craftsman out of you is very hard. I believe to find a good mentor one must be a great apprentice first. Apprentice must be honest, hard-working and full of positive energy. Apprentice also needs to be respectful to gain his mentor’s trust and confidence. Only a great apprentice can become a great mentor and a great mentor can become a great craftsman.

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.