Problem Solving

Mental Blocks

SO MANY TIMES.

In this sprint there were heaps of times that I was "blocked" because I was still a little unsure on how to use some of the functions, comprehension and the fact that the "math was not mathing.".

Because I am a beginner to coding, this sprint was definitely a challenge. However, by some miracle of trial and error, research, console.logging, mental breaks away from my laptop and of course google, I completed the Kata Tasks and made it through the week.

🎉

However, I found that when I would eventually find the solution to my headache - it was because I had either forgotten a comma, space between a bracket or forgot an "s" on a word that was meant to be plural. Grammer & spelling is really important. It led me to a lot of "ah huh" moments and "oh duh" moments.

Elegantly Solved ? 😅

Elegantly solved? I don't think I solved these problems elegantly. But they got solved. But, honestly with the multiple different techniques that have been presented, solutions were found. 😅
An example:

  • Youtube & Google: If there was something I was stuck on I would search it on google. However, I did find that a few forums were confusing - it was hard to find simplified terminology - Luckily, a few youtube creators came through clutch, with visuals and simplified explanations.

  • Problem Solving Techniques

    Personally, I like Trial and Error as a method, but it isn't always practical for time crunching situations.

    However, throughout this sprint have discovered new methods and rediscovered some important ones.

    • Rubber Ducky Method
    • Pseudocode
    • Console.logging
    • Google


    Confidence Level for Technique Capabilities
    ★ ★ ★ ☆

    At the moment my confidence for the above techniques are sitting at a 3.5/5 star rating.

    Pseudo is great but sometimes it takes me a little while to break down the problem into smaller blocks and to comprehend what the actual task at hand is and what it is asking me to do. However, I found that using pseudo in conjunction with console.log to see if it was doing what it was what I wanted to do.

    One thing that I will definitely be looking at improving is asking for help. I need to be more confident in asking for help from my peers.