So I haven't mentioned this before, but I've applied to be in the Flatiron School + NYC Tech Talent Pipeline's Mobile Dev Corps. Why? Simple answer: because I love coding and I don't just want to do it when I get home from work or squeeze it in weekend mornings before I run errands. I want programming to be the work I do on the weekdays and improve on weekends. As I mentioned in a previous post, I'm moving slowing, but surely; I know that I'd thrive/do better if I was able to code 24/7 as opposed to squeezing a little code here before work, a little code there after work.
I also did my research for the right "coding bootcamp" for me. I researched Hackbright, Fullstack, General Assembly, and HackReactor, but the Flatiron School stood out to me. So I applied to the Flatiron School, and only the Flatiron School. That may be a naive move; I know most people apply to multiple bootcamps, but Flatiron is the only programming school I want to attend - so why waste my time applying to others - and that's absolutely no shade to the other schools, because I've heard great things about them too! I actually keep running into Fullstack Academy students and graduates at Women Who Code events and they have nothing but nice things to say.
I could go on and on and on about why I decided on the Flatiron School, but I won't - at least not in this post. Just know that I know when something is right for me, so I applied.
And now I'm waiting. I had my first interview earlier this month, and I was so nervous, but the person who interviewed me was very kind. She asked me some good questions and at the end allowed me to ask her a few questions. My nervousness was gone midway through that interview. I wish I could say the same for the second interview. I was freaking out internally. The second interview was a technical interview based on "(Le) Deli Counter." The interviewer started off by asking me how I got into coding and what I found hard about it. I think I gave a horrible (but truthful!) answer to the latter. I said that I didn't find a lot hard, just tricky (and at this point, I'm thinking "Oh God Laticia, really?"). But it's true! Hard to me is something that's damn near impossible, or at least feels near impossible - and nothing in coding has ever felt that way to me - challenging HELL YEAH, but hard? No (but I guess the argument could be made that hard/challenging are the same). I know that 9 times out of 10 the solution is somewhere out there. If for some miraculous reason the answer isn't somewhere out there, then there's a living, breathing human being who can help me. Anyway! Back to my horrible answer, I realized after saying tricky that I really wasn't giving a solid or satisfactory answer, so I said loops; which, to me, are the trickiest of the bunch - it's hit or miss when it comes to me avoiding infinite loops - so. I. said. loops.
Next, I had to explain my solution to one of the instructors of the program, which I believe I did well even though underneath my shirt I was sweating profusely (and anyone who knows me will tell you, outside of hot yoga I'm not one to sweat much) and hoping that I was explaining my solution well. After my explanation he asked me a few questions about what changes would I need to make to my program given a certain scenario. Honestly, my nervousness doubled at this point - the sweat, there was so much! But I answered to the best of my ability in that sweaty, nerve-wrecking situation. Now I wait until the end of next week... I think.
It sort of scares me how much I want to get into this programming, but I know I'm gonna crush it if I do.
I so badly want to insert a gif of those two girls CRUSHING IT in that dance video to the song 'Panda', but you can see that in the Deli Counter post, instead I'll leave you with this.