During the gradebook repl.it I became stuck on a part of the course where I had to push a new total into an array. I was 100% sure I had the code right, I was console logging the array and I could see the item pushed into it. To try and solve this problem, I double checked my code, had a browse around the internet to see if I could find an answer, and finally asked someone for help. I had made a mistake that I had made earlier in the course where I was calling the function but running the test was also calling the function so it was doubling up my answer.
It felt.. fun. I have a lot of fun when encountering problems in coding, especially at this stage. I know the answer will be out there somewhere, I am writing fairly basic code so there will definitely be many more people who have got stuck on this. It is also a chance to ask for help and see how someone else goes about finding the problem and then solving it. In this case, Jo$eph was albe to find the fault with my code right away and explain the solution to me. I hope to have learned not to use calls when they aren't asked for.
I ran into a problem during the built-in methods of the repl.it course that, I think, I solved quite elegantly. It's going to feature a problem solving technique not mentioned below. Late on tuesday afternoon, I was attempting to solve the second part of the built-in methods repl.it. The problem I was running into was that no matter what code I put in, I wasn't getting the right solution, but more importantly, I wasn't really understanding the things I was googling to help solve the problem. At first I thought I was just inaccurately googling and not getting the answers to what I wanted. Then I thought about asking for some help, but before that, I thought I would try explaining the problem to my cat. Here is the cat tax:
In the process of explaining what I thought should be the solution to my problem, I realized I was having a hard time explaining it and my brain was really struggling. I hadn't had much of a break that day and this was the reality check I needed to realize I needed a break. I had a break, had some food and a rest. When I returned to the code, within a few minutes I had the right solution and was able to explain the problem and solution.
I felt a bit worried during the rest period, I had a bit of self doubt creeping in, but the excellent results after the break really sold me on it. I feel like I learned the importance of having breaks and making sure I don't grind myself into a wall.
I feel pretty confident in pseudocode. Writing out the problem in plain language really helps me get a good idea of what's going to be expected of the code and helps me not get off track.
I am about 50/50 when it comes to trying something. Sometimes I don't know what to even start trying still, I usually have to read a bit more and try to understand the problem well before I can try something.
I feel fairly confident reading error messages. They are really quite informative if you know what they are saying and help me locate a problem.
Console logging is my jam and I use it ALL the time. I can think of nothing better. I use it when doing almost anything, just so I can see what's going on, see if it's succeded and it helps with my understanding of how my code is working or not working.
I do quite a bit of googling for answers, it's always a good go to. Someone out there somewhere has encountered the problem I am running into and have probably written about it on the internet so theres a good chance to find an answer this way.
I feel extremely lucky to have such a good homegroup and a good cohort in general. There is always someone around to help and my homegroup have been especially good at providing help and just being there for general encouragement. Basically homegroup 14 > all other homegroups. If you disagree then maybe you should have written about your homegroup, but you didn't did you?
100%! The coaches have all been a huge help and everytime I have talked to one of them about a problem, they have been able to help me out swiftly. I feel fully confident in all of them.
Extremely confident in this. I am quite a reflective person and improve a lot of my life through reflection so it's a natural progression to reflect on my coding experience and improve from it.
Back to Top