Solving 75 LeetCode Questions

Well, it’s that time again. I have to prepare for a coding interview. I am getting tired of this. Hey, I chose this career. I know if I solve enough of these problems, I will be able to crack a few interviews. But I am also trying to learn some new programming languages. namely Go and Rust.

So, here is my plan. I will attempt to solve these 75 Problems in three languages. JavaScript is my native language, and I speak JavaScript at home too. And on top of that, I will attempt the problem in Go and Rust. I am hoping this will familiarise me with the syntax and all the nicks and nacks of those two languages (Go-lang and Rust).

But here is the problem: even though I have over 10 years of experience writing enterprise-level software, I still have to go through these coding challenges to even be considered for a first face-to-face interview. I am not saying that’s how all tech companies operate, but most of them do. If the whole Soham Parek case has taught us anything, Trust is more important than anything. I don’t want to make this a rant post. But rather, I want to document my learning experience doing this exercise, to see if it makes me a better programmer in all these languages.

Let the learnings begin… But here is the thing. And it’s a big one. I hate doing these problems. They are the most boring thing a programmer can do with their time, according to me. So I am going to have to make this a fun experience for myself. One part of making this a fun experience is writing about it. I am not a writer by profession. But I have grown fond of documenting my journey, things I am doing. It was very successful with the Discovering mechanical keyboard Journey. So why not try it here, too?

And on top of this, I also want to improve my Laptimes with my Sim Racing Hobby. So the plan is to keep me motivated with alternating learning sessions between improving at my Hobby and working on these problems.

So the Plan is to solve a problem, however long it takes for me. I am not timeboxing these initially. simply because the goal is to see if they actually learn something, not improve my coding speed.. Once I finish a problem, I will take a break and jump on my Sim Rig for an online race or work on improving laptimes in one of my favourite tracks.

So far, it sounds like a good plan to me. What could go wrong.

Update: September 25, 2025

Well, it’s been a few months, and I have not yet done anything. Time to get back on track.