Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Urvisha Maniar
Developer Tools I’m Seeing Teams Actually Rely On (Not Just Try Once)
Every year, dozens of new developer tools launch. Most look impressive in demos. Very few survive real, day-to-day engineering work. Spending time around engineering teams lately, I’ve noticed something consistent: the tools that stick aren’t the flashiest — they’re the ones that reduce cognitive load and quietly fit into existing workflows. Here are the categories of developer tools teams are actually relying on today — with real examples — and why they matter. 1.
Legacy Code Got You Crying? Batch Docs Can Help
Legacy systems aren’t just old code. They’re old decisions, old assumptions, and old “temporary” fixes that somehow became permanent architecture. Every team has one. Every developer eventually inherits one. And every sprint gets slowed down by one. But here’s the real punchline: Legacy code doesn’t hurt because it’s old. It hurts because nobody remembers why things were built that way. And that lack of context becomes tech debt.
Engineers Don’t Hate Documentation.
They Hate Being Set Up to Fail at It. Let’s say this clearly: Engineering teams don’t avoid documentation because they don’t care. They avoid it because documentation, as it exists today, is a losing game. It’s slow. It’s invisible. It’s never finished. And the moment you’re done, it’s already wrong. So eventually, even the best teams stop trying. Not because they’re careless — but because the system is broken. “We’ll document it later” is not laziness. It’s self-preservation.
The Open-Source Problem Nobody Talks About (And How AI Docs Can Actually Fix It)
Open-source maintainers know this feeling all too well: You pour hours into building a library, tool, or framework… You open it up to the world… And then: “Hey, I want to contribute — but I have no idea where to start.” That sentence is the soundtrack of open-source maintainability. Most contributors aren’t scared of writing code. They’re scared of not understanding the existing code. And honestly? That fear is justified.
The 12 Developer Mindsets I’ve Seen in My Career (And What They Teach Us About Building Software)
After years of working across engineering teams, open-source communities, product cycles, late-night debugging marathons, and “just ship it” deadlines… I’ve learned one thing: There is no single type of developer. There are mindsets — and they shape everything. You meet them in code reviews, in standups, in Slack threads, in last-minute hotfixes, and in architecture decisions that haunt you years later.
Backend, Frontend & Product Walk Into a Meeting… And AI Docs Finally Make It Less Painful
Every dev knows that meeting. Backend is explaining an API. Frontend is saying “that’s not what we built.” Product is wondering why the app behaves like a gremlin after 5pm. Everyone is talking. Nobody is aligned. And somehow… the feature still ships. (We don’t ask how. We simply accept it.) Why does this happen? Because every team is working with a different mental picture of the system.
🎉 We’re Tackling One of the Tasks Developers Like Least
Let’s be honest: code review is important — but it’s also one of the least enjoyable parts of the job. It takes time. It takes context. It takes energy you usually don’t have at the end of the day. And most of us would rather be… well, actually writing #code. So we’re building something new at Everdone to help with exactly that. Not replacing reviewers. Not doing any heavy, architecture-level magic. Just using AI to make code review less painful, less time-consuming, and a lot easier to start.
Code Reviews: Quality Control or Ego Olympics?
Let's talk about what's really happening in your code reviews. You know that junior who just quit? The one who mentioned in their exit interview that your reviews made them feel like they'd never be good enough? Yeah, that happened on my team. And before you think "well, my juniors love my feedback," ask yourself: would they actually tell you if they didn't? This isn't about pointing fingers. Well, you know what, actually - it is.
Ship Code, Not Chaos: AI Docs Keep Your CI/CD From Becoming CI/See-Ya-Later
CI/CD pipelines are supposed to make shipping code fast, predictable, and drama-free. But when documentation can’t keep up with releases, even the cleanest pipeline can turn into: ❌ “Wait, who changed this module?” ❌ “Why does this API behave differently now?” ❌ “Who approved this… and where’s the reasoning?” Congrats — you’ve unintentionally deployed chaos into production. But here’s the good news: AI-generated documentation is finally fixing one of CI/CD’s oldest bugs — documentation drift.
Lights, Camera, Publish! Dev.to Now Supports Video Cover Links
If you’re someone who loves adding a visual punch to your Dev.to articles, you probably already use the Cover Image feature. But what if you want your cover to be a video instead of a static image? Great news — Dec.to has added a brand new “Cover Video Link” option, and here’s how you can use it to level up your posts. 🎬 What is “Cover Video Link”? With this feature, you can add a YouTube, Loom, Vimeo, or any public MP4 link as the cover for your article.
The AI Tools Nobody Builds (But Every Developer Secretly Needs)
Everyday I see a shiny new AI tool for coding: AI that writes code AI that explains code AI that reviews code AI that documents code AI that fixes bugs you didn’t even know you had Amazing. Useful. Love that for everyone. But being around developers all the time, I’ve realized something: The most exhausting parts of a developer’s job have nothing to do with writing code. And THAT’S where the AI gap is.
How to Automatically Generate Code Documentation from Your GitHub Repo?
Engineering teams want accurate documentation but rarely have the time to write it. Between feature releases, bug fixes, and sprint deadlines, documentation is the first thing that gets pushed aside and the result is outdated, incomplete, or missing internal knowledge. But what if your documentation could update itself, directly from your GitHub repository?
How AI Became My Mental Reset Button in a Chaotic World
I never expected AI to become my calm-down tool. My productivity tool? Sure. My cheat-sheet? Obviously. My “explain this to me like I’m five”? Absolutely. But my mental reset button? Yeah… didn’t see that coming. Tech isn’t always a peaceful place. There’s pressure, speed, too many ideas, too many tabs open (in browsers and in life), and the constant background noise of “learn this” / “ship that” / “don’t fall behind.” Somewhere in the middle of that storm, AI became… my slowdown.
We Upgrade Software Without Question. Why Don’t We Upgrade Ourselves?
I don’t code. But I spend my days around people who do — the late-night builders, the tab-vs-space philosophers, the “I’ll fix it in 5 minutes” liars (we all know it’s never 5 minutes :P). And being surrounded by them taught me something no self-help book ever has: Software updates constantly. Humans avoid updating at all costs. And that… makes no sense. 💻 In tech, upgrades are NORMAL. Expected. Celebrated. If a framework updates every 3 weeks? Cool. If a library is deprecated? Expected.
I Don’t Code, But Tech Somehow Became Home
I don’t code. Never learned. Probably never will — unless “using AI tools, begging them to understand me, and hoping for the best” suddenly becomes a programming language. But honestly? Being around tech people has taught me something unexpected: there is a special kind of joy in making things — even if I’m not the one writing the code. Somewhere along the way, this whole world — the chaos, the acronyms, the debugging frustration, the late-night “I FIXED IT!!!” energy — started to feel like home.
What’s a Tool You’ve Built Just for Yourself? (I’m Curious.)
I’m not a developer, but I work around a lot of them — enough to know that devs build things for fun, for curiosity, for frustration relief, and sometimes just because the idea wouldn’t leave their brain alone. And honestly? I think that’s one of the coolest parts of tech culture. Because while companies talk about roadmaps, features, and customer needs… developers quietly build things that solve their own problems first. Tools no one asked for. Tools no one paid for.
Why Both Startup Code and Legacy Systems Need Code Context - And How LLMs + CodeDoc Make It Possible
If you’ve ever worked with a startup codebase or a decades-old legacy system, you already know the truth: Both are confusing in totally different ways — but for an AI model, they’re equally unreadable without real context. In 2025, every company wants to use LLMs to generate documentation, refactor old systems, or speed up onboarding. But here’s the catch: 🧠 LLMs don’t magically “understand your code.” They only understand the context you give them.
DEV.to Just Quietly Dropped One of Its Best Features Ever - AI Image Generation for Articles
If you’ve published even one article online, you know the pain of choosing a cover image. Stock photos feel generic. Hand-made illustrations take forever. And “just skip the cover image” somehow makes the whole post feel incomplete. So when DEV.to quietly rolled out a new Generate Image button for article headers, I wasn’t expecting much… But after trying it? Wow. This is easily one of DEV.to’s most underrated features of 2025. Let me show you why.
How LLMs Are Learning to Understand Code, Not Just Generate It?
We’ve all seen what large language models (LLMs) can do — autocomplete half a function, write an API call, even generate an entire app from a prompt. Cool, right? But let’s be honest — that’s not the hard part. The hard part is understanding why that code exists, how it connects to the rest of the repo, and what happens if you touch it. That’s the part most “AI coding tools” still skip. And that’s where the next wave of LLMs — the ones built for understanding, not just output — start to matter.
👋 Hey devs, We’re Everdone.ai — an AI lab obsessed with doing the work humans don’t want to repeat. Documentation. Summaries. All those context-building chores that eat your time. So we built Codedoc — an AI that writes your code context for you.
Is there any software for documentation for code?
#programmerhumor #funwithcode #discorddev I’m not a coder, but I keep hearing you all leave wild little notes to yourselves inside your code. What’s the funniest, weirdest, or most random comment you’ve come across in code? Bonus points if it made no sense, involved “fix this later” or had chaotic energy 😂 Teach me your ways 👇 I need a good laugh today. We're a place where coders share, stay up-to-date and grow their careers.
Hey devs - how do you manage your code context when you switch between tasks?
Hey folks — I’m not a developer myself, but I work closely with coders and keep hearing about how tough it is to pick up where you left off in a project, especially after interruptions or task-switching. I’m curious: 📌 How do you manage your code context? 📌 What eats up the most time when you get back to a project? 📌 Are there little hacks, tools, or rituals you use to stay sane? Would love to hear your war stories, tips, or even things you wish existed to make this easier.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Urvisha
Contact Urvisha, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack