Sprint Reflection 6

Even though we all got much accomplished within our team over the semester, unfortunately we were not able to get one of our pushes to be committed. I felt that we were making good progress on the button together as a team but after we decided to split into 3 miniature teams we slowed our progress. Also, there were points when the button stopped working on our system which was also very inconveniencing. We had times where our systems wouldn’t even start up. But in the end I feel that everyone has learned much more than they had thought they would, by being a team and collaborating together on a project and always staying in contact.

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.

Software Craftsman Chapters 5 and 6 (4/04/17 Week 9)

Going into Chapter 5, the only thing I can recall is the same topic the other author discussed in Clean Coder was pretty much the same thing. This chapters covered the confidence and necessity to say No during a project when you need to even though it may upset your client. There is a thing called dead-lines which have to be accounted for and these dates tend to cause the most stress in development where in some cases the deadline may or may not extend. There comes a time where your employer want you to add more to the plate even though there is already enough to deal with let a lone there is the fact that unexpected events happen during development which can not stop the deadline from happening. The chapter describes how to professionally say you can not do something as well as give a good reason why to. After all, it may make you a hero.

Interesting enough, this topic instantly reminded me of the Clean Coder book which talk about the same topic and pretty much has similar advice. That is actually a good thing knowing that something you read is reliable especially if different people go by it.  I love its mentioned you should provide options if there is bad news. It sounds like you want to make the best out of what you got and not just not wanting to do work.

Chapter 6 covers what is also another aspect in development which is knowing that even though you have something that is functional and working, is does not mean it is the end of the project, the finish line is far from over and the team only hit a milestone. There comes the whole fact of maintenance and on-going support that the software will require after launch. You need to have updates to fix bugs and hopefully add new features, let alone if the developers know how to do so professionally. Speaking of bugs, testing your software profusely is another key part after launch as there are bound to be user reports of certain areas not working, you may never know.

As I like to put it. The end is not the end and even though your software is out in the wild  (congrats by the way you do deserve some champagne) you have to give the impression that you care about the product and tell users you are still there for them when they need help using what you created  No it doesn’t have to be forever, but a garden does need to be looked after.

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Reflections (3/29/17) Week 8

After contacting Jonathan Dick regarding trying to find the draft button and trying to get the forms to work. He told us to use the test 2 server path in order to get access to the forms and such and in theory it should work. We tried that originally and it did not work. We thought we had to log in to openMRS itself and see if that was where the button was because we had no clue where else to look. Afterwards, we did what Jon told us to do for the sake of it and then this time around it actually worked. We managed to load the forms and then Kyle managed to find that orange “back to draft” button that was on the far right of the screen. What was unfortunate is that the button did not even work when we tested it out, so Patrick reported that to AMPath however they did not reply back to him about it. Instead we just focused on moving the button to place AMPath devs wanted us to move it. We decided to move it to the left side because it would be easier to see and not miss.

When we got into class on day, we saw that Patrick already found the code to move the button and have moved it to the left side of the screen and we were proud of it. All we had to do was find the appropriate styling and edited the button’s alignment. After feeling proud of it, we ended up pushing the changes to the main repository that Ryan created and then Ryan began the process of requesting a pull request hoping that it would get approved.

Our teammate was disappointed on a grade we gave him regarding his lateness and that he was put into the improvement program. We decided to help him out to improve his score before it was too late.

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Software Craftsman Chapters 3 and 4 (3/28/17 Week 8)

In the third chapter of the Software Craftsman, the author goes in depth of what Software craftsman actually is. The author uses this term in order to describe good and angelic developers who always want to do their best and give their project the most value they can ever give it. They want to be productive and get things moving along and just leave things in a cluster, and that means with clients and publishers as well. I guess this is what he calls a ‘Dream Team’.

In my opinion, this probably should end up being the whole resolve of the book even though its just a chapters that’s not even the first one the author dives into.  I feel like in this chapter the author is being kind of sarcastic because he does not tell you what the definition of being a Software Craftsman is. He is telling you what it isn’t and also what other sources say such as wikipedia. Instead of getting straight to the point he just mocks the reader. Later on he finally stats that Software Craftsmanship is about professionalism in software development. This chapter could have been straight to the point and overall shorter. I’m reading to learn not to waste time.

In the fourth chapter, the author continues touching base on developers’ behaviors except this time he is talking about the attitude toward the project. Making a good point that if we think good code from the past is still good, then we are not learning anything, the author goes into how much craftsman care about their work, which also includes discovering new things and adapt to better outcomes to help suit development in this future time-frame.

This chapter came to me as a good advice kind of area where he mentions good practices a developer should commit too on their own time that inflicts on their skills. Always practicing, staying up-to-date and keeping communication with the outside world are great ways to actually stay in shape as a developer and evolve the precious skill set.

 

 

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Software Craftsman Chapters 1 and 2 (3/14/17 Week 7)

