Ashish Yadav’s Post

Yesterday, I joined the Open Source Friday live stream featuring Serena from GitHub. It was an insightful deep dive into collaborative development and real-world problem-solving. Watching experts navigate a codebase in real-time offers a perspective you can't get from documentation alone. It highlights the critical thinking, the debugging logic, and the architectural "why" behind every decision. My main takeaways from the session: Community-Driven Growth: Open source is about collective intelligence and making technology inclusive. The Learning Curve: Continuous exploration remains a constant, even for seasoned developers. The Reality of Building: Exploring the Serena project (https://lnkd.in/d9EKMbCn) was a great reminder that every polished feature begins with iterative, sometimes complex steps. For those looking to go beyond watching and start using it, here is how to get Serena MCP running on your machine: 1. Installation on Windows The simplest way to run Serena MCP is using uvx. It allows you to run Python packages on the fly without a complex local setup: Ensure Python is installed. Use uvx in your terminal to execute the package directly as per the documentation. This keeps your environment clean while giving you full access to Serena's capabilities. 2. Setup in VS Code (using GitHub Copilot) Once the server is ready, you can integrate it into your workflow in seconds: Add a configuration file: Create a .vs code folder in your project and add an mcp.json file. Register the server: Use the "Add Server" button or the command palette to link your MCP server. You can run it via a local command or even a Docker image. Interact: Once connected, your tools will appear directly in the Copilot chat, allowing you to query the Serena codebase or perform tasks through the MCP protocol seamlessly. A big thank you to Serena and the GitHub team for promoting the "Build in Public" mindset. 🚀 Are you currently contributing to any open-source initiatives or exploring MCP tools in your IDE? I’d love to hear about your experience in the comments. #OpenSource #GitHub #SoftwareEngineering #MCP #VSCode #SerenaProject #WebDevelopment #LearningInPublic #TechCommunity

💻 Debugging Chaos: The Real Developer Experience 😅 You sit down to code with full confidence… “This should be easy.” 30 minutes later 👇 ☕ 3 cups of coffee 🐛 10 new bugs 😵 0 idea what’s going on Your screen is full of errors… Your code looks fine… And somehow, nothing works. At this point, debugging feels like: 👉 Staring at the same code for hours 👉 Googling the same error 20 times 👉 Whispering “please work” before hitting run And the plot twist? It was just a tiny mistake… A missing bracket. A typo. Something so small. But here’s the thing 👇 This chaos is part of the journey. Every frustrating moment: ✔ Sharpens your attention to detail ✔ Builds real problem-solving skills ✔ Makes you a better developer over time So if your code is breaking today… Good. That means you’re learning. Because behind every great developer is… a long history of debugging chaos. 🚀 #Debugging #WebDevelopment #CodingLife #ProgrammerHumor #LearnToCode #DeveloperJourney #100DaysOfCode

🚀 Just built and published my first Go REST API project on GitHub! I built a Library Management System from scratch using Go —  no frameworks, no external libraries, just pure Go standard library. What the project does: → Add and list books in the library → Members can borrow books with automatic due date (14 days) → Return books and get fine calculated automatically → Fine system: 5 rupees per day after due date → Full input validation on every route Tech used: → Go (Golang) → net/http — built-in router and server → encoding/json — JSON parsing → In-memory storage using Go slices API Endpoints I built: → GET /books      — list all books → POST /books      — add a new book → POST /borrow     — borrow a book → GET /borrow/{id}   — check borrow status → POST /return     — return a book → GET /fine/{memberID} — check member fines This project taught me: → How HTTP servers work in Go → JSON encoding and decoding → Routing with ServeMux → Input validation patterns → Writing clean commit messages → Thinking like a backend developer GitHub link in comment👇 #golang #go #backend #restapi #programming #100daysofcode #webdevelopment #opensource #github #coding #softwaredevelopment #beginnerprogrammer #learntocode #india

Every senior developer I know follows this rule: "If you debug for more than 30 minutes, you're debugging the wrong thing." I wasted 6 hours debugging last week. The bug? A missing comma in a JSON config. Here's my debugging framework now: Step 1: Reproduce the bug (5 min max) - Can you consistently trigger it? - If no, check environment differences Step 2: Check the OBVIOUS first (10 min) - Typos, missing imports, wrong file - console.log at every step - Check git diff -- did you change something? Step 3: Isolate (10 min) - Comment out everything - Add code back piece by piece - The bug lives where the break happens Step 4: Google SMART (5 min) - Copy exact error message - Add your framework name - Check GitHub Issues, not just Stack Overflow Step 5: Ask for help (0 min wasted) - After 30 min, ping a teammate - Explain the problem out loud (rubber duck method) - Fresh eyes find bugs in seconds Time limit: 30 minutes. After that, you're not debugging. You're spiraling. Save this for your next 3 AM debugging session. #Debugging #Developer #CodingTips #Programming #WebDevelopment #JavaScript #SoftwareEngineering #DevLife

We're shipping a new /init in the next opencode release. It reads your repo before it asks you anything. Figures out what agents actually need, build commands, project conventions, the stuff that's not obvious from a glance. Then asks a small number of targeted questions to fill in the gaps it can't infer. The output is an AGENTS.md that's actually grounded in your codebase. It's not a generic template; you'll need to rewrite it from scratch. Guided setup that does its homework first.

