I find it interesting that this last project is drawing out the details of the process, where my previous entries did not. I don't know if it is the fact that it IS the last project, or that it feels like a culmination of skills learned so far, and therefore requires more expression of thought. Either way, I hope it is useful to those that read it.
Remember in my last post, where I spoke about overcomplicating things? Yep, I did.
I ripped out the entire search section, and did more research on Knockout, specifically finding some code that using the ko.utils functions. There are a lot of helpful functions that are built into KO, but not necessarily listed on the main documentation page. I tried to adapt a few scenarios, but still could not get the markers or list to respond to my changes that the code was doing in the background.
One of the advantages to the nanodegree program is the cohort system. Basically, when signups are taken in the beginning of the month for a specific nanodegree, all students that start in the same month are grouped together in a cohort. That group stays together through the entire series of projects, allowing students to bounce ideas off of each other (unless you fall behind, in which case you are switched to a later cohort, so that the projects that you are working on are the same as your cohort).
Since I knew I was missing something in my code, I took a moment to present my issue in the group chat to the rest of the Front End students. Two students did take the time to look over my code, and pointed out what my issue was - a complete misunderstanding of what I was supposed to be doing. Normally, when I use JavaScript, I code very linearly, almost as if I am using it as an event engine. However, Knockout uses an object oriented approach. I was treating my code as if it was processing events, not objects. Thankfully, both Tyler and Dallas recognized this pretty quickly, and suggested that I look at my issue differently. With a bit of guidance, I was able to correct my process and rewrite the search in less than two hours, and even added a bit of real-time flair to it.
What I also appreciate about the help that I have received (and try to give back when I can), is that students recognize that handing someone an answer is not going to help them in the long run. Sure, an answer might fix the immediate issue, but it doesn't allow the person who needs the help, to really learn how to recognize the issue if it comes up again in the future. I was given a basic idea of how things might be put together, and allowed to put together the details myself.
Even in the forum post from yesterday, Matt took the time to point out lines that needed to be addressed, but did not cut/paste the entire section and put it on a platter. This is the benefit of the cohort approach - those that have worked through the issues, can help those that are currently struggling with those same issues. Also, there are a lot more students than coaches, so availability is higher. (Not to take away from the coaches, as some do spend a lot of time being available as well.)
So, another hurdle cleared - more to go, but the light at the end of the tunnel looks more like destination than an oncoming train.
Remember in my last post, where I spoke about overcomplicating things? Yep, I did.
I ripped out the entire search section, and did more research on Knockout, specifically finding some code that using the ko.utils functions. There are a lot of helpful functions that are built into KO, but not necessarily listed on the main documentation page. I tried to adapt a few scenarios, but still could not get the markers or list to respond to my changes that the code was doing in the background.
One of the advantages to the nanodegree program is the cohort system. Basically, when signups are taken in the beginning of the month for a specific nanodegree, all students that start in the same month are grouped together in a cohort. That group stays together through the entire series of projects, allowing students to bounce ideas off of each other (unless you fall behind, in which case you are switched to a later cohort, so that the projects that you are working on are the same as your cohort).
Since I knew I was missing something in my code, I took a moment to present my issue in the group chat to the rest of the Front End students. Two students did take the time to look over my code, and pointed out what my issue was - a complete misunderstanding of what I was supposed to be doing. Normally, when I use JavaScript, I code very linearly, almost as if I am using it as an event engine. However, Knockout uses an object oriented approach. I was treating my code as if it was processing events, not objects. Thankfully, both Tyler and Dallas recognized this pretty quickly, and suggested that I look at my issue differently. With a bit of guidance, I was able to correct my process and rewrite the search in less than two hours, and even added a bit of real-time flair to it.
What I also appreciate about the help that I have received (and try to give back when I can), is that students recognize that handing someone an answer is not going to help them in the long run. Sure, an answer might fix the immediate issue, but it doesn't allow the person who needs the help, to really learn how to recognize the issue if it comes up again in the future. I was given a basic idea of how things might be put together, and allowed to put together the details myself.
Even in the forum post from yesterday, Matt took the time to point out lines that needed to be addressed, but did not cut/paste the entire section and put it on a platter. This is the benefit of the cohort approach - those that have worked through the issues, can help those that are currently struggling with those same issues. Also, there are a lot more students than coaches, so availability is higher. (Not to take away from the coaches, as some do spend a lot of time being available as well.)
So, another hurdle cleared - more to go, but the light at the end of the tunnel looks more like destination than an oncoming train.
No comments:
Post a Comment