Super Simple Dev Tricks (That Actually Work) + 2 Myths I’m Done Believing

There’s no shortage of advanced dev tools, frameworks, or “next big things” flying around in our industry. But over time, I’ve realized that some of the most valuable tools in my daily workflow are surprisingly simple—and often overlooked.

As developers, we’re constantly pushed to learn more, do more, and stay ahead. But sometimes, it’s the small, repeatable habits and the ability to ignore bad advice that make the biggest impact on productivity and sanity.

In this post, I want to share a few simple tricks that have made my day-to-day work smoother, and clear up a few myths I’ve stopped buying into along the way.

✅ Stupid Simple Dev Tricks I Actually Use

Use npx to Avoid Installing Global Packages You’ll Never Use Twice

If you’re like me, your global package list used to be filled with random CLIs you installed once and forgot about.

Instead of cluttering your system:

npx create-react-app my-app

npx serve

npx kill-port 3000

No global install. No cleanup. Just get things done.

Git Aliases = Sanity

If you work with Git daily, typing out the same verbose commands is just unnecessary friction.

Here’s a few I actually use:

alias gco="git checkout"

alias gst="git status"

alias gcam="git commit -am"

alias gpo="git push origin"

Multi-Cursor Editing in VS Code Is a Game-Changer

This one’s simple but powerful. Instead of editing one line at a time:

• On Mac: Option + Click

• On Windows: Alt + Click

You can edit multiple lines at once, rename variables across sections, or drop the same line of code in several places. It’s a small thing that adds up fast.

npx serve for Quick Testing

Whether I’m testing a basic HTML/CSS file or sharing a static project locally, I use: npx serve

No full server setup. No configuration. Just preview and go. Perfect for side projects, components, or quick UI tests.

Use Comments to Leave Notes for “Future You”

I used to think code should be self-explanatory. Now I know better—especially when returning to old projects. A short, honest comment can save future-you a lot of pain.

// This conditional looks weird, but it's needed for legacy behavior

// Don’t delete this unless you also update X module

Comments aren’t a weakness—they’re a courtesy to your future self and your team.

❌ 2 Dev Myths I’m Done Believing

Myth 1: “You Need to Learn Everything to Be a Real Developer”

I used to chase every new library, tool, or trend—afraid I’d fall behind. The truth? You don’t need to learn everything—you need to learn what helps you solve real problems.

Focus on what’s useful in your projects. Depth beats breadth over time.

Myth 2: “Frameworks Are More Important Than Fundamentals”

Frameworks change. Core concepts don’t. If you understand how the web works—how browsers render, how JavaScript handles async, how CSS layout behaves—you’ll be adaptable across any stack.

Invest in fundamentals first. Frameworks will come and go.

Staying sharp as a developer doesn’t always mean chasing complexity. Sometimes, the best upgrades come from simplifying what you already do, refining your habits, and tuning out the noise.

If you’ve got a favorite trick that makes your workflow easier—or a myth you’ve stopped believing—I’d love to hear it.

Let’s keep it simple, useful, and real.