Mentee to mentor: Makers Day 28
After yesterday's blog, I decided to listen to my own advice and take the evening off (other than the blog itself). This meant I woke up feeling much more well-rested this morning.
Our debugging workshops to date have focused on tightening the loop and we’ve covered loads of ways in which we can do that, emboldening our process and helping us to build skills that we will use for the remainder of our careers. I have notes and walkthroughs for the previous workshops over in week 1 and week 4.
This week we were focused on following the flow. This meant ensuring that we understood how different types of code are instantiated and executed, and using this knowledge to help find where and how our code was going wrong. It very much falls into the category of tightening the loop, we’re simply using a different methodology.
We then completed an exercise that involved using a plethora of console logs to follow the flow of some buggy code to get it working again.
Before we started the 12-week main course, we completed a 4-week pre-course. During this pre-course we were asked to pick a mentor from the list provided to us, this list was made up of main course students. I ended up forming a really good relationship with my mentor, and we have since become friends.
Last week, it was our turn to step up to the plate and fill in a brief bio about ourselves for potential mentees to muse over. It’s truly astonishing to believe that we’re already at this point, this bootcamp is flying by so quickly, it’s both exciting and absolutely terrifying all at once.
Today our form was sent out to the April cohort, and I had a few unfamiliar faces appear in my Slack DMs. I’ve had some nice conversations with the potential mentees, and though I sadly cannot take them all, I’m looking forward to imparting whatever wisdom we have amassed thus far, and helping them in any way I can.
There was a little flurry around the room as several of us had received messages whilst we were in the workshop, and naturally, we were all reflecting on the seemingly ludicrous reality that we had already gotten to this point.
This has been extremely evident this week, there is absolutely no need to baby-step us through any of this work, once syntax and conceptual differences in the language were covered, we could apply the armada of skills we’ve already learned. A very agnostic approach indeed.
This means we know where we are with testing, mocking, business logic and so much more. The only translation of skills left to cover is one of the most exciting parts of JS, building web apps. We’ll be looking at this next week and I must admit I’m pretty excited.
There were definitely moments in the group project last week where it was obvious that JS would enable us to create something much more dynamic, responsive and visually impressive. I love seeing the code we write take shape on screen, so I eagerly await moving forward.
In the meantime, we will continue making progress on the current scope of this week's work, taking the time to ensure there are no gaps in our knowledge.