Forem: Kelvin Nimely

[Boost]

Kelvin Nimely — Tue, 09 Dec 2025 22:48:11 +0000

Boost Your Next.js Workflow: Understanding npm run lint vs npm run build

Kelvin Nimely ・ Dec 9

Boost Your Next.js Workflow: Understanding npm run lint vs npm run build

Kelvin Nimely — Tue, 09 Dec 2025 22:46:11 +0000

Hey, Kelvin here! Let's Dive into npm run build vs npm run lint in Next.js

As a developer, I've often found that understanding the nuances of your tools can make a world of difference. Today, let’s chat about two essential commands in the Next.js ecosystem: npm run lint and npm run build.

npm run lint: The Code Quality Guardian

Think of npm run lint as your code’s best friend, ensuring everything is tidy and error-free. It helps catch those pesky stylistic issues and potential bugs before they become headaches. It’s all about maintaining consistency and quality in your codebase.

npm run build: The Production-Ready Power-Up

Meanwhile, npm run build is like the dress rehearsal for your app. It compiles your code, checks for type errors (especially crucial if you’re using TypeScript), and optimizes everything for a smooth production environment. This ensures that your app performs at its best when it reaches your users.

Bringing It All Together

By running both commands, you’re not just preventing bugs; you’re building a robust, maintainable, and high-performance application. It’s all part of the journey to creating top-notch software.

As always, I’d love to hear about your experiences and any tips you might have. Feel free to drop a comment or reach out—let’s keep the conversation going!

Happy coding, and until next time, keep building awesome things!

— Kelvin

Why Developers Should Stop Fighting AI and Start Using It

Kelvin Nimely — Wed, 03 Dec 2025 18:31:25 +0000

AI is reshaping software development in real time, and the shift is bigger than most people admit. Companies like AWS, Google, Meta, and Microsoft are adopting AI coding agents to accelerate development cycles. These tools aren’t gimmicks. They’re now part of the engineering workflow.

Despite this, a portion of the developer community still pushes back against AI. Not with technical arguments, but with emotion, fear, and misconceptions. And strangely, many of the strongest opinions come from developers who have never used a real agentic coding system,only simple “autocomplete-style” tools.

But here’s the reality: if AI can help ship a product in two months instead of five, it’s not unreasonable to use it. It's not cheating. It’s evolution.

The truth is that innovation has never paused for anyone’s comfort. If the invention of email depended on emotional reactions, we would still be writing letters today. If social platforms were judged through fear alone, Facebook might not exist. Progress happens because someone ignores resistance and keeps moving.

AI follows that exact pattern.

For beginners, slowing down to learn properly is okay. Foundations matter. But for experienced developers, freelancers, and builders who are racing against time, clients, and competition, rejecting AI is almost self-sabotage. You don’t earn extra respect for working slower.

AI won’t replace real developers. But real developers who use AI will outperform those who don’t.

The wave is here. It’s rising.
You can resist it emotionally, or you can ride it technically.

History shows that only one of those choices keeps you relevant.