**3 PRs merged into GitHub's spec-kit here's my open-source journey so far** Over the past week, I've had 3 pull requests merged into github/spec-kit an open-source specification framework. --- 🔹 PR #1: Documentation fix (Mar 31) Found that AGENTS.md was out of sync with the actual agent configuration. Several agents were missing from the docs. Synced everything up so developers aren't confused when onboarding. --- 🔹 PR #2: Community catalog extension (Apr 1) Added the fix-findings extension to spec-kit's community catalog, making it discoverable and installable for all users. --- 🔹 PR #3: argument-hint frontmatter for Claude Code (Apr 3) This was the big one. When users typed slash commands like /speckit-plan in Claude Code, there was no hint about what input the command expects. I built a post-processing pipeline that injects argument-hint into YAML frontmatter for all 9 Claude Code skill commands. Now users instantly see prompts like "Describe the feature you want to specify" right inline. This PR went through: ✅ Multiple rounds of code review with the maintainer ✅ A rebase when upstream merged a major architecture change ✅ 6 targeted tests The maintainer's feedback genuinely improved the final code. --- 📌 What this journey taught me: 💡 Start small (docs fix), build trust, then take on bigger features 💡 Code review isn't criticism it's collaboration 💡 Open source rewards consistency and quality over speed --- 🚀 Currently working on PR #4 adding Table of Contents to generated markdown documents. --- #OpenSource #GitHub #Python #AI #ClaudeCode #SoftwareEngineering #SpecKit #WomenInTech

Ever wondered what actually happens under the hood when you type git commit or git merge? I decided to move beyond just using developer tools and actually understand the system architecture behind them. So, I’ve been developing CAF, a custom Version Control System written in Python and C++ to replicate the core mechanics of Git. Building a VCS is a masterclass in file systems, graph theory, and data structures. It's more than just a file-copier, it’s about managing state and history: 🔹 Object Database: Cryptographically hashed blobs and trees (DAG) for content-addressable storage. 🔹 Branch Namespacing: Native directory-based branch resolution to manage complex workflows. 🔹 3-Way Merge Engine: A custom algorithm capable of finding common ancestors, detecting textual conflicts, and writing Git-style conflict markers for developer resolution. 🔹 Full CLI Suite: Includes robust implementations for checkout, log, status, and tag, providing a familiar, Git-like developer experience. 🔹 DevEx First: Packaged the entire engine inside a Dockerized GitHub Codespaces environment for zero-setup testing. If you want to see the engine in action (or try breaking the merge algorithm right in your browser), you can spin up a live environment from my repository here: 👉 https://lnkd.in/dMiDs6fp #SoftwareEngineering #Python #SystemArchitecture #Git #OpenToWork #Backend

Readable Code Is Better Than Clever Code Every single time. Couple years ago I used to write clever code. The kind that made me feel smart. One-liners. Nested ternaries. Stream pipelines that did five things at once. 🧠 I thought: "If it's hard to write, it must be hard to read. That's a good thing." I was wrong. The Problem Clever code is a puzzle. The person reading it (future me, usually) has to solve that puzzle before understanding what the code actually does. At 3 AM, debugging a production outage, I don't want puzzles. I want clarity. I want obvious. I want boring. What I Do Now I write code my junior self would understand. Simple names. Small steps. One idea per line. If I feel clever, I stop and simplify. Cleverness is usually just complexity wearing a fancy hat. The Truth Code is read more times than it's written. Every minute you save by being clever costs hours for everyone who follows. Readable code isn't less sophisticated. It's more considerate. 😌 #CleanCode #Readability #SoftwareEngineering #CodingStandards #ProgrammingWisdom #SeniorDeveloper #Java

Manage your localhost ports like a PRO 🔥 Meet Port-Whisperer — a sleek CLI tool that lets you see exactly what’s happening behind your ports and take control instantly. ✨ What you can do: → List all active ports → Identify which app is using each port → Kill processes on unused or blocked ports → Monitor ports in real-time No more guessing what’s running in the background 👀 🔗 Source: https://lnkd.in/ehjiairk #programming #webdevelopment #developer #coding #javascript #opensource #github #devtools #cli #softwaredevelopment #tech #codinglife #developers #frontend #backend #fullstack #computerscience #buildinpublic #productivity #devcommunity

I’m tired of forgetting terminal commands for specific projects. You switch to a repo you haven't touched in a month and immediately think, "Wait, what was the flag for that specific migration again?" or "How do I start this legacy project?" I got fed up with digging through my shell history and rereading the READMEs. So I built QuickRun to keep everything where it belongs: Right inside the project. ⚡ How it works for teams: 📂 Centralized Access: Save commands to a .vscode/quickrun.json file in your repo. 🤝 Shared Knowledge: When you add a new command, just commit it. Now the whole team has it instantly. 🚀 Easy Access: Everyone runs the exact same scripts from a simple sidebar panel. No more searching through READMEs or shell histories. It’s free, open-source, and turns your README into actual, clickable buttons. 🛠️ 🔗 Check it out here: VS Code Marketplace: https://lnkd.in/eaYAn_jj GitHub: https://lnkd.in/eTye2zyA #vscode #developer #productivity #buildinpublic #opensource #coding