Introducing Andor: Open-Source AI Coding Agent for VS Code

How I’m Learning Full-Stack Development (Backend + Frontend) Instead of just writing code, I’ve started following a structured learning system to truly understand how applications work. Here’s my approach 1. Start with a clear algorithm * Backend flow (API logic) * Frontend flow (UI → API → response) 2. Break into steps * Each feature is divided into small steps 3. Go deeper with sub-steps * How control actually moves (line-by-line) * What happens internally in backend & frontend 4. Implement ONE step at a time * Write minimal code * Understand every keyword (why it’s used) 5. Track control flow * Backend: Controller → Service → Repository → DB * Frontend: UI → API call → state update → UI render * Key Insight: “Real learning happens when you understand how control flows, not when you just write code.” * Right now I’m building: Authentication system (Register, Login, Role-based access) #Java #SpringBoot #ReactJS #BackendDevelopment #FullStackDeveloper #LearningInPublic #SoftwareEngineering

Reality of Becoming a Full-Stack Developer💻 At the beginning, everything feels impossible. “I can’t build the frontend.” 🎨 “I can’t write backend logic.” ⚙️ “I don’t understand databases.” 🗄️ “I have no idea how deployment works.” 🚀 Every part feels like a different world. But something changes when you stop saying “I can’t” and start saying “I’m learning.” 📚 Slowly you begin to connect the dots: • UI talks to APIs 🔗 • APIs talk to databases 🗄️ • Everything works together as one system 🧩 You realize something important: Being a Full-Stack Developer isn’t about mastering everything at once. It’s about consistent progress across the stack. 📈 At first it’s syntax, bugs, and confusion. 🐛 Later it becomes architecture, systems, and problem-solving. 🧠 Errors stop being scary — they become clues. 🔍 Debugging becomes a skill. Patience becomes a requirement. And the biggest shift happens in your mindset: From “Can I do this?” 🤔 to “I’ll figure it out.” 💡 Full-stack development isn’t about knowing everything. It’s about being curious enough to learn, resilient enough to keep going, and resourceful enough to connect the layers. Still learning. 📚 Still building. 🛠️ Still evolving. 🚀 #ProgrammingLife #DeveloperJourney #CodingLife #LearnToCode #DeveloperMindset #CodingJourney #TechLearning

Modern Dev Playbook (Industry Level) In today’s tech world, coding is not enough thinking like a modern developer is what sets you apart. Here’s the Real Playbook Used by Top Developers: Write Clean, Scalable Code Not just working code build systems that grow. Follow best practices, design patterns, and keep everything maintainable. Master One Stack, Understand Many Go deep in one technology (React, Django, Node), but stay aware of trends across the ecosystem. Version Control is Your Backbone Git isn’t optional it’s your daily tool. Learn branching, pull requests, and team collaboration. Think in Systems, Not Just Features Understand how frontend, backend, APIs, and databases connect. Big picture real power. Debug Like a Pro Errors are not problems they’re clues. Learn how to read logs and solve issues efficiently. Stay Consistent, Not Perfect Top developers don’t wait for motivation they build daily habits. Bonus Mindset: Your code is your identity write it like your future depends on it. If you’re serious about becoming a professional developer, start following this playbook today. Growth is not magic it’s discipline smart learning. #WebDevelopment #Programming #DeveloperMindset #ModernDev #CodingLife #TechPakistan #LearnToCode #SoftwareEngineer

💭 During my LeetCode grind, I ran into a real problem… You keep solving problems daily… but after a few days, you can’t even remember what you solved. No proper way to revise, no clean tracking, nothing structured. So I started looking for tools that could help me track my submissions… but honestly, I found nothing that actually solved this properly. Then I went hunting for APIs 👀 I came across a few options — but they had issues: • Strict rate limits • Not reliable enough for real projects • Not scalable if a user has a lot of submissions None of them felt “production-ready”. Finally, I dug deeper and reached the LeetCode GraphQL API… It was powerful — but not straightforward. Still, I decided to build on top of it and make it usable. And that’s how this came to life 👇 ✨ LeetTrack — a simple LeetCode progress tracker 🔗 https://lnkd.in/dPJYR32Z 🚀 What it does: • 📅 Revision Mode → revisit problems from any date range • 📊 Clean dashboard to actually see your progress • 📌 Easy / Medium / Hard breakdown • 🧾 Recent submissions, properly structured ⚡ Zero friction: • No login required • Just enter your username and start instantly ⚙️ How it works: • Fetches your latest 20 submissions initially (API limitation) • Then keeps auto-syncing in the background • Builds your own personal dataset over time 🛠️ Built using: • Backend: Pure Java + MongoDB • Frontend: Next.js + Tailwind CSS • Deployment: Render + Vercel 📌 Code : Frontend Repo: https://lnkd.in/dJCejDSw Backend Repo: https://lnkd.in/daiNFrf3 Built this to solve a real problem I personally faced — simple, useful, and no unnecessary complexity. If you’re grinding LeetCode, this might actually help you stay consistent 👇 Would love your feedback 🙌 #LeetCode #FullStack #Java #NextJS #WebDevelopment #CodingJourney #Projects

