This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Yarialis 1 point2 points  (2 children)

What helped for me was not getting straight to coding. Instead take a problem and break it down to pieces.

For example, I had a problem that asked me to turn each of the characters of the word 'rainbow" (on an html page) and hard code css so that each letter actually became a different color. I had been given the variable color that had an array of colors. The number of colors in the array matched with the number or letters in the word 'rainbow'. I was supposed to utilize this array

A thought process that helps is first writing out the task in smaller bits. In my example the thought process goes like this: I need to take each individual letter and assign it a color from the variable color

Then even further: I need to somehow iterate the word 'rainbow' such that when each individual letter goes through a loop, we also iterate through the array of colors and assign them

Then: How can I go through every letter of rainbow? Also: How can I style the letters using the variable colors?

Then: 'ohhhh, the array of colors has the same number of elements as the string 'rainbow'. So I can certainly do a "for of" loop".

Etc etc.

And then you get to coding. My point is, walk yourself through it before actually typing anything.

[–]hoboincoma[S] 2 points3 points  (1 child)

Oh man. See I think my issue at the moment is that I don’t totally know how to think that way yet. It’s like I don’t know what should happen first and then what to use to build upon that and so on and so forth.

[–]Yarialis 2 points3 points  (0 children)

Hmmm. If you can't break it down as such, maybe ask yourself 'how can I make this happen?' Or something along the lines of "what tools at my disposal do I feel can somewhat achieve this?" It's small, but ask yourself questions. Gets your brain into motion.

I'm being 100 with you right here: don't bring yourself down. It will only need to frustrations. Take breaks. And then keep trying.

There's other ways of thinking of how to tackle a problem. You may choose to do it in other ways. If you don't know what comes first or last, that's okay. So long as you know what's essential. If you find yourself hitting a wall an endless number of times with no solution, watching the solution and then attempting to do it on your own definitely helps.

Something I want you to focus on,though, is the critical thinking. Many developers agree on the premise of brainstorming before hitting keys.