Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

The Clean Coder Chapters 3 & 4

Chapter 3:

I had favorable things to say about the first two chapters
because they kind of reminded me that no matter where you work or shall I say I
have worked, a lot of it rings true but it is also to me just common sense. I
mean saying no and saying yes? I feel like a bit too much is dedicated to this
and it gets old real fast and I want to skip on but I pushed through chapter 3
and well once again I have to say it is really to me a lot of common sense
things. I guess I shouldn’t say common sense, but for me I learned a lot of
this by trial and error and promising things to people that I knew I couldn’t
get done but just wanted to please so and so and felt that I would just deal
with the blow back later. You can only do that sort of thing so many times (for
me once or twice was enough) before you catch on and realize not to promise
things that you can’t deliver and to commit to things that you’ll do when you
say you will. I guess the book does a decent job at laying out situations and
the outcomes so hopefully people won’t make the same mistakes that Bob made. I
feel though that I have lived through all of the scenarios in some way or
another so I guess I got a chuckle out of it. He says that the language of
commitment can sound scary and it can help solve a lot of the communications
problems facing coders. He is absolutely right but it definitely takes time to
learn how to do it and be taken serious about it. You have to build trust and
being straight about things is the best way to do it.

Chapter 4:

I feel that this chapter is also about experience and a bit
of sense. This is all life stuff and applies to any form of work in my opinion.
He talks about preparedness and how coding is intellectually challenging and
how if you aren’t prepared for it your work will suffer. I find that this seems
like my dad is preaching at me when I was 16. I mean of course your work is
going to suffer when you can’t concentrate or when you are tired. The worst
code written at 3am, I have been there and don’t do that anymore because I have
learned the hard way and the good ole flow zone where you think you are
actually doing an awesome job reminds of the people who say they do their best
work high or drunk. Sorry it just doesn’t work like that as like he said, yes
you may get a lot done, but what did you miss? I am sorry but I guess I am kind
of disappointed with the first few chapters. I was good with the first two at
first but the next two to me seem to be more of the same lessons just in a
different context and I can’t write anymore about them. It does however seem
like the rest of the book will be decent to me. I thought his other book (
Clean Code) was good so I figured that this would be more of the same and I
hope the rest is.

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that. 

Reflections on Week 2

This week was actually pretty good for me. I think that our
team works well together and that it is going to be a productive semester. This
week I was able to get my accounts set up with OpenMRS and trello and learned a
bit about Scrum and finally started to put it to use. I like it because I am
finally putting everything that I have been learning so far to use or will be.
Aside from getting the basics set up we are going to be using Angular this semester
and I have never used it before. I am familiar to some extent with Javascript
but I feel that I have so much more to learn with Angular even though it is based
on JS.

I went through the Angular Tour of Heroes tutorial here and I have to say
that though I enjoyed it, I am still a bit foggy and will be going back through
it and doing another tutorial I have found. I am fairly comfortable with a lot
of it, but when it came to routing and navigation I felt a little lost so I am
going through some more on that area. I really like how the framework actually
works though and think that it is going to be a great experience this semester
and hope to be proficient with it as I hope to get into Web Development of some
sort and I know that this is used a lot. It doesn’t really take a lot to get an
app off the ground running, but digging deeper is going to be fun. I really
like how it is easy to split your app off into multiple modules or components
as your project gets bigger. I am confident that it will all come together
though and I will be proficient before I know it.

I am looking forward to what this week brings and what new
challenges are ahead of me. I am taking everything as it comes in and trying
not to put too much on my plate and so far I have been able to do that.