The Software Craftsman 9 & 10 Week 12

The first section of the reading talks about the hiring process and what you should and should not do. If you already have a team of unorganized developers, bringing in another one will not help your situtation only make it worse. There should be little to no job description, it should be vague as it attracks more abstract minds. You want to hire someone that does not need constant direction and can learn things on their own. You should be hiring developers that are passionate about what they do.

The second part of the reading goes over the interview process. When in an interview make sure you ask a lot of questions about the company and get to know their process and how they treat developers. If you are a software craftsman you should not just be looking for good pay and cool projects, you should be looking at what will make you a better developer.

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

Sprint 5 Reflections

In this sprint we were given more issues to fix. I have become very used to JIRA, it’s not a hard system to learn. Some issues were taken by individuals in the group and other issues required the whole group to help. In the next sprint I think it would be helpful to figure out which issues are easy enough for one person to fix and which issues would need more than one person, still I know this is hard as we only have 2 hours a week to work together. I’ve also been learning a lot of CSS and HTML which is necessary to fix these issues.

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

The Software Craftsman, Chapter 1 & 2

For this week, I read Chapter 1 Software Development in the Twenty-First Century and Chapter 2 Agile, from the book title The Software Craftsman by Robert C. Martin. Chapter 1 explains how the software developers have evolved over the years and what it means to be a developer of the 21st century. It also focuses on the measurement of seniority in the field. Chapter 2 flashes light on delivery of software projects technique known as Agile. Author explains the meaning, purpose, adoption, ups and downs of what it means to be Agile. Author also mentions his contribution, suggestions and experience with Agile system.

One of the interesting fact that I noticed in chapter 1 was how the definition of seniority in the computer programming world has changed. In the beginning era of the author in the field, seniority was measured based on your understanding and writing of complicated code. If no one understood your code; you were automatically considered a senior. In the 21st century, seniority is not measured just by writing good code and be familiar with a language or framework. In the modern era, with seniority comes more responsibilities. Modern developers are expected to participate in all aspects of software development and business. Developers responsibilities includes speaking to customers to find and help them with their needs and wants, watching out for the best interest of the business, taking part in designing, producing, testing, and deploying software process, estimate time and costs, presenting to clients, and many other places that will result in greater customer satisfaction and successful company/business. In simple words, developer is no longer a person sitting in a cubicle and writing code with no involvement in other business activities.

In chapter 2, author goes through the software delivery technique known as Agile. Author makes it very transparent since the beginning of the chapter that Agile is not just one thing, but rather, it is a combination of methodologies and techniques. To understand the full motive of Agile, I personally liked how the book explained the two main groups of Agile. First, process-oriented discipline, which focuses on how the teams and organizations should work, collaborate, and organize. The purpose of process-oriented discipline is to keep focus on what is important and valuable to the business. Second, technical-oriented discipline, which focuses on the challenges of developing, growing, maintaining, and delivering the product/software. The purpose of technical-oriented discipline is to focus on the quality of the product/software. These two groups explained the agenda of why a business would adapt to Agile from their previous practices.

 

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

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

Reflection: Sprint 5

It took couple of days to trace down our new issue ‘APTS-296’. We all, as a team, had difficulty of tracing through the code. The main hindrance was the huge code base of the OpenMRS project.

We finally were able to fix the issue, and ran it successfully on the AMPATH test server 2. But the thing we are currently getting suck in order to push our changes is the module we modified is not a part of ng2-amrs src code. It seems to be using a 3rd party npm-plugin which is located under ‘node_modules’ outside of the src code folder.

We must ask AMPATH developers if we can edit the npm modules, if yes, then how.

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

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 5 & 6

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

Chapter 9 was all about how to recruit good developers; it was a very interesting read. The author explains what is wrong with the recruitment process in most companies and how to fix it.

One of the major issues with recruitment today is that companies recruit developers just by their resumes and keywords in them. They value keywords ( whether a developer has worked is some technology for x years) rather than whether the developer is passionate about development.

It is very hard to judge whether a developer is passionate about developmen or not. One of the ways that the author judged passion was whether the developer had a gitHub accout, had contributed to open source projects, have a twitter account, have a blog, or have spoken at conferences.

