Software Craftsman Chapters 9 and 10

Chapter 9

There a lot of good
point in this that I never gave thought to. I don’t believe I will
be in a position to hire anyone for a while, but this chapter gives
some good tips on recruitment. He makes a good point in how companies
don’t get better because they are hiring the wrong people or
advertising the wrong skill set etc. In my limited experience looking
over job boards fr the CS field there does seem to be a lot of boiler
plate style templates. I also notice that they are usually looking
for x number of years experience in such and such and he is right
that the number of years is not a very good judgment tool and
experience. I have seen people which less time in a language that
know 10 times more and are that much better than people with 10 years
experience so it an uneven gauge. I also agree that companies should
be involved with the community and have seen companies that do this.
I use the web application meet up and go to presentations and talks
by various companies in the field and they are great for networking
as well as talking to potential new hires and such. It is also good
to see for the person who is looking for a job in that they get to
see what the company is all about and the people that work there.

Overall I think this
chapter was well put together and there are a good amount of tips for
the employer as well as future employees. I will probably refer back
to this chapter in the future.

Chapter 10

I like how he
described the interview as a business negotiation. I never thought of
it like that, but that is indeed what it is. The company has its
outlooks and is looking to keep up revenue and the prospective
employee that could possibly help in achieving said goals and or
challenges. His points on the hiring companies perspective is good. I
feel like that when hiring people you would want hem to ask questions
about the company. It shows interest as well as commitment to the
company in a sense because they took the time to research th place
and find out things about it so they could ask questions. There are
time though that maybe the questions they had were answered during
the interview, but still that should be stated. There are a lot of
good points, but a lot are also in my opinion common sense like
paying attention to how enthusiastic the person is when talking about
technology or their previous jobs and experience, as well as project
thy have worked on. If you have a dull unmotivated rock sitting
opposite you, you may want to end it there.

I would have never
given much thought about paying attention to what the interviewers
role in the company is, but he makes a good point about interviewers
that aren’t developers and are instead project leads or managers. I
would have never thought that might mean that developers may not be
empowered to make decisions. The single interview process is also
interesting and worth noting. It would not have dawned on me that the
company might be in a hurry and doesn’t take the time to hire the
right people. I think overall there are some great points here. I
like how he describes a good interview and I couldn’t put it better
myself. “A good interview is like a good an informal chat between
passionate developers.” I have been on interviews like this and
have been hired. They are good because both parties are at ease and
it makes it easier to be open about yourself. I agree as well about
it being a mistake to hire someone without seeing them code or their
code at least. It can give a good glimpse at their confidence and
experience as well as decision making skills and the ability to take
constructive criticism. Bringing your computer I don’t think I
would have thought of, but it is a good idea so they can see what
tools you have and use etc. Last but not least I can’t agree more
with developers must interview developers.

Overall another good
chapter with a lot of good information that I will probably revisit
in the near future.

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

Software Craftsman Chapters 9 and 10

Chapter 9

There a lot of good
point in this that I never gave thought to. I don’t believe I will
be in a position to hire anyone for a while, but this chapter gives
some good tips on recruitment. He makes a good point in how companies
don’t get better because they are hiring the wrong people or
advertising the wrong skill set etc. In my limited experience looking
over job boards fr the CS field there does seem to be a lot of boiler
plate style templates. I also notice that they are usually looking
for x number of years experience in such and such and he is right
that the number of years is not a very good judgment tool and
experience. I have seen people which less time in a language that
know 10 times more and are that much better than people with 10 years
experience so it an uneven gauge. I also agree that companies should
be involved with the community and have seen companies that do this.
I use the web application meet up and go to presentations and talks
by various companies in the field and they are great for networking
as well as talking to potential new hires and such. It is also good
to see for the person who is looking for a job in that they get to
see what the company is all about and the people that work there.

Overall I think this
chapter was well put together and there are a good amount of tips for
the employer as well as future employees. I will probably refer back
to this chapter in the future.

