DEV Community: Madison Kanna

Completing the freeCodeCamp JavaScript Algorithms And Data Structures Certificate

Madison Kanna — Mon, 30 Nov 2020 07:49:46 +0000

I'm currently taking freeCodeCamp's JavaScript Algorithms and Data Structures (https://www.freecodecamp.org/learn) certification for the first time and recording myself code as I go through each part of the curriculum.

If you'd like to join me in completing this certification, sign up to my code club (https://madisonkanna.com/codebookclub), and once you're in our discord, join the #freecodecamp-curriculum channel. Here you can post when you get stuck, or discuss the challenge with me as we go.

Video 1: Basic JavaScript part 1.

I was inspired to hit record as I go through the entire curriculum after watching Florin Pop's channel where he did so with the FCC curriculum.

These videos are just me hitting record and going through lessons-- nothing fancy, and almost zero editing. The goal is not to post polished videos but share my thought process as I go through the certifcate.

I plan on uploading at least 1 video each week and finishing the certification in 8 weeks.

One Tip For Learning How To Code

Madison Kanna — Tue, 06 Oct 2020 05:02:27 +0000

The amount of advice out there on learning how to code is overwhelming.

In this video, I go over just one tip that helped me go from beginner to employed developer. While there is lots of great advice out there, I focus on just one action that can get you from total newbie to coder.

I also invite you to join the CodeBookClub a community I help run for new and experienced developers.

I'd love to hear your feedback or comments.

If you're learning how to code, what are you struggling with?

If you already work as a developer, what is the one tip you'd share with new developers who are just getting started?

Join our JavaScript book club

Madison Kanna — Sat, 11 Jan 2020 20:32:53 +0000

Are you learning JavaScript in 2020? Or are you a JavaScript developer who wants to level up his or her skills?

Edit: the book club reached 1,000 members in a day (and growing) and in addition to the club, we're now hosting community events that are free and open to developers of all experience levels. Join the discord below or follow our Twitter account to attend an event.

Starting January 19th, I’m hosting an online JavaScript book club that is free and open for all to attend. We will be reading the free You Don’t Know JS series. We'll be kicking off the club with reading the first book in the series: Get Started. We will always meet online (on Zoom) so you can join from anywhere in the world.

So... why should you join?

Whether you're already working as a JavaScript developer or more of a beginner to JS, you're probably working on leveling up your understanding of JS. Instead of doing this alone, we'll meet weekly and learn together as we read You Don't Know JS--a free book series that is considered one of the best resources on JS.

Here are the next steps if you're interested in joining the club:

Join our email list to get your invitation to the club by email, and to get updates on future books or community events. (https://twitter.com/Madisonkanna) and I'll send you the link again.
Vote for what time you'd like the club to meet at. The club will meet on Sundays but the time chosen will be based on attendees availability. Once you join the discord, you'll find the pinned poll to vote on a time.
Introduce yourself in the discord, and start reading chapter 1.
Remember that you don't need to attend every meeting! Just make it when you can.

If you're still thinking of joining but would like more details, here's some more info on the book club.

When you think of a book club, you usually think of people meeting to discuss a book. Instead of only having discussions, our book club will have themes to each week so we can actively learn together. We'll alternate between discussion week and teach week.

For discussion week, we’ll break up into small groups and each person will share either one thing they learned and a comment or question they have on it, or one thing they struggled with in the chapter. This will give us the opportunity to learn from each other and share our takeaways or struggles with the chapter. For discussion weeks, you'll just need to read the chapter and come up with a comment or question before the meeting.

For teach week, you read the current chapter and then explain just 1 thing you learned from that chapter with a small demo. On the call, we’ll break up into small groups of 5 and present our demos to each other. Each demo can be presented in 4-6 minutes with a minute or two for questions or more comments. This will allow us to practice our coding by creating a demo of what we learned, and cement our learning as we teach it to others.

You might be thinking... OMG! A demo? No way! That's scary and might be a lot of work.

Okay, hold on. The point of the book club is to have a free, friendly and low-pressure place to learn JS with others. We also want to make the book club as valuable to you as possible. And a great way to learn is to teach others what you learned. This will cement your understanding of what you learned.

Our teach week meetings will never be about pouring hours into creating a fancy demo, or about doing scary presentations. Our teach week meeting will be about taking just 1 thing you learned from the current chapter and briefly explaining it in a few sentences or a few lines of code. Or even just one sentence, or one line of code! Did you learn how to createn a object? Share it in a sentence! Did you learn the difference between const and let? Share it!

By taking turns sharing what we learn, we'll gain a better understanding of what we're learning. For our teach week call, you can come to the call with a small demo (such as a line or two of code on Repl.it) and explain what that code means to others. Or if you'd like, simply grab a bit of code or a concept straight from the chapter and explain it to. For teach week, you'll read the current chapter and then pick a concept or idea from the chapter that you'll (briefly!) explain to your fellow book club attendees.

If there’s one thing I learned in the last three years as I went from beginner to working as a JavaScript developer, it is that having a better understanding of the foundations of JS is helpful—no matter what experience level you’re at. It's one thing to read a book and talk about it. It’s another to present a small demo and teach what you learned. You’ll get feedback on what you learned from others, and you'll grow your skills as a communicator as you talk about code to others.

By doing this on our calls, we'll grow as JavaScript developers—-together. :) Our meetings will happen every Sunday, and never go over 1 hour. We’ll meet live on Zoom, where we can talk to each other via video and break up into smaller groups from there. This club will be a place to learn with each other and ask the "stupid" questions--even though there is no such thing. :)

There is no obligation to attend the book club every week. If you can’t make it one week, simply catch up on reading and join us the next week. I've also added a doc with more details on the club.

I look forward to seeing you in the club!

What should you do after you fail the technical interview?

Madison Kanna — Sun, 10 Feb 2019 01:53:33 +0000

Asking for a friend, of course...

But really. I'm not currently interviewing, but I've failed plenty of technical interviews before and I still shudder thinking of my very first one.

I bombed it.

After, I didn't know what to do. I wondered if I should just give up.

Doing poorly in a technical interview meant I wasn't cut out to be a developer. At least, that's what I believed at the time.

Fast forward to today and I know that isn't true. But I often hear aspiring developers talk about how failing technical interviews shook their confidence afterwards and made them question if they could really become devs.

So here's a question that I'd love to hear the answer to from other developers--how do you bounce back after a technical interview? What do you tell yourself? What do you do next?

One thing that's been helpul for me:

Always figure out the answer later. At the end of the interview, it seems like I'll never understand what the solution to the technical problem presented to me was. But later, when I learn as I go over it, I see that I can. That helps rebuild my confidence as I identify the knowledge gap that preventing me from understanding the problem, and I close that gap.

But I wish I would have known this sooner. That's why I created this thread.

In your experience, what should you do after you fail the technical interview to ensure that you'll learn and grow as a developer because of the experience, not in spite of it?