I've been building full-stack apps for a while now. But I realized something. I was skipping the fundamentals. So I stopped. And I started DSA from scratch. Here's my exact plan: 🗓 Platform: LeetCode 📌 Goal: 3–5 problems every single day 📚 Topic order: → Arrays & Strings → Hashing → Two Pointers & Sliding Window → Linked Lists → Stacks & Queues → Recursion & Backtracking → Binary Search → Trees → Graphs → Dynamic Programming I know the basics. My weak spot is patterns recognizing WHICH technique to use and WHEN. So my focus isn't just solving problems. It's understanding the pattern behind each problem. I'll be posting my progress every day for 30 days. The wins. The struggles. All of it. If you're on the same journey. let's connect. 🤝 #DSA #LeetCode #100DaysOfCode #developer #competitiveprogramming
Improving DSA skills with LeetCode and daily practice
More Relevant Posts
-
𝐃𝐚𝐲 5/30: 𝐓𝐡𝐞 2-𝐇𝐨𝐮𝐫 𝐁𝐮𝐠 𝐓𝐡𝐚𝐭 𝐖𝐚𝐬 𝐚 1-𝐖𝐨𝐫𝐝 𝐅𝐢𝐱 😅 Spent hours last night fighting a “Not Found” error in my app. My frontend kept asking the backend: “𝘎𝘪𝘷𝘦 𝘮𝘦 𝘵𝘩𝘦 𝘶𝘱𝘭𝘰𝘢𝘥 𝘭𝘪𝘴𝘵.” But the backend only understood: “𝘚𝘢𝘷𝘦 𝘢 𝘯𝘦𝘸 𝘶𝘱𝘭𝘰𝘢𝘥.” They were speaking two different languages. 𝑮𝑬𝑻 𝒗𝒔 𝑷𝑶𝑺𝑻. 𝑻𝒉𝒆 𝒇𝒊𝒙? Changed one word in my code: `𝒫𝒪𝒮𝒯` → `𝒢𝓔𝒯`. Instantly worked. 𝑳𝒆𝒔𝒔𝒐𝒏: In tech, small typos cause big headaches. Always double-check how your app asks for data vs how your server expects it. 2 hours debugging. 5 seconds fixing. Priceless lesson. #30DaysOfCode #BuildingInPublic #LessonsInCode #WebApp #RecruitmentPlatform #Jobs #React #Code #Challenge #Programming #Software #Engineer
To view or add a comment, sign in
-
-
Inside Backend – Day 1 When a user clicks a button in an application, a lot happens behind the scenes. - The app sends a request - Backend processes it - Database is queried - Response is sent back This entire flow happens in milliseconds. Understanding this is the first step to learning backend development. Starting a series to break down backend concepts in simple terms. Day 2 coming tomorrow. Stark Your Backend Journey with Node.js: https://lnkd.in/g_BC6jty #backenddevelopment #webdevelopment #programming #softwaredevelopment #coding
To view or add a comment, sign in
-
Personal Software Development Tools Empower Non-Programmers to Build Apps 📌 Non-programmers can now build custom apps with personal software, thanks to Samuel Girardin’s “The Makers” framework. Designed for rapid, low-friction development, it empowers users to solve niche problems without enterprise complexity. By leveraging Python, Vue.js, and modular tools, this movement turns digital creation into a personal, autonomous workflow-democratizing tech in powerful new ways. 🔗 Read more: https://lnkd.in/djABwydX #Mediumpublication #Developerframework #Nonprogrammertools #Customappbuilding #Samuelgirardin
To view or add a comment, sign in
-
1,400 problems later. When I first opened LeetCode, I stared at "Easy" questions with a completely blank mind. Brute force was my only strategy, and most days, I felt entirely out of my depth. But I made myself a simple promise. Solve just one problem every single day. No exceptions. Some days it took five minutes. Other days, it took hours of reading through discussions just to grasp the basic concept. But slowly, the friction faded. It stopped being about memorizing tricks or just trying to get the green checkmark. I started seeing the underlying patterns. The logic finally began to click. Looking back, the greatest takeaway from this milestone wasn't mastering dynamic programming or graph theory. It was learning the quiet power of showing up. Consistency compounds. A daily habit, no matter how small it feels in the moment, eventually builds a deep, unshakable understanding over time. If you are struggling with a concept right now, don't worry about the big picture. Just focus on today's problem. The rest will build itself. What is one daily habit that has paid off the most in your career? #LeetCode #SoftwareEngineering #ProblemSolving #Consistency #TechCareers
To view or add a comment, sign in
-
-
🚀 Pocket-sized AI coding agent! I just got @JetBrains Junie CLI running natively on my Android phone. 🤯Standard desktop installers aren't built for mobile terminals, but I found a brilliant backdoor to get this powerful tool working perfectly on the go.🔥 The JAR Hack: I completely bypassed the official executable and went straight for the source. By extracting the core 138 MB .jar file directly from the release zip, I built a custom shell script to launch it natively.⚡ The Working Condition: Using Termux and OpenJDK 21, java -jar dynamically targets the extracted file and runs it flawlessly.The result? An enterprise-grade AI CLI agent purring along on a smartphone with an incredibly lean ~340 MB footprint. No heavy emulators, no containers—just pure native Java execution.If you want to run heavy developer tools right from your pocket, I open-sourced the exact reverse-engineered installation method and scripts.👇 Check out the repository here:https://lnkd.in/db4y2YXF #Junie #AndroidDev #Termux #TechHacks #OpenSource #SoftwareEngineering #MobileCoding #AIAgents #JavaDev #10xDeveloper #GitHub
To view or add a comment, sign in
-
-
Got tired of debugging "𝗡𝗼𝗻𝗲𝗧𝘆𝗽𝗲 𝗵𝗮𝘀 𝗻𝗼 𝗮𝘁𝘁𝗿𝗶𝗯𝘂𝘁𝗲 𝗫" errors? Only to realize - 20 minutes later - it was just a missing environment variable. I built a tiny Python package: 𝗲𝗻𝘃-𝘀𝗲𝗻𝘁𝗶𝗻𝗲𝗹 You call it once at the top of your app: from env_sentinel import require require({ "DATABASE_URL": str, "PORT": int, "DEBUG": bool, "OPENAI_API_KEY": str, }) If anything is missing or invalid, it fails immediately with a clear error: EnvironmentError: Environment validation failed: - PORT: missing - DEBUG: cannot convert 'maybe' to bool No dependencies. No config files. Just one job: fail fast, fail clearly. 🚀 Now live on PyPI: pip install env-sentinel 🔗 GitHub: https://lnkd.in/g2XNeuWt If you've ever lost time debugging env issues in production, this might save you a headache. #DevTools #OpenSource #BuildInPublic
To view or add a comment, sign in
-
𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗱𝗼𝗻’𝘁 𝘄𝗮𝘀𝘁𝗲 𝘁𝗶𝗺𝗲 𝗰𝗼𝗱𝗶𝗻𝗴… 𝘁𝗵𝗲𝘆 𝘄𝗮𝘀𝘁𝗲 𝘁𝗶𝗺𝗲 𝗳𝗶𝗻𝗱𝗶𝗻𝗴 𝗳𝗶𝗹𝗲𝘀. Developers don’t waste time coding… they waste time finding files. 🚨 THE PROBLEM Files get saved randomly across your system. Same scripts exist multiple times with different names. Duplicate data keeps growing without you noticing. And the worst part? You know you created a file… but you don’t remember where you saved it. So you keep searching. And wasting time. ⚡ THE SOLUTION — SmartFileManager (Launching very soon 🚀) Automatically organizes all developer files in seconds. Removes duplicate data — even with different file names. Lets you find any file instantly, even if you forgot its location. Opens directly in VS Code, PyCharm, Android Studio. No cloud. No subscription. 100% offline. Built for developers. Still in testing — but early results look promising: 👉 Indexed 483,021 files in under 5 minutes I’m validating the idea before launch. Would you use something like this? What feature would make it a must-have for you? #BuildInPublic #DevTools #Productivity #Python #IndianDeveloper #StartupJourney
To view or add a comment, sign in
-
-
Tip 64: Leetcode is supposed to be fun! Leetcode is a great collection of programming puzzles. The problems are fun to solve, and it's a nice way to flex your brain. The problems are well curated, the tests are extensive, and there is a huge community to practice and learn together. But. Leetcode is considered the Big Gatekeeper, and it's the biggest source of anxiety. "I must learn N LeetCode problems by heart, then I can get a job" -- that's what I hear very often. And N is usually in the range of 100 to 1000. It sounds obvious, but I will still say it. Please, do not try to memorize solutions. It is a dead end. You *may* pass a shallow technical interview with a memorized solution, but it will not get you anywhere beyond that. It's actually better if you do not have the most efficient solution, but can think out loud and speak about the trade-offs as you solve the problem live. Well, it may even be okay if you don't solve the problem at all -- if it's clear that you're solving it, not trying to reproduce the next line of that "best O(1) solution". Try treating Leetcode problems as they naturally are -- fun puzzles. What is the easiest brute force solution? What can be optimized? Which algorithms come to mind when you see it? Would X work? What if we tried Y? How about Z? If you minimize the anxiety ("I must remember them all") and keep the fun ("I have this really silly algorithm in mind... but hey, let me try!"), you might enjoy the process. I know, it's much easier said than done, and anxiety catches us in many ways (waking up at 3am, anyone?). But if solving problems is not fun at all, then... why? #256tipsforjuniordevs (this time posting as a text, to see what works best; the video is available on YouTube from the page linked below in the comments!)
To view or add a comment, sign in
-
Many developers use First() and FirstOrDefault() interchangeably… but they behave very differently First() → throws an exception if no data is found FirstOrDefault() → returns a safe default (null / 0) That small difference can break your app or make it more reliable 💡 ✔ Use First() when you’re 100% sure data exists ✔ Use FirstOrDefault() when data might be missing Save this for later #dotnet #csharp #aspnetcore #backenddevelopment #programmingtips #softwareengineering #developers #coding #learnprogramming
To view or add a comment, sign in
-
-
LeetCode Day 5 : Problem 121 (Best Time to Buy and Sell Stock) Just solved another LeetCode problem. It was "Best Time to Buy and Sell Stock", sounds like a finance problem, right? But here's what I actually learned: My first solution checked every possible buy and sell pair using a nested loop. It gave the correct answer but was O(n²), on a large array with 100,000 prices that's 10 billion comparisons. LeetCode would have thrown a Time Limit Exceeded. The fix? One pass. Track the minimum price seen so far as you move forward. At each day just ask, if I sell today, what's my profit? Update the max profit if it's better. That's it. O(n) time, O(1) space. The insight that made it click, you never need to look back. The best buy point is always the lowest price you've seen so far. So just keep track of it as you go. Seven problems in. The lesson keeps showing up, if you have a nested loop, there is almost always a one pass solution hiding somewhere. The real lesson? Don't just solve the problem. Ask yourself if you can do it in one pass. #DSA #LeetCode #JavaScript #CodingJourney #Programming
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development