SaiTeja Addepalli’s Post

‼️𝗧𝗵𝗲 𝗕𝗶𝗴𝗴𝗲𝘀𝘁 𝗠𝗶𝘀𝘁𝗮𝗸𝗲 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿 𝗖𝗼𝗱𝗲𝗿𝘀 𝗠𝗮𝗸𝗲, When I started learning coding, I thought trying multiple languages would make me better. Python one day, HTML the next, then CSS, then something else. It felt productive. It felt like progress. But in reality, I was just confusing myself. 🤔𝗪𝗵𝗮𝘁 𝗜 𝗥𝗲𝗮𝗹𝗶𝘇𝗲𝗱: Jumping between languages doesn’t make you a developer. It makes you someone who knows a little about everything and masters nothing. I was unknowingly developing a translator mindset instead of actually understanding how to build things. ✅𝗪𝗵𝗮𝘁 𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗪𝗼𝗿𝗸𝘀 Pick one language. Go deep. Build small projects. Stay consistent. That’s where real growth begins. I made a short video explaining this mistake and how to fix it. If you are starting your coding journey, this might save you a lot of time. 🎥🌐Watch here: youtu.be/d2J1m-MgkWc 🫵𝗪𝗵𝗮𝘁 𝗮𝗯𝗼𝘂𝘁 𝘆𝗼𝘂: Are you focusing on one language or jumping between many #coding #programming #learncoding #developer #beginners #python #webdevelopment #techtips YouTube

Most self-taught devs don’t fail because coding is hard. They fail because they never learned how to learn. A lot of people treat tech like a buffet: Today Python. Tomorrow JavaScript. Next week AI. No plan. Just vibes and 47 open tabs. Three months later: “I’ve been learning… but I’m not confident.” Confident in what exactly? Here’s the truth: Watching tutorials ≠ learning Copy-pasting ≠ understanding Recognizing code ≠ building code Real learning looks like this: • You struggle (a lot) • You build while learning • You get stuck and figure it out • You break things, then fix them • You revisit concepts until they click Use AI wisely: Don’t copy answers — ask for hints Don’t outsource thinking — sharpen it Certificates help with structure, not skill. Projects are your real proof of work. And please — use GitHub. Show your progress. The real shift: Stop asking “What next?” Start asking “Can I build with what I know?” Because one person collects courses… Another builds competence. Guess who gets paid? Learning how to learn is the real skill. Master that — everything else follows. #LearnToCode #SoftwareDevelopment #SelfTaught #Programming #WebDevelopment #CodingJourney #TechCareers #DeveloperLife #100DaysOfCode #BuildInPublic #CareerGrowth #Upskill #TechSkills #AItools #Productivity

Last Sunday, I walked into a session by Anand Kumar sir with zero coding knowledge. No Python. No Java. No C++. Nothing. Honestly? I almost didn't go. I kept thinking — "What will I even understand there? This is not for me." But I went anyway. And then he introduced us to something called Vibe Coding. I didn't fully get it at first. I was sitting there, slightly lost, watching everyone around me nod along. That uncomfortable feeling of being the only one who doesn't "get it" — yeah, I know that feeling too well. But here's the thing — by the end of that session, I had built my own plugin. ME. Someone who has never written a single line of code in their life. That moment felt unreal. Vibe Coding isn't about syntax or algorithms. It's about expressing what you want and letting AI do the heavy lifting. You bring the idea, the intent, the "vibe" — and the tools do the technical work. For someone like me, that changes everything. I always thought tech was a world I'd have to watch from outside. Last Sunday proved otherwise. If you've been holding back from exploring tech because you feel "not technical enough" — this is your sign to go explore Vibe Coding. The barriers are coming down, one session at a time. 🙌 #VibeCoding #AIForEveryone #NoCode #LearningJourney #AnandKumar

Some people treat tech like a race. I’ve started treating it like a mirror. Here are a few things I’ve noticed while learning to code: - You can finish a 10‑hour course and still freeze on a 20‑line project. - The person who quietly reads documentation often moves faster than the one who talks about how many languages they “know.” - 90% of “being good” is just not quitting when the 5th error appears on the same line. Tech looks like it’s only about tools and frameworks, but most days it feels like you’re debugging your own thinking. You see how you react when things break, how patient you are when nothing works, and how honest you are about gaps in your understanding. Somewhere between broken builds and tiny wins, you stop chasing the image of a “perfect developer” and start respecting the version of you that shows up, experiments and learns in public. Maybe the real measure of progress in tech is not how many buzzwords you can list, but how many times you’re willing to open the editor again after it went wrong yesterday. What has your tech journey quietly taught you so far? #TechThoughts #WomenInTech #Python #WebDevelopment #LearningInPublic #StudentToDeveloper #CareerGrowth