I totally aggree with the ideas in this chapter. Most companies that I interviewed with were more interested in the keywords in my resume than actually accessing whether I had the knowledge, aptitude and passion for software development. Some others asked me stupid obscure questions related to data structures and algorithms that I don’t have at the top of my head at all times, but could solve them if I was given some time to think.

Chapter 10 was about the software developer interview process. The main thing that I learnt from this chapter was that interviewing is like a business negeotiation. The company has needs and problems to solve and the software professional can help the company solve them. The software professional needs to understand the risks and rewards of that negeotiation before signing any contract. The software professional has a reputation and anything that can damage that reputation must be considered a risk.

The rest of the chapter was about how to properly interview a candidate.

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

Chapter 9 is the first chapter of Part II of The Software Craftsman.  This chapter discusses what companies can do to attract great developers during the recruitment process.  Many companies will post a traditional job description along with the criteria that you should have ____ years of experience.  The chapter states that companies may be pushing away great developers that would be extremely beneficial to the company by their recruitment process.  One point that really stuck out to me is that many jobs require so many years of developer experience.  I have always thought this truly made no sense.  A second year software developer could be much better and have more skills then a software developer with 12 years of experience.  Seniority is not a good way to judge the quality of a worker.  Another good point the author talked about is looking for a developer with the passion.  Having a passion for something will mean that you are giving it your all.  A developer who loves what they do and wants to succeed will always be better then someone who just does enough to get the paycheck.  Overall, I enjoyed reading this chapter.  It was interesting to get some tips on how companies should view you as a developer, rather then how you should view yourself like in the previous chapters.

Chapter 10 gave advice on the interview process for both the companies and the candidates.  The author stresses that an interview shouldn’t be an integration of the candidate, but instead a business negotiation where both parties reach mutually beneficial agreements.  I really enjoyed and agreed with the whole idea of this chapter.  I am always extremely nervous for interviews and feel like they are testing my every word to make sure I say the right thing.  However, it really shouldn’t be like that.  An interview,  on the side of the interviewer, should be a way to get to know your possible soon to be employee and see if they are a right fit for the job.  If you give a formal “by the book” interview, someone coming in is going to answer like a robot and say what you want to hear.  I really hate how so many companies expect you to have the perfect answers to every question.  If I ever personally give an interview, I will make sure to make the candidate feel comfortable and like they don’t have to speak like they are reading from a textbook.  Another good point the chapter made is that when giving an interview you should be more focused on the candidate’s passion, willing to work, and previous accomplishments then what skills they currently have.  Someone who is enthusiastic about learning new things will be able to pick up quick on any skill they may not have going into the job. When I first got accepted to my internship as a software engineer, I was only a freshman and honestly had minimum technical skills.  I was honest with the interviewer, but I also was clear that I was willing to put the time and effort into learning anything that I needed to.  I ended up getting the job, even though I wasn’t the best at everything.  Now I can say, as a senior that I know so much more then I did during my interview as a freshman.  I am willing to keep this mindset throughout future jobs.

 

 

 

 

 

 

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 Software Craftsman, Chapters 5 & 6

Chapter 5 of The Software Craftsman has the exact same message as Chapter 2 (about how to say “No”) of The Clean Coder. Basically boils down to make sure you understand what you and your team can handle in terms of projects, and stand up to management if your team cannot handle the task. Also make sure that what you are working on is transparent to, not only, your team, but the managers and business people as well.

Chapter 6 goes on to talk about how developers should be in the habit of writing clean and maintainable code that won’t have to be refactored later. If the code does end up needing to be refactored, the previous developer show have been professional enough to have made unit tests for that piece of code. This way new developers are not scared to break the system since they know that they can easily run some test to find out if the new code works the same (or better) as the old code. The main thing that I got out of this chapter (because most of it is repeated in The Clean Coder) was when he talked about working with legacy code. It feels like an obvious answer, but I never thought of taking a small portion of the code, figuring out what it is suppose to do, and then writing a unit test for it (if it doesn’t have one yet). Doing this will not only make it easier to understand the code, but it will let you clean and refactor the code easily.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.