Ironhack Week 4
So, first of all: I switched over to counting weeks. It's very confusing to enumerate the days because I have three Ironhack days per week - I just lose track. I decided to group the experience in time units rather than content - I'll try to make sense of it while I write, I promise!
Most of this week's work was on methods - more specifically, on the probably most helpful array methods .map(), .reduce(), .filter(), .sort() and .reverse(). And it was about working with Objects (well, again, I should say) - because working with Objects in Object Oriented Programming is kind of mandatory, I should think.
My own method of approach is to do the "homework", the labs, before the material is covered in class. Thanks to my months of prepwork I understand the documentation that's given to us and can work on the labs beforehand, and if there is ever a problem I don't understand or something I don't grasp completely, I can still wait for class and see if it won't be cleared up then. And if necessary, THEN I can ask questions.
It was a lot of work - the lab was divided into two parts - but I sat down and used the free time I had to work on those exercises.
Manipulating Space and Time
Since the third day of every Ironhack Week is a long day, we split it up pretty much into two parts. And you could see it from the perspective of preparing you for the labs, but also preparing you for being able to talk about coding - interview questions and such.
It's so funny to me. Timeouts, intervals, the Date or Math object - all of that stuff by itself seems so useless to me. It still does! What am I going to do with the Math object in real life? And then you start thinking about it in logic and coding terms - when does some process ever use a seemingly random number? When does something get repeated, over and over again? This code is everywhere.
The challenge our instructor cooked up was building a "Simon Says" game - like the plastic children's game, not the plot device from Die Hard 3. (We also had a choice of Whack-A-Mole, but I asked my classmates to consider not normalizing violence against animals.) And so "we" started coding. Our instructor wanted to only write instructions in pseudocode but ended up writing up about 95% of the whole game. We just had to piece it together here in there, and I almost got it done. I wasn't able to finish it during class though, since the lecture was actively going on and I do prefer to be able to stare at my code in silence for a while.
In this series of blog post I write about my experience at Ironhack bootcamp. The material is available to anybody and free to use on the internet - I do not work for Ironhack (I paid to participate in a bootcamp, so...). These posts are not supposed to be deep-dive anything, just reflect what I learned about various programming techniques. If anybody finds them while googling, cool. If anybody finds them helpful, even cooler! If nothing happens - also fine.