In the first chapter of Software Craftsman, the author talks about how working in the industry was different in the past compared today. He makes remarks that even though people who work in the industry have been there for a long time and have gotten the Senior rank, it does not mean that they have the assumed knowledge that a Senior rank developer should have. Nowadays, companies are wanting professional work and professionally made projects, unlike back when they used to hire cheap coders who thought they knew what they were doing.

I kind of have to agree with the whole senior rank topic when it comes to knowledge. Not everyone is as fresh when they reach senior rank and they would usually depend on the internet and make excuses to go through their day. While it could be anyone, the seniors have an ideal image as they are looked up to as leader so its interesting how today plays out.

In the second chapter of Software Craftsman goes into the topic of being Agile, as did the Clean Coder in the previous book. Talking about the two groups, process-oriented and technical-oriented. Process-oriented focused on what is priority to finish while technical-oriented aims for teams to focus on quality. The author then talks about the Agile manifesto which comes with the 12 principles along with other agile content.

Its interesting that the author started to point out that companies who have been tackling the agile process have been producing crap results in terms of code.I guess only people who know how to agile should use it or as the author calls them professionals. Describing how the work environment between two companies can tell how professional they are with organizing and that comes clear with being agile.

 

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Software Craftsman Chapters 11 and 12

Chapter 11

I enjoy how this chapter opens with the “Don’t Be a
Smart-Ass Interviewer”. There is nothing more I dislike than someone who thinks
they are better than you and try’s and prove it. If I ever walk into an
interview and that happens I would like to think I would leave. I don’t have
the time or tolerance for such nonsense. I also enjoy some of the questions he
says to avoid in the brain teasers, “How many golf balls can you fit into an
airplane?” Hahaha. All joking aside I think that this chapter is pretty much a
common sense issue and unfortunately I think that some people really need it
beat into them. It is common sense you shouldn’t ask questions you don’t know
the answer to and don’t make the candidate look like a fool. If someone does
not know these basics, they probably shouldn’t be interviewing anyone, or maybe
even be in any position. I also like how he talks about not blocking the
internet during a coding activity and goes on to say, “I wonder how they would
do without it?” I also like his thoughts on not asking the interviewee to write
out code on paper or white boards and feels they should stick to what the
candidate would face on the job. Great tips and I am certain I will run into
interviews where I am asked to do these things.
His take on not asking to wrote algorithms or algorithmic
exercises is awesome. I like his thought pattern here on how they should ask
something closer to the reality of the projects at the company and that how
many problems weren’t related to the algorithms, but the lack of good tests and
the like. Overall good chapter and some great advice.
Chapter 12

I really don’t have much to say in this chapter as I think
it speaks for itself. Lack of morale is a company killer in my opinion. It is
all pretty plain to see that if you lack motivation and hate the job you are
doing than you will not bring anything of use to the company. It is contagious
as well. People moping around complaining about this and that and blaming everything
on so and so, when they really need to take a hard look at themselves. 

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

Chapter 11

I enjoy how this chapter opens with the “Don’t Be a
Smart-Ass Interviewer”. There is nothing more I dislike than someone who thinks
they are better than you and try’s and prove it. If I ever walk into an
interview and that happens I would like to think I would leave. I don’t have
the time or tolerance for such nonsense. I also enjoy some of the questions he
says to avoid in the brain teasers, “How many golf balls can you fit into an
airplane?” Hahaha. All joking aside I think that this chapter is pretty much a
common sense issue and unfortunately I think that some people really need it
beat into them. It is common sense you shouldn’t ask questions you don’t know
the answer to and don’t make the candidate look like a fool. If someone does
not know these basics, they probably shouldn’t be interviewing anyone, or maybe
even be in any position. I also like how he talks about not blocking the
internet during a coding activity and goes on to say, “I wonder how they would
do without it?” I also like his thoughts on not asking the interviewee to write
out code on paper or white boards and feels they should stick to what the
candidate would face on the job. Great tips and I am certain I will run into
interviews where I am asked to do these things.
His take on not asking to wrote algorithms or algorithmic
exercises is awesome. I like his thought pattern here on how they should ask
something closer to the reality of the projects at the company and that how
many problems weren’t related to the algorithms, but the lack of good tests and
the like. Overall good chapter and some great advice.
Chapter 12

I really don’t have much to say in this chapter as I think
it speaks for itself. Lack of morale is a company killer in my opinion. It is
all pretty plain to see that if you lack motivation and hate the job you are
doing than you will not bring anything of use to the company. It is contagious
as well. People moping around complaining about this and that and blaming everything
on so and so, when they really need to take a hard look at themselves. 

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

Chapter 11