🚀 Day 32 of My Coding Journey — Mastering Binary Search Today I solved the classic Binary Search problem (LeetCode 704), and it reinforced one important concept: 👉 Divide and conquer can turn O(n) problems into O(log n). 💡 What I practiced today: Iterative Binary Search (most optimal & commonly used) Recursive Binary Search (clean logic, but uses stack space) 🔍 Key Learning: Instead of scanning the whole array, we eliminate half of the search space in every step. That’s why Binary Search is extremely powerful for sorted data. 📌 Approach (Recursive): Find mid index Compare with target If smaller → search right half If larger → search left half Stop when low > high ⚡ Time Complexity: O(log n) ⚡ Space Complexity: Iterative → O(1) Recursive → O(log n) (due to call stack) 💭 My Takeaway: Binary Search looks simple, but mastering edge cases (like overflow in mid, base conditions) is what actually matters in interviews. 📈 Slowly building strong fundamentals for problem solving and technical interviews. #Day32 #DSA #BinarySearch #CodingJourney #LeetCode #ProblemSolving #TechLearning

Like a lot of people, I’ve found myself relying more and more on AI tools (Copilot, Claude Code, etc.) for day-to-day coding. They’re useful obviously, and hard to resist, but I’ve started to notice that I’m not always thinking through problems as carefully as I used to. So recently I decided to try working through a few small JavaScript problems entirely by hand (pen and paper, no editor, no autocomplete, no AI). It was harder than I expected. Not because the problems were advanced, but because I had to think so much more slowly and carefully and remember syntax I haven't had to remember for awhile. It also reminded me of the research showing that writing by hand improves retention and understanding compared to typing. I’m not sure how strong the analogy is, but it does seem plausible that the same applies to coding—especially now that so much of the “easy” thinking is offloaded to tools. Out of that experiment, I ended up putting together a small workbook of JavaScript problems specifically designed to be done by hand—not beginner-level syntax drills, but also not LeetCode-style interview problems. More like “everyday reasoning” problems that force you to trace through code and think carefully. If that sounds interesting, you can check it out here: https://lnkd.in/eD_r7nDj I'm mostly curious if anyone else has tried something like this, since I hadn't really come across suggestions for writing code literally by hand on paper.

💻 Want to start coding but don’t know where to begin? Start here. Most beginners overcomplicate coding… But the truth is — it’s simpler than you think. 🚀 Follow this roadmap: 1️⃣ Understand what coding really is 2️⃣ Pick ONE language (Python / HTML+CSS / JavaScript) 3️⃣ Learn the basics → variables, loops, functions 4️⃣ Build small projects (calculator, to-do app, portfolio) 5️⃣ Practice daily (even 20–30 mins matters!) 6️⃣ Level up → Git, APIs, frameworks 7️⃣ Build something BIG 👉 Reality check: You don’t need 10 courses. You need consistency + real projects. 🔥 The difference between beginners and pros? 👉 Beginners consume content 👉 Pros build things 💬 Let’s discuss: If you’re starting today — which language would you pick and why? Drop your answer below 👇 #Coding #Programming #LearnToCode #WebDevelopment #Python #JavaScript #Developers #TechCareer #Beginners #100DaysOfCode

🚀 I just built something I wish I had when I started coding. 💡 It's called Daily Coding Coach — a project I created using Claude (by Anthropic) that acts as my personal coding mentor. ✨ Here's what it does: → Gives me one coding problem daily, starting from beginner level → Doesn't hand me answers — it makes me think first → Breaks problems into smaller parts and walks me through hints → Reviews my code for logic, readability, and performance → Explains time & space complexity in simple terms → Gradually increases difficulty from Beginner → Easy → Medium → Hard → Covers Arrays, Strings, Recursion, Trees, Graphs, Dynamic Programming & more → Throws in interview-style questions, timed challenges, and quizzes → Tracks my weak areas and revisits them 🔥 The best part? It teaches me HOW to think, not just what to code. 🧠 I'm using JavaScript (Node.js) as my primary language, and the progression feels like having a real mentor who adjusts to my pace. 🎯 If you're someone who wants to level up your DSA and problem-solving skills but doesn't know where to start — this approach might work for you too. ⚡ Building with AI to become a better developer. That's the goal. #Coding #JavaScript #DSA #LearningInPublic #AI #Claude #DailyCodingCoach #SoftwareEngineering #BuildInPublic

Python looks simple. It isn’t. Example: a = [1, 2, 3] b = a b.append(4) print(a) Output: [1, 2, 3, 4] Why? Because: Variables store references Not actual values Fix: b = a.copy() Now a remains unchanged. This concept alone explains: Unexpected bugs Shared state issues Side effects in functions If this isn’t intuitive, you will struggle in real systems. Practice Python edge cases here: https://lnkd.in/gAxHAqji

Agentic coding. Vibe coding. AI coding. Lots of phrases. Confusion. Angst. Even anger. Whatever you're feeling, I get it. But this technology isn't going away. And I want to help you master it. Later this month, I'm giving two more agentic coding workshops for #Python coders: • April 23rd, all about OpenCode — what it is, and how to use it • April 26th, advanced Claude Code — MCP, skills, and agents Want to learn more? I'm holding a free info session on Monday, May 21st. A link is below.