🚀 I spent the last few weeks studying 5 open-source repos with 200K+ combined GitHub stars. Superpowers (108K ⭐), claude-mem (39.9K ⭐), awesome-claude-code (30.9K ⭐), ruflo (24.8K ⭐), and ui-ux-pro-max-skill. Each solves ONE piece of the agentic coding puzzle: 🔹 One gives you workflow methodology 🔹 One gives you session memory 🔹 One curates 1,234 skills 🔹 One orchestrates multi-agent swarms But nobody had built the layer that makes them all WORK TOGETHER — while cutting your token costs by 70%. So I built it. 👇 Meet AgentKit: The intelligent orchestration layer for AI coding agents. One install. 10 platforms. 5 architecture layers: 🧠 Smart Skill Router — Classifies your task in <10ms, loading only 2-5 relevant skills instead of dumping everything into context. Impact: 45,000 tokens → 5,000 tokens per session. 💾 Project Memory Graph — SQLite knowledge graph that remembers your architecture decisions, API patterns, and bug fixes across sessions. No more re-explaining your codebase. 💰 Token Budget Intelligence — Auto-routes Haiku for simple tasks, Sonnet for standard work, and Opus only when you need it. Thinking budget auto-tunes from 0 to 32K tokens based on complexity. Impact: $200/mo → ~$60/mo. ⚡ Workflow Engine — Enforces Research → Plan → Execute → Review → Ship. Quality gates run after every edit. Can't skip planning. Can't skip tests. 🌍 Universal Platform Layer — One SKILL.md source of truth, auto-converting for Claude Code, Cursor, Codex, Gemini CLI, Antigravity, OpenCode, Windsurf, Aider, Kilo Code, and Augment. It's fully open-source (MIT), published on npm, and installs in one command: 👉 npx agentkit init Why did I build this? As a Gen AI developer who builds agentic systems in production for FinTech and Logistics clients, I was spending $200+/month on Claude Code. I kept watching tokens drain on skills that weren't even relevant to my current task. I knew there had to be a better way. This is that better way. 🔗 GitHub: https://lnkd.in/dcNPmGsX 🔗 npm: https://lnkd.in/dG6rZVBg If you use Claude Code, Cursor, or any AI coding agent — give it a try and let me know what you think! Star ⭐ the repo if you find it useful. Open an issue if something breaks. PRs are always welcome, especially new skills for languages I haven't covered yet. #OpenSource #ClaudeCode #AI #DeveloperTools #AgenticCoding #TokenOptimization #GenAI

𝗪𝗮𝗸𝗲 𝗨𝗽, 𝗧𝗵𝗮𝘁 𝗧𝗲𝗰𝗵 𝗬𝗼𝘂 𝗟𝗲𝗮𝗿𝗻𝗲𝗱 𝗬𝗲𝘀𝘁𝗲𝗿𝗱𝗮𝘆? 𝗬𝗲𝗮𝗵, 𝗜𝘁'𝘀 𝗗𝗲𝗮𝗱. ☠️ Ever notice how your feed is filled with "X is Dead" takes? Git? Dead. REST? Dead. Docker? Dead. JWT? Dead. Welcome to 2026, where the half-life of a tech stack is shorter than your coffee break. The Acceleration is Real • 2010: "Learn jQuery, it'll last forever!" • 2015: "React is the future" • 2020: "Kubernetes is everything" • 2025: "Have you tried [framework from last week]?" Every new tool solves problems created by the last "revolutionary" tool. We're building abstractions on top of abstractions, while somewhere at the bottom, a dev just wants to ship a login form.The Uncomfortable Truth 𝗬𝗼𝘂 𝗰𝗮𝗻'𝘁 𝗸𝗲𝗲𝗽 𝘂𝗽. 𝗔𝗻𝗱 𝘁𝗵𝗮𝘁'𝘀 𝗼𝗸𝗮𝘆. The game isn't about knowing every framework. It's about: 1. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀 - HTTP doesn't care about your JS drama 2. 𝗣𝗶𝗰𝗸𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗯𝗮𝘁𝘁𝗹𝗲𝘀 - Learn what matters for 𝘺𝘰𝘶𝘳 work 3. 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗿𝗮𝗻𝘀𝗳𝗲𝗿𝗮𝗯𝗹𝗲 𝘀𝗸𝗶𝗹𝗹𝘀 - Problem-solving > tool mastery The Real Question Is Git actually dead? No. REST? Still running in production. Docker? Check your containers. But will there be newer, shinier alternatives? Absolutely. Every. Single. Week. The developers thriving aren't chasing every trend. They know how to learn fast, read docs, and ignore the noise. 𝗧𝗵𝗲 𝗻𝗲𝘅𝘁 𝘁𝗶𝗺𝗲 𝘆𝗼𝘂 𝘀𝗲𝗲 "𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗫 𝗶𝘀 𝗗𝗲𝗮𝗱": The person making millions of API calls to REST endpoints while running Docker containers and using Git isn't worried. They're too busy shipping code. 𝗪𝗵𝗮𝘁'𝘀 𝘆𝗼𝘂𝗿 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆? 𝗖𝗵𝗮𝘀𝗲 𝘁𝗿𝗲𝗻𝗱𝘀 𝗼𝗿 𝗳𝗶𝗻𝗱 𝘇𝗲𝗻 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗵𝗮𝗼𝘀? 💀 𝘗.𝘚. - S𝘰𝘮𝘦𝘵𝘩𝘪𝘯𝘨 𝘯𝘦𝘸 𝘭𝘢𝘶𝘯𝘤𝘩𝘦𝘥 𝘸𝘩𝘪𝘭𝘦 𝘺𝘰𝘶 𝘳𝘦𝘢𝘥 𝘵𝘩𝘪𝘴. #Technology #SoftwareEngineering #TechTrends #DeveloperLife #ContinuousLearning