I enjoy how this chapter opens with the “Don’t Be a
Smart-Ass Interviewer”. There is nothing more I dislike than someone who thinks
they are better than you and try’s and prove it. If I ever walk into an
interview and that happens I would like to think I would leave. I don’t have
the time or tolerance for such nonsense. I also enjoy some of the questions he
says to avoid in the brain teasers, “How many golf balls can you fit into an
airplane?” Hahaha. All joking aside I think that this chapter is pretty much a
common sense issue and unfortunately I think that some people really need it
beat into them. It is common sense you shouldn’t ask questions you don’t know
the answer to and don’t make the candidate look like a fool. If someone does
not know these basics, they probably shouldn’t be interviewing anyone, or maybe
even be in any position. I also like how he talks about not blocking the
internet during a coding activity and goes on to say, “I wonder how they would
do without it?” I also like his thoughts on not asking the interviewee to write
out code on paper or white boards and feels they should stick to what the
candidate would face on the job. Great tips and I am certain I will run into
interviews where I am asked to do these things.
His take on not asking to wrote algorithms or algorithmic
exercises is awesome. I like his thought pattern here on how they should ask
something closer to the reality of the projects at the company and that how
many problems weren’t related to the algorithms, but the lack of good tests and
the like. Overall good chapter and some great advice.
Chapter 12

I really don’t have much to say in this chapter as I think
it speaks for itself. Lack of morale is a company killer in my opinion. It is
all pretty plain to see that if you lack motivation and hate the job you are
doing than you will not bring anything of use to the company. It is contagious
as well. People moping around complaining about this and that and blaming everything
on so and so, when they really need to take a hard look at themselves. 

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

Chapter 11

I enjoy how this chapter opens with the “Don’t Be a
Smart-Ass Interviewer”. There is nothing more I dislike than someone who thinks
they are better than you and try’s and prove it. If I ever walk into an
interview and that happens I would like to think I would leave. I don’t have
the time or tolerance for such nonsense. I also enjoy some of the questions he
says to avoid in the brain teasers, “How many golf balls can you fit into an
airplane?” Hahaha. All joking aside I think that this chapter is pretty much a
common sense issue and unfortunately I think that some people really need it
beat into them. It is common sense you shouldn’t ask questions you don’t know
the answer to and don’t make the candidate look like a fool. If someone does
not know these basics, they probably shouldn’t be interviewing anyone, or maybe
even be in any position. I also like how he talks about not blocking the
internet during a coding activity and goes on to say, “I wonder how they would
do without it?” I also like his thoughts on not asking the interviewee to write
out code on paper or white boards and feels they should stick to what the
candidate would face on the job. Great tips and I am certain I will run into
interviews where I am asked to do these things.
His take on not asking to wrote algorithms or algorithmic
exercises is awesome. I like his thought pattern here on how they should ask
something closer to the reality of the projects at the company and that how
many problems weren’t related to the algorithms, but the lack of good tests and
the like. Overall good chapter and some great advice.
Chapter 12

I really don’t have much to say in this chapter as I think
it speaks for itself. Lack of morale is a company killer in my opinion. It is
all pretty plain to see that if you lack motivation and hate the job you are
doing than you will not bring anything of use to the company. It is contagious
as well. People moping around complaining about this and that and blaming everything
on so and so, when they really need to take a hard look at themselves. 

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

Chapter 11

I enjoy how this chapter opens with the “Don’t Be a
Smart-Ass Interviewer”. There is nothing more I dislike than someone who thinks
they are better than you and try’s and prove it. If I ever walk into an
interview and that happens I would like to think I would leave. I don’t have
the time or tolerance for such nonsense. I also enjoy some of the questions he
says to avoid in the brain teasers, “How many golf balls can you fit into an
airplane?” Hahaha. All joking aside I think that this chapter is pretty much a
common sense issue and unfortunately I think that some people really need it
beat into them. It is common sense you shouldn’t ask questions you don’t know
the answer to and don’t make the candidate look like a fool. If someone does
not know these basics, they probably shouldn’t be interviewing anyone, or maybe
even be in any position. I also like how he talks about not blocking the
internet during a coding activity and goes on to say, “I wonder how they would
do without it?” I also like his thoughts on not asking the interviewee to write
out code on paper or white boards and feels they should stick to what the
candidate would face on the job. Great tips and I am certain I will run into
interviews where I am asked to do these things.
His take on not asking to wrote algorithms or algorithmic
exercises is awesome. I like his thought pattern here on how they should ask
something closer to the reality of the projects at the company and that how
many problems weren’t related to the algorithms, but the lack of good tests and
the like. Overall good chapter and some great advice.
Chapter 12

I really don’t have much to say in this chapter as I think
it speaks for itself. Lack of morale is a company killer in my opinion. It is
all pretty plain to see that if you lack motivation and hate the job you are
doing than you will not bring anything of use to the company. It is contagious
as well. People moping around complaining about this and that and blaming everything
on so and so, when they really need to take a hard look at themselves. 

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