// Mentorship Learning To Code

The Finish Line is Closer Than You Think

3 min read · Mentorship
Summary 3 min read

New developers struggle with things experienced developers have long forgotten were ever hard. A lesson from being a CS101 teaching assistant: help lands best from someone whose struggle is recent, and newcomers need to see that the finish line is a peer one step ahead, not a distant expert.

Recently I was helping out a new developer with code they couldn’t get to behave properly. To someone new to programming everything is a big deal. As an experienced programmer, it’s hard to imagine how simple thing like variables can be one of the biggest challenges to newbies. The reality, though, is that we’ve been there too. We had our time when scope and variable naming was something we would spend a lot of time trying to figure out. It’s just been so long, that we don’t relate anymore.

In college, I was a TA for CS101. I was the TA immediately the following semester after I took the course. It sounded ridiculous at first. Imagine a 7th grader teaching a 6th grader. That would be odd, wouldn’t it? But the professor, the actual person teaching, made a very good point at the time. He said that we are the ones who would relate the best with the students, the struggle of that course is still fresh in our mind and our experience is the closest to theirs. Which is why we would be better suited to help the current students in office hours than he is because when you can relate to the problems the other person is facing you’re better equipped to help them through it.

That said, it’s not only important to be able to relate to the person facing the problem, it’s as important for the person you’re helping to be able to relate to you as well. It is important for someone who is struggling to know that the finish line is reachable. If the finish line is a professor with a Ph.D. when they’re still in their first semester of college, that finish line will not seem achievable and realistic. Whereas if you make it evident that the finish line is much closer, as in a peer who’s only one semester ahead, the goal will seem much more possible. The professor knew that back then, and it’s been something I’ve kept with me all this time, especially when dealing with people who are just beginning their career in development.

Now back to the conversation with the new developer. The mistake they made was a silly one, but a silly mistake any developer could make, regardless of experience level. So it was great to see someone else in the group chime in with: “I suspect everyone here has made this exact bug”. I was about to say the same exact thing. It just made a much bigger impact coming from someone else, at least in my opinion. It also felt natural and genuine. And I really liked that it was said. It’s important to let new developers know that the stuff they struggle with are things everyone else has struggled with at one point in their career. Writing code is something that takes a lot of time to click, and each person gets there at a different pace. It’s OK if a newcomer isn’t there yet. It will click. It just requires patience.

So to all the new developers out there I say: be patient, give it time, it’s OK if you are making silly mistakes at this time, and more importantly it’s definitely OK to ask about anything you are unsure of. We are not judging you, we were you at one point, and we want to help you.

Bear & Giraffe Advisory

We partner with founders and tech leads to build sustainable Rails architecture, untangle monoliths, and scale pragmatic systems.

Schedule a Strategy Call
ESC

Type to search 38 posts