Came accross my first tech blog post on Medium the other day. April 2020. "Build a multi-step form with React Hooks, Formik, Yup and MaterialUI." Six years ago. Shortly after that, I joined NAB. That turned out to matter more than the blog post. Many great colleagues and mentors I met there helped me grow from a too-narrow, frontend-obsessed developer into a more balanced engineer. Less fixating on specific libraries and tools, more thinking about systems, trade-offs, and people. Now in 2026, it does feel like technical blog posts are becoming obsolete. AI can write code for you faster than you can read the tutorial explaining how. Why spend 10 minutes reading a walkthrough when you can get a working answer in 30 seconds without understanding any of it? But I think tech writing still has its place. It just has to evolve. The old "step 1, step 2, here's the code" format? Yeah, AI replaced that. But posts that help you build real understanding, that push you to think about why and not just how? Those are harder to replace, because they change the way you approach problems, not just the code you ship. I still have a lot ahead to learn and a lot of catching up to do in this fast-moving world. Writing tutorials and building tools on Upskills is how I keep myself sharp. Same reason I wrote that Formik post in 2020, it’s just a different shape now.

For a while, I’ve been learning consistently but keeping most of my progress to myself. I’ve decided to change that. Going forward, I’ll be sharing updates every 2–3 days to document my journey and stay accountable. As I get more hands-on and start building, I’ll also share practical work and projects along the way. This is Part 1 of Week 2. ✅ WEEK 2 | POST 1 Understanding Node.js: Why It’s Such a Big Deal This week, I gained a clearer understanding of what Node.js really is, and it has genuinely reshaped how I view backend development. Here are my key takeaways: 🔹 Node.js isn’t a language or framework It’s a runtime environment that allows JavaScript to run outside the browser, powered by Google’s V8 engine. This extends JavaScript’s capabilities to work with files, networks, and operating systems. 🔹 Why Node.js is fast and scalable Node uses a non-blocking, asynchronous architecture. Instead of waiting for one task to finish before starting another, it handles multiple operations efficiently. This makes it well-suited for data-intensive and real-time applications. 🔹 Modules promote cleaner, safer code Every file in Node operates as its own module with a private scope. This prevents unintended global variables and function conflicts. Only what is explicitly exported becomes accessible elsewhere, improving maintainability. 🔹 Core modules simplify development Node comes with built-in tools such as: • fs (file system) • os (operating system information) • path (file path utilities) • http (server creation) • events (event-driven programming) These make it possible to build functional backend systems without additional installations. Each concept I learn continues to reinforce how Node.js makes backend development both efficient and accessible, especially for developers coming from JavaScript. Looking forward to building more and sharing the process. #NodeJS #BackendDevelopment #JavaScript #LearningInPublic #DeveloperJourney #TechTraining #WebDevelopment #Coding #TSAcademy

AI agents are quickly changing how routine work gets done, including in software development. In my latest DZone article, I walk through how to build a GitHub triaging AI agent using JavaScript and TypeScript. I wanted to keep the article practical and easy to follow for developers who want to explore Agentic workflows without stepping away from the JavaScript ecosystem. Read here: https://lnkd.in/eEtG2EdU Curious to hear where others see AI agents making the biggest impact. #AI #AIAgents #JavaScript #TypeScript #SoftwareDevelopment #GitHub #LLM