Chapter 9 talks about recruitment, essentially how recruiters should go about searching for qualified developers. One of the problem with finding developers is how recruiters write their job description. Adding things like years of experience, academic background, certifications is how most companies job description looks like. I have done a lot of job searching in this field and i can agree that most of the description are just specific requirements needed from developers. They fail to focus on the companies culture and values and that is why they are not satisfied we developers they’ve hired.
Chapter 10 continues the previous chapter and talks about what to look for in an interview. Just like a job description should not always list specific requirements, a developers resume shouldn’t be just about knowledge and years of experience. During an interview, recruiters should be looking for passionate developers who are willing to learn or try new things. Those are the developers where if you put them in the right environment, they can really shine. One thing i can agree with from this chapter is that developers should interview other developers. A good developer will know what their company needs and what to look for; they will hire developers that are even better than they are.
Our group have reached the end of sprint 2 with a lot of accomplishments. We are all connected to the AMPATH server and have completed our stories on Trello. This sprint period was a great one for my team.We received the result of our peer review and it was pretty comforting to know that we’re all content with the team’s progress. We have improved individually and have manage to strengthen our teamwork and communication. During this period, Professor Wurst provide a set of diagrams that shows us how we can successfully manage version control. We forked the latest version of the AMPATH project and cloned it on our computers. One of us has created a remote repository for the AMPATH project so they can pull the latest version for the rest of the team. We also have a TeamOrganization repository where we will have our version of the project with the latest changes.Since we’ve connected to AMPATH, I have edited the project on WebStorm to get familiar with it however, i haven’t made any significant change. For the next sprint our team hope to be writing some Angular and dive into the project.
During the first week of this software development course, we took the time to form teams that will work well together. Most of the class time was used to get comfortable in our teams and prepare to work on our AMPATH and openMRS projects. We are using slack to communicate with our groups as well as the rest of the class. Although I have never used slack in the past, I find it very useful and it is an efficient way to stay connected and share information.