Days 39-47 out of #100daysofcode
Hello everyone,
Day 39
On October 27 I had an unexpected day. Sometimes things don’t go according to plan. I had a lot of tasks set up for Tuesday, and I was feeling quite motivated. I had planned to push commits to projects, to do leet code exercises, complete assignments for my college classes, and a few other things...then we noticed our family bunny, Dakota, was acting really odd. We took him to the vet and they said he had one of two illnesses and that both had a very slim chance of recovery. We had to force-feed him and keep a close eye on him making sure he doesn't run into things and hurt himself more. We prayed for that little guy so hard. Much to everyone’s surprise (including the vet) he was much better the next morning. His eyes had stopped shaking, he wasn’t running in circles, or doing his sideways head bob and he was eating and drinking almost like normal.
Even though I had this wonderful productive day planned out, something more important needed to be taken care of. For me, I often get programmers guilt when I can't get enough (or any) time to code that day or I fall asleep on my computer. We can do only do our best and that is all we can do. I am passionate about coding but I also have a full-time job, am going to school, and have a son. If I need to pick between coding and my son, then I choose him first even though he dropped a gooey cinnamon roll on my computer today. When he goes to sleep, that is when I will then work as long as I can before I start falling asleep.
Day 40-47
October 28-November 4th I have been busy studying for an interview that I have TODAY. To prep, I have been practicing leet code exercises, working on small projects to utilize OOP concepts of Encapsulation, Inheritance, Abstraction, and Polymorphism, reviewing and making new programming flashcards, making an acronym discussion outline for going deep into my project details in explaining OOP concepts, and talking about all of my project functionalities.
--QUESTION FOR YOU---
How do you prep for interviews? What has worked for you and what hasn’t? Let me know in the comments!
-------------
Thanks for reading my article,
Mara Munoz
Life happens! You have a lot on your plate. Little steps each day will add up... Prepping: I research the company as much as possible ahead of time...products they make, management, any relevant news. Then I review my Java interview prep questions I have assembled over time. It’s a living document that I add to as I learn new things. I make sure I can confidently answer the common questions. Then I review some of the common algorithms, but not too much because it’s hard to predict what they will ask. Then I review my own stories. Being able to tell stories about work I have done is way better than giving academic answers to questions. I try to use a story to answer questions as much as possible. Lastly, I write down questions I have for the interview team that are geared toward information gathering and creating opportunities to tell them more about how I would be a good fit. It’s a lot of work, but interviewers respond well to prepared candidates.