Dev Bootcamp: Phase 1, Week 1

I'm not really sure what my blog format will be at this point. I know that I want to capture what the DBC experience is for me, and I want to blog about it. Below are my daily reflections for my first week.

July 27, 9:03 PM - What have I gotten myself into?

I kid! Today was great. We met all the staff, got to meet everyone face-to-face. I'm less intimidated by the process now that I've met the people behind it (probabaly becuase they work to mitigate the intimidation factor - at least I think that's what they're doing). We have these check-ins that last two minutes per person, whether or not that person has something to say or not. Not going to lie, the check-ins scare me the most at this juncture (I hate being the center of attention in this way). Sure, I'm worried that I won't be able to keep up, but I'm less afraid of that now that I've been here for a day. I'm really excited to be here and I know that my enthusiasm will carry me through. I'm grateful to have found the thing that reignites my passion for creating things. Just last night I made this awesome hangman game. I'm so proud of it that I've been showing it to almost everyone I meet.

My cohort is awesome, and pairing is a skill. Sleep is really important, and having a good attitude is a much bigger part of being 'effective' than you might think (especially on account of the pairing). I very much look forward to getting to know my cohort-mates better. Once we're all reasonably used to each other, I think this experience is going to get a lot cooler.

Day One, signing out!

Tuesday, July 28, 9:00 PM - What day is it?

The most common topic of conversation today was "what was your experience of XYZ?" We talk about how we're reacting to things as much as we discuss programming concepts. It's unexpected, and I have a feeling it will be super duper helpful later down the line. Our goal at this point seems to be to get used to DBC rhythms and to build some camaraderie amongst our group. I think we'll do great.

I end Day 2 hopeful, scared, and hopeful again.

Wednesday, July 29, 6:50 PM - Flying high

Today was a really good day - like, even better than Monday. I came into the space pretty tired (apparently a common theme for Wednesdays). In the working world, maybe Mondays are the low energy day. Here, we want to be here and we work hard. By Wednesday, we start to burn out a little. It's interesting.

So here's why today was so awesome: I worked with someone who's repeating Phase 1. I found it really great to work with someone that mostly already knows this stuff. Something my pair said to me helped as well - we're given a lot to do each day. It's not expected that we finish, in fact, it's all but expected that we don't. This is intentional for a few reasons. In 'real life', there will be days when you don't accomplish anything with a visible, external result - and that's okay. It doesn't mean that you're a failure as a web dev (or any other bad ideas you can come up with). They're getting us comfortable with being uncomfortable, or at least better able to deal with it. I'm incredibly grateful to be here. I think I'm going to learn a lot, and that I'm going to enjoy myself while I do. This isn't an experience I ever expected to have and I feel lucky to have found this (beautiful, zany, wonderful) place.

As always, the best advice is to have a good attitude. It will make or break the experience (as in life).

Saturday, August 1, 10:13 AM - Where did the time go?

I finally have a moment to sit down and record my thoughts.

Thursday was our first solo day, and it hit me like a ton of bricks. It was a day full of anxiety and struggle. I found myself unwilling to ask for help. The code that I did complete felt better designed and thought-through than my code on some of the other days, but I didn't complete as many things.

Friday was awesome! I stayed way too late, but I had a lot of fun! Friday was our first group challenge. We came, we whiteboarded, we conquered! The tricky part was the whiteboarding at the beginning. With a good, conceptually sound plan to work off of, we were unstoppable. The trouble we ran into at the end of the day was that we couldn't agree what to put on the whiteboard.

Final Thoughts

What works?

  • Keeping a good attitude. I cannot emphasize this enough. This is a cooperative learning experience. Being respectful of your pairs and their ideas is super important. I had to remind myself to relax quite a few times. It was interesting trying to figure out why I was stressed. More often than not it had to do with fear of incompetency or fear of not being heard. I'm going to keep up the inquiry around my stress points.
  • Exercise! healthy eating! hydration! all that good stuff

What doesn't?

  • Talking louder to be heard. A better plan is to say, "I don't feel included in the decision making process right now, can we slow down?" (and also realizing that you may be the cause of this reaction in others)
  • Coffee > smoothies for an afternoon pick-me-up (super helpful if you feel like you're running out of steam after lunch)
  • Pig-headedly trucking through a problem. It's not wrong, but it's also not the most enjoyable way to program. Next time try discussing potential solutions with coaches, staff, or other boots. I got caught up in comparison and competition in the worst way on Solo Day. I'll be on guard for that in the future.

Full steam ahead! I don't know what to expect from this experience and that excites me. My intention is to gobble up everything that DBC is putting on offer.