What Testing a Real App Taught Me About Building One

Divyansh Kumar — Sun, 26 Oct 2025 18:15:56 +0000

When I joined Stapubox as a Backend + QA Intern, I thought testing would be the “less exciting” part of the journey.
But I was wrong.

Within the first week, I realized testing isn’t about clicking buttons or breaking things—it’s about understanding how real users think. And that changed the way I look at building products forever.

📖 My Story

Since this was my first experience in QA, I honestly didn’t know where to start.

A senior teammate gave me a simple but powerful suggestion:

“Before you think like a developer, think like a user. Do a bit of monkey testing first.”

At first, it sounded funny. But when I started exploring the app like a curious user—signing up, creating a profile, testing chats, checking recommendations—I began noticing small details I would’ve completely ignored as a developer.

Tiny loading delays.
A misplaced button on the onboarding screen.
A chat message that didn’t update in real-time unless I refreshed.

Individually, they seemed minor. But together, they told a bigger story about user experience.

That’s when it hit me—every tiny inconsistency matters because that’s exactly what a user notices first.

By the second week, I wasn’t just finding bugs anymore.
I was understanding why they happened—and more importantly, how to prevent them while building.

💡 What I learned?

Testing taught me lessons no coding tutorial ever could:

Empathy beats logic. You can’t build something great unless you understand how it feels to use it.
Small details aren’t small. A one-second delay or an unhandled state can define how users perceive your entire product.
QA makes you a sharper developer. It forces you to think beyond “does this code work?” to “does this experience make sense?”

Now, whenever I write backend logic, I automatically imagine how a user will interact with that flow on the front end.
And that mindset shift alone has been priceless.

🤝 Over to you!

I used to think testing was the final step in development.
Now, I see it as the foundation of building something truly meaningful.

If you’re a developer—especially early in your journey—I’d love to hear this from you:
👉 How do you make sure your code feels human to the end user?

Let’s share stories, not just syntax. 👇

Stop Shipping Broken .env Files — Meet env-check-ts

Divyansh Kumar — Mon, 07 Jul 2025 05:15:02 +0000

Have you ever deployed your Node.js app, only to see it crash due to a missing or incorrect environment variable?

If yes — you’re not alone.

Environment variables (.env files) are essential for configuring secrets, ports, database URLs, and more — but they’re also fragile and invisible. A single missing or mistyped key can break your entire app in production, CI/CD, or even onboarding new teammates.

That’s exactly the kind of problem I wanted to solve when I created:

env-check-ts

A simple, TypeScript-powered CLI that validates your .env file against a schema and even auto-generates .env.example.

🤷‍♂️The Problem We Often Ignore

Let’s say you’ve got a .env like this:

NODE_ENV=prod
PORT=3000
DATABASE_URL=https://secure-db.com

What if:

NODE_ENV was expected to be "production", not "prod"?
PORT was accidentally deleted?
You forgot to include DATABASE_URL in .env.example?

These bugs don’t get caught until runtime... and by then it’s too late.

🧪The Solution — env-check-ts

env-check-ts solves this with schema validation, powered by Zod. It ensures your .env is:

✅ Present

✅ Complete

✅ Valid by type and value

You can also auto-generate a neat .env.example based on your schema.

🧑‍💻 Try it Now

npm install -g env-check-ts

or use via:

npx env-check-ts validate

Full docs + GitHub: Here

🤔Why I Built This

As a developer working on open-source and team projects, I faced recurring issues:

CI/CD failing due to missing envs
Confusion over .env files in onboarding
Forgetting to update .env.example

I wanted something:

Simple and Type-safe
And powered by a schema — not just regex

So env-check-ts was born. It’s lightweight, zero-config, and developer-first.

🔮What's Next?

I'm actively improving this tool. Upcoming features:

Support for .env.production, .env.test, etc.
Ability to redact secrets when generating .env.example
VS Code extension for inline validation
Auto-run as part of CI/CD pipelines

Have suggestions or ideas? I’d love your feedback!

🫡Final Words

If this tool helped you or your team:

⭐️ Give it a star on GitHub

🗣 Share it with a dev friend or a crazy techy

📥 DM or comment — I'd love to hear your thoughts!

Thanks for reading 🙌
Built with ❤️ by Divyansh Kumar

Forem: Divyansh Kumar