Sprint 6 reflections

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

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 reflections

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

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 reflections

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

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 reflections

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

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 reflections

Well this learning reflection is going to be short as spring
break got in the way and well I was lazy over the break and didn’t accomplish
as much as I would have liked. I will say that this whole experience so far has
been decent, but has had its challenges to me. It has taken a while to get to
where we are at and when we finally got issues the semester is half over so
that is kind of frustrating, but like with anything in life, things don’t
always go as planned. We have been working on an issue to do with logging out
while you are editing a form and it is not saving your data. The whole team has
been assigned to separate parts of this and my part was to figure out the
routing to use when it was all said and done. Upon looking into the issue
though I cannot do the route until someone else does their part so I was kind
of at a standstill in a sense. I have become more familiar with the projects
code though and I happy about that. After discussing the issues we found out
that we were looking at the issue wrong and were now waiting on the folks at
ampath to get back to us. I will quote a team member as to what we need to work
with no, “So the actual problem with the code is that the confirmation dialogue
is being run asynchronously using an observable. Which means as soon as the
observable is made it is being returned regardless of whether you have clicked
accept or not. Which means the value that’s returned by canDeactivate is
neither true nor false which is what glitches out the routing. Supposedly, if
you make the return value of canDeactivate, Observable<boolean> it’ll
wait for the returned Observable to complete before judging the activation but
for some reason that’s not working.”

So what initially seemed to be straight forward has proved
to be a bit more challenging as we get further into the proverbial can of worms
and are now trying to come up with a plan of attack at this. I like how this is
unfolding though as I am learning a lot even though it doesn’t seem like we
have done a whole lot we are still learning about what problems and issues can
arise while tackling a bug and the process of working together as a team as
well as using electronic communication and the various tools at our disposal to
solve the issue. I am confident that this issue will be solved now that we have
a direction to go in and I am looking forward to tackling the next challenge.
We are going to be pairing up and doing some pair programming for the next
issues. I have never done this in practice and am looking forward to it. I have
read enough on it and it seems like a good way to do things.

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

Clean Coder Chapters 13 & 14

Chapter 13: Teams and Projects

Chapter 13 is one of the shorter chapters in the book. This chapter is all about teamwork. In my own experience, like most I have come to find out that just because you get along with someone does not mean you will work well with them. The author states that teams need a long time to start working together, he states it is on the magnitude of months. He also starts that giving one person more than one teams doesn’t work great but giving one team more than on project works well. I am one of the people that likes to work alone so I need to work on my team skills like communication.

Chapter 14: Mentoring, Apprenticeship, and Craftsmanship

This chapter is one of the most important or rather most relevant chapter to my current professional status. My thoughts on Software design used to be that you learned the skill then got a full-time job doing said skill. But more realistically is the way the author describes the transition into a professional Software Developer where you would train through years of work. I rather like his idea of using crafting trade rankings like master, journeymen, and apprentice. He also states that the profession of Software Development is missing the elders teach the young. Though I have not experienced the profession to this extent yet I hope that this is not the case.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Sprint 4

Coming back from spring break not much was done on my end regarding issue 184. However, our team have decided that each member should pick there own issue to solve. After I’ve updated the module from the team’s repository, i came across an issue and couldn’t connect to the server. Because of that, i spent some time trying reconnect to the server. I received help from Haider who was familiar with this problem.

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

Sprint 3 Retrospective

During this sprint i spent most of my time navigating through the ng2 module to get a strong understanding of it. Our  team spent time solving  issue NGPOC-184 and unfortunately we did not finish on time for the sprint. For me personally, i need to get a better understanding of Angular 2 to actually contribute significantly. Since this is a senior level course, we are given a lot of freedom with the expectation that we would be responsible enough to learn, communicate, and produce meaningful results within our groups. However, that is not the outcome of our team as a whole. We are about halfway through the semester and it’s not to late to pick up some of the slack.

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

Clean Coder 11 & 12

Chapter 11: Pressure

Chapter 11 is titled pressure and well it is quite straight forward. Every person deals with stress,  and all professions have a certain degree of pressure thrust upon them and being a professional Developer is no different than those other professions. The key in life is to learn how to be cool and clam under pressure. One great way to deal with presser that is detailed in the book is to properly assign your time as to allow for time to deal with crisis if it comes up. Another thing is to code cleanly (which was the title of the last book he wrote) Yet another way to deal with a problem of disaster proportions is to pair up. This is a useful technique to quickly and efficiently quiet the problem.

 

Chapter 12: Collaboration

This category is one of the ones that I feel like I need the most amount of help in, Collaboration. I definitely am one of the programmers who would like to work completely alone. I feel as though I could be more efficient by myself. But, This is not a good habit ad most of programming stems from collaboration with others. Some of these are clients and business people who know more about the situation you are coding for than you might. Therefore it is most beneficial to collaborate and communicate with other around you get the best end product that you can. Collaboration could even prevent future disasters that you have previously not even thought about.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 1 & 2 Week 8

The first part of this reading started out by saying you should be in the field that you enjoy. Just because you make more money doesn’t mean it’s meant for you. Another point was made that just because you’ve been coding for a long time does not make you a senior coder. It all depends on what you’ve been working on and the diversity of your skills that makes a senior coder.

The next part of the reading focuses on companies being agile. It takes about how being competitive means delivering software faster and with better quality. Most companies end up making this all about their process and tools. Just because a company practices agile ways does not mean they will improve. The most important part is hiring developers that can handle this and can make it happen, without these developers that have mastered these process and tools, then it will not improve the product or speed.

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