Chapter 10

I like how he
described the interview as a business negotiation. I never thought of
it like that, but that is indeed what it is. The company has its
outlooks and is looking to keep up revenue and the prospective
employee that could possibly help in achieving said goals and or
challenges. His points on the hiring companies perspective is good. I
feel like that when hiring people you would want hem to ask questions
about the company. It shows interest as well as commitment to the
company in a sense because they took the time to research th place
and find out things about it so they could ask questions. There are
time though that maybe the questions they had were answered during
the interview, but still that should be stated. There are a lot of
good points, but a lot are also in my opinion common sense like
paying attention to how enthusiastic the person is when talking about
technology or their previous jobs and experience, as well as project
thy have worked on. If you have a dull unmotivated rock sitting
opposite you, you may want to end it there.

I would have never
given much thought about paying attention to what the interviewers
role in the company is, but he makes a good point about interviewers
that aren’t developers and are instead project leads or managers. I
would have never thought that might mean that developers may not be
empowered to make decisions. The single interview process is also
interesting and worth noting. It would not have dawned on me that the
company might be in a hurry and doesn’t take the time to hire the
right people. I think overall there are some great points here. I
like how he describes a good interview and I couldn’t put it better
myself. “A good interview is like a good an informal chat between
passionate developers.” I have been on interviews like this and
have been hired. They are good because both parties are at ease and
it makes it easier to be open about yourself. I agree as well about
it being a mistake to hire someone without seeing them code or their
code at least. It can give a good glimpse at their confidence and
experience as well as decision making skills and the ability to take
constructive criticism. Bringing your computer I don’t think I
would have thought of, but it is a good idea so they can see what
tools you have and use etc. Last but not least I can’t agree more
with developers must interview developers.

Overall another good
chapter with a lot of good information that I will probably revisit
in the near future.

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

Sprint 6

The last sprint of the semester.  This semester flew by, but I am proud to say that we finally fixed our issue! Turns out we focused so much on how to fix it that we didn’t even realize it was totally out of our hands.  We ended up asking for help, and the openMRS developers got right back and said that they will need to contact someone in order to make this change.  I learned something very important from this sprint.  I learned that you shouldn’t stay stuck for too long without asking for professional help.  We broke down the whole issue and knew where the problem was happening, but we just didn’t have the access to the code to change it.  This must happen all the time in the professional world.  Next time I have any type of coding bug to fix, I will break down the problem (like we did), but I will make sure to ask someone for assistance way sooner.  If we never asked for help, we would have never resolved this issue.  Our last and final thing to do for the semester is put together our final presentation.  I look forward to sharing with everyone!

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 11 & 12

Chapter 11 of The Software Craftsman gives great advice on what companies should NOT do when interviewing for new developers.  Many great developers will end up not going with certain companies because of a horrible interview experience.  Individuals conducting interviews need to make sure to not scare away great potential workers by having bad interviewing tactics.  The chapter discusses that interviews should not be a test to see how well you know the answer to close ended and technical problems.  Anyone can simply memorize and study common interview questions to be sure to come across as a good candidate for the job. However, this chapter makes a great point that just because you know the technical/text-book answers doesn’t mean that you are the best candidate for the job.  I personally would rather have a co-worker that is passionate and wiling to learn, rather then someone who knows “everything”.  A passionate coder is the coder that will be great.  A coder who knows everything may seem really good and all, but they also may lack that passion and drive that someone else might have.

Chapter 12 talks about how low morale can negatively impact a workplace in more ways then you may think.  This chapter discusses that having passion will go long ways in the overall outcome of an organization.  I agree with the whole idea of this chapter, and I have actually personally experienced this.  The experience I had wasn’t at my computer science internship but it was when I used to work at an ice cream shop.  Most of the girls I worked with there, along with myself, would want to make nice looking ice cream cones and sundaes for the customers.  However, there was one girl that was always extremely sloppy.  The ice cream would be dripping everywhere, and the customers were never happy with her work.  This was a perfect example of someone who had no passion whatsoever.  She was just there to simply get paid, and she did the bare minimum amount of work possible to get the paycheck.  Her lack of effort negatively impacted all of us.  We would have to clean up after her, and deal with the problems she caused with the customers which brought down everyones motivation and attitude.  My experience relates to what this chapter talks about.  The chapter talks about how being a motivated developer will motivate other developers to work hard.  Have one person bringing everyone down with no passion or willing to try their best is not a good thing in any type of work place.

 

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.

Reflection: Sprint 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 15 & 16

This week i read chapters fifteen and sixteen from The Software Craftsman by Sandro Mancuso.

Chapter fifteen is titled “Pragmatic Craftsmanship”. This chapter discusses the idea of mastering our practices as a programmer and being more pragmatic. It talks about how making quality code should not be more expensive and it is our job as software developers to make this a reality. This does not mean we have to use TDD every time or practice XP practices constantly, however we have to care about what we are doing and be the difference between great and mediocre. You have to be a developer is passionate about writing code. Not only that but you should be proud of the code that you do write. He goes on to talk about the four rules of simple design which he likes to define as.

  1. passes all test
  2. minimizes duplication
  3. maximizes clarity
  4. has fewer elements

Although the order is debated these design elements are very important to writing quality code that you can be proud of.

Chapter sixteen is titled “A Career as A  Software Craftsman”. The chapter opens with him telling the readers how amazing it is to be a software craftsman and then he starts listing where software is not only relevant but essential to life as we know it, hint its everywhere. This chapter essentially ties everything in the book together. It goes back over how important our careers are and what we should do if we do not know where exactly we want them to go just yet. The chapter ends with a paragraph titled “The Mission”. This is a very important paragraph to the book. It is something that every software developer should read and implement in their everyday lives along with every thing else that is in these books. It tells developers to be proud of what they can do and who they are. All in all this was an amazing book, that will definitely help me in my future career. I would highly recommend the Robert C. Martin series to any aspiring or current developer.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman Chapters 13 & 14

This week i read chapters thirteen and fourteen of The Software Craftsman by Sandro Mancuso.

Chapter thirteen is titled “Culture of Learning”. This was a very interesting chapter in my opinion as learning is one of the most important skills that a computer scientist or software craftsman can have. Technologies will continue to change and we have to be able to stay current in order to be able to do our jobs well, and that means learning as much as we can as often as we can. In this chapter the author tells us how to cultivate a culture of learning in our work environment even if we are not in a position of power within the company. He suggest things such as starting a book club, having a tech lunch, or even switching projects every once in a while. There are numerous ways to encourage learning in a work environment, the key is to cultivate it into a culture so you can motivate others to want to learn as well. Even if it is something that you can only fit in once a week it will be a very beneficial tool in the long run for both your company and your career.

Chapter fourteen is titled “Driving Technical Changes”. This chapter revolves around bringing new and better technical practices such as TDD to your team. This is not always the easiest thing as people do not usually like to change especially management. However it is necessary if you want  a well working team that produces good code in a reasonable amount of time. The chapter teaches us about a large number of different types of skeptics that we might run into, such as the cynic, the burned, the herd, and so on. It also goes into detail as to how we can attempt to deal with these skeptics and bring in new practices. He then goes into detail about the hardest part of this process in my opinion which is dealing with someone above you who is roadblocking your changes. He goes as far as to say that to just fall into line and not push changes you know will help is irresponsible and incompetent. All in all this chapter will most likely help me in my future career as i am sure to face developers and even managers who are stuck in their ways, and if i care about the projects or the company at all it is my responsibility to attempt to bring better practices so that we may all produce better code in the future.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman Chapters 11 and 12

This week I read chapters eleven and twelve of The Software Craftsman by Sandro Mancuso.

Chapter eleven is titled “Interview Anti-patterns”. This chapter continues the interview trend discussing something he refers to as interview anti-patterns. The author talks about all the things that an interviewer should not do when talking about a technical interview. The interesting thing is that every single one of the things that he discusses should not be a part of the technical interview are something i have experienced first hand in technical interviews over the past month. He says that you should not do things such as brainteasers, whiteboard coding, blocking the internet and even using algorithms (unless of course it is a job that requires algorithms in the every day job). Over the past month i have been subject to every one of these types of interviews and i have to say white board coding is my least favorite thing in the entire world.

Chapter twelve is titled “The cost of low morale”. This chapter discusses low morale on development teams and how at times it can destroy a software project. It begins with something called the “agile hangover” this is the idea that after a company has taken in all the agile practices and began to implement them, they are still outputting software in a slow manner. This is due to the fact that they don’t fully adopt the technical part and the coaches do not know how to implement these processes. Basically even though they adopted agile they are still doing the same thing that they were before they adopted it. Software projects need motivated and skilled developers to see them to completion. Motivated developers make more motivated developers, allowing a project to flourish. He talks about something called a nine to five developer, basically someone who only goes to work to get paid and doesn’t care about the company the project or even developing their own skills. These people can kill software projects and are very bad to have on your team. You need software craftsman who actually care to help motivate the other developers to care as well.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

Reflections on Learning and Work Products, Sprint 6

With this being our last Sprint of the year, we wanted to try and get our last issue (APTS-254) dealt with – this issue being the one in regards to the Viral Load Pop-up reminder. However, right off the bat, we ran into more problems that we needed clarification on. We were able to get the code for the ETL Rest Server and looked into. Our team was able to find the file in which the reminders where generated, but we were unsure how to go about coding it. The way that the issues was phrased could mean all we needed to do was make a pop-up appear in Angular, but it could also be that we needed to work on the ETL backend. On top of this problem, we also could not get the ETL server to work locally on our computers. This means that we couldn’t see how the reminders and pop-ups worked, so we couldn’t see the issue or troubleshoot our code to fix it.

After coming to these conclusions, our team decided to message AMPATH for more clarification. A day later they got back to us saying that they would make a test2 ETL server that we could work on. However, we were never able to work on this server due to the fact that our Sprint ended before they could get back to us. I think what I’ve learned from this is that clarification should be addressed at the end of the previous Sprint. That way you can go back into your next Sprint with those problems already resolved, and it gives the team the ability to set fresh.

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

The Software Craftsman Chapters 9 and 10

This week I read chapters nine and ten of The Software Craftsman by Sandro Mancuso.

Chapter nine was titled “Recruitment”. This chapter was mainly aimed at people who would be conducting interviews. Or even people who may be in a position to have an affect on the recruitment process at their company. In that regard the author does a good job of outlining how most companies conduct recruitment is very bad and the reason that they do not find the developers that they are hoping for. He talks about how job descriptions do not help as well,  especially when they say things like five years experience java etc. This is because it really tells you nothing about the developer himself. They suggest doing interviews where you can see how the person thinks and how the person codes in real time. Having a set of questions planned out with static answers is not a good thing because anyone can sit down and memorize a bunch of information. You need to provide the candidate with a problem and watch how they go about solving and coding a solution to that problem, maybe even helping them along the way. This chapter was relevant to me in that it showed me what companies might be looking for in the interview process as well as some of the skills that i may need to develop in order to get better at interviews in the future.

Chapter ten was titled “interviewing Software craftsman”. This chapter was very much a continuation of the previous chapter. The previous chapter did a lot of showing what was wrong with the recruitment process where this chapter provided a great deal of solutions in how to fix that process. This chapter looked at the situation from both the side of the candidate as well as the company that is interviewing. Again this chapter helped me much the same to be more prepared for upcoming interviews, or at least provided me with the right information so that i can attempt to make myself more prepared. There was a great deal of helpful information and the author did an excellent job of outlining what good interview practices are and what companies should really be looking for which will help me become that person.

From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.