How conveniently I had forgotten all about recursion and how it came back to bite me! :P
I did put in a lot of work for this coding challenge too. And I learned SO much. My biggest take-away from this though was the usage of pry and debugger to debug my code. I’m not a visual debugger (who is?), I always use well placed “output to terminal statements” to check how each of my variables is faring through my program. And I can write very very buggy code the first time I try to solve a problem (hey, don’t judge me, I’m still learning!). So I really loved pry & debugger because of how easy they made this for me.
When the time came for the coding challenge though, I was a bit disappointed with myself. I was able to solve only 3 of the 4 problems in the challenge. I had time to solve the final question, but I just couldn’t understand what they were asking me to do. How can I solve a problem that I can’t understand in the first place? (nice segue to “you need to truly understand customer requirements in order to translate them into the exact product they want! Which didn’t really happen in this case!).
So with a heavy, nay sinking heart, I submitted my answers to 3 of the problems, wrote off my chances of interviewing with app academy and drowned my sorrow in icecream, while watching the red wedding in Game of Thrones. Who can recover from this situation? I DID. Only after an email from App Academy inviting me to interview with them though. Woot.
I interview this Monday & I’m so excited about it. I’m happy to have made it this far & I hope I get the chance to be part of their SF class this summer. More *fingers crossed*.