The One Where We Get Better at Coding!

It's 2025 and we need to IMPROVE our coding skills girl! Here's how I'm doing it:

1️⃣ Solve a Simple Algorithm

I hop onto platforms like LeetCode or HackerRank and pick a beginner-friendly problem. It’s not just about solving it but learning how to break the problem down into smaller, logical steps. Plus, the satisfaction of seeing all those test cases pass? Priceless.

2️⃣ Build a Small Script

There’s nothing like creating something functional! I try automating small tasks like renaming a batch of files or scraping data from a website. These projects help me practice writing clean, efficient code while solving real-world problems.

3️⃣ Debug Someone Else’s Code

Diving into someone else’s logic might feel intimidating at first, but it’s an incredible way to improve. I learn to spot patterns, understand different coding styles, and develop better debugging techniques.

🧠 Which one are you excited to try first? Let me know in the comments, and follow for more coding tips and challenges! Let’s grow together. 🚀

#lemon8partner #learnonlemon8 #studytips #studying #studyinspo

2025/2/11 Edited to

... Read moreSo, you're looking to really dive deep into improving your coding skills, especially with tools like LeetCode and optimizing your workspace? I'm right there with you! After sharing my top three methods, let's zoom in on how to make those methods even more effective with the right tools and environment. Let's talk about the 'LeetCode on iPad' query – it's something I've experimented with a lot! When I'm not at my main coding station, my iPad becomes my mini problem-solving lab. I usually access LeetCode directly through Safari. It works surprisingly well, especially with the integrated code editor. For tougher problems that require more thought, I often use the iPad's split-screen feature: LeetCode on one side, and Apple Notes or GoodNotes on the other. This allows me to diagram complex algorithms, trace variable values, and brainstorm different approaches without switching between physical notebooks and screens. I've found that using an external Bluetooth keyboard (even a small, portable one) significantly boosts my efficiency, making the typing experience much smoother than the on-screen keyboard. While it might not replace a full-fledged development environment like Eclipse IDE for larger projects, for focused algorithm practice, especially when you want to break away from your desk, it's an absolute game-changer. It forces a more deliberate, pen-and-paper style of problem-solving before I even start typing code, which has genuinely improved my logical thinking. It’s like having a portable coding challenge companion! Now, for the 'coding problem-solving desk' aspect – this is where consistency and comfort meet productivity. My personal setup has evolved over time, and it's something I continually tweak to maximize my focus when I'm deep into debugging or building a new script. My core is my MacBook connected to a large external monitor. This dual-screen setup is non-negotiable for me; having code on one screen and problem statements, documentation, or even a tutorial on the other makes a world of difference in workflow. I also swear by an ergonomic chair, as spending hours at a desk requires proper support. My FlexiSpot standing desk is another essential; being able to switch between sitting and standing throughout the day helps keep my energy levels up and prevents stiffness. For input, I prefer a mechanical keyboard for its tactile feedback and a comfortable mouse. Good lighting is often overlooked but crucial – I use a desk lamp that minimizes glare and eye strain. I also keep a physical notebook and a favorite pen on my desk. There’s something incredibly satisfying about jotting down pseudocode, sketching out data structures, or simply brainstorming ideas away from the glow of a screen. This problem-solving 'desk' isn't just a collection of items; it's a dedicated space designed to foster deep concentration and efficient learning, whether I'm tackling a new algorithm or refining a small script.

11 comments

Lizzie's images
Lizzie

what do you recommend for debugging someone else's code if you're not in school?