DEV Community: Dipraj Girase

The Deeper I Go Into Tech, The More I Realize How Much I Don't Know

Dipraj Girase — Sat, 13 Jun 2026 07:38:23 +0000

After four years of Computer Science engineering, a startup experience, and now working at an MNC, I thought I'd have most things figured out.

I believed that by this point, I'd feel confident about my technical knowledge and have a clear understanding of the software industry.

But the deeper I went into tech, the more I realized how much I still didn't know.

Not in a discouraging way.
Just in a humbling way.

The Reality Check

Like many Computer Science students, I spent years learning data structures, algorithms, databases, operating systems, networking, software engineering, and programming languages.

I built projects.
I fixed bugs.
I participated in hackathons.
I learned frameworks and tools.

And eventually, I got the opportunity to work in both a startup and later an MNC.

Naturally, I felt like I had a decent understanding of software development.
Then I started exploring beyond my day-to-day work.

That's when I began coming across topics like:

System Design
Cloud Architecture
Distributed Systems
Linux Internals
Cybersecurity
Cryptography
AI/ML
MLOps
Networking at Scale
Open Source Ecosystems

And what surprised me wasn't how difficult these topics were.
It was realizing how many more topics existed beyond them.
Every rabbit hole seemed to open three more.

When Imposter Syndrome Creeps In

I remember reading posts from experienced engineers discussing concepts I had never heard of before.

Large-scale architectures.
Observability.
AI infrastructure.
Performance engineering.
Security.

Sometimes I'd find myself scrolling through discussions thinking:
"Wait... people actually understand all of this?"

That's usually when imposter syndrome would show up.

Questions like:

"Am I behind?"
"Should I already know this?"
"How does everyone else seem so knowledgeable?"
started creeping into my mind.

The more I explored, the bigger the gap felt.

What Changed My Perspective

Over time, I started paying closer attention to the engineers I looked up to.

Senior engineers.
Staff engineers.
Architects.
People with years of experience.

And I noticed something interesting.

They weren't pretending to know everything.

Many of them openly talked about what they were currently learning.
Some were learning AI.
Others were diving deeper into cloud infrastructure.
Some were exploring security.
Others were trying to better understand distributed systems.

The common pattern wasn't expertise.
It was curiosity.

That's when something clicked for me.

Maybe being a good engineer isn't about knowing everything.
Maybe it's about staying curious enough to keep learning.

My "Things I Don't Know Yet" List

One habit that has helped me a lot is maintaining a simple note called:

"Things I Don't Know Yet."

Whenever I come across a topic I don't fully understand, I add it to the list.
Not because I need to learn everything immediately.
But because I don't want to forget it.

Today, that list contains things like:

Advanced System Design
Cloud Architecture at Scale
AI/ML beyond tutorials
MLOps and AI Deployment
Cybersecurity
Linux Kernel Internals
Distributed Systems
Networking
Cryptography
Open Source at Scale

Some items stay there for months.
Some get checked off.
And somehow, new ones keep getting added.

Earlier, that would've bothered me.
Now I see it differently.

The growing list isn't proof that I'm falling behind.
It's proof that I'm still discovering new things.

Why This Small Habit Helps

The biggest benefit isn't that it makes me learn faster.

It's that it reduces the pressure.
Instead of feeling overwhelmed by everything I don't know, I simply write it down.

The list becomes a roadmap instead of a reminder of my limitations.

Every few months, I revisit it.
Some topics that once looked intimidating suddenly make sense.
Some are still waiting their turn.

And new topics appear that I didn't even know existed before.
That's become one of my favorite parts of working in tech.
There's always another layer to uncover.

The Rabbit Hole Never Ends

One thing I've learned is that software engineering is much broader than it appears from the outside.

You learn web development.
Then you discover system design.
System design leads you to distributed systems.
Distributed systems lead you to networking, infrastructure, and observability.

AI introduces entirely new worlds.
And every path branches into several more.

The deeper you go, the more you realize there isn't a finish line.
And honestly, that's okay.

Because that's also what makes this field exciting.

What I Tell Myself Now

These days, whenever I encounter something unfamiliar, I try not to think:
"I should already know this."

Instead, I remind myself:
"I don't know this yet."

That one word changes everything.

It turns a knowledge gap into a future learning opportunity.
And it reminds me that growth isn't about having all the answers.
It's about being willing to find them.

Final Thoughts

If you're a student, fresher, or early-career developer feeling overwhelmed by how much there is to learn, you're not alone.

I've felt that way.
I still do sometimes.

But I've learned that the best engineers aren't the ones who know everything.

They're the ones who keep learning.

So now, whenever I discover something I don't understand, I don't see it as a weakness.

I add it to my "Things I Don't Know Yet" list.

And then I move forward.
One step at a time.
That's how engineers grow.

Express.js vs Nest.js: The Battle of Backend Frameworks

Dipraj Girase — Tue, 25 Mar 2025 12:01:42 +0000

When it comes to backend development, Node.js with Express has long been the go-to choice. It's fast, lightweight, and event-driven a solid foundation for web applications.

But then came Nest.js, built on top of Node.js and Express, with a structured, opinionated approach that brings enterprise-level organization to backend development.

So, is Nest.js just Express in a fancy outfit, or is it a game-changer? Let’s break it down.

Node.js: The Backbone

Think of Node.js as that dependable friend—always there when you need a quick server setup or a lightweight backend.

🔹 Speed & Scalability – Perfect for real-time applications.
🔹 Flexibility – Lets you build things your way.
🔹 Minimalistic – No unnecessary overhead.

But there’s a catch.

🛑 No built-in structure – You have to organize your code manually.
🛑 Callback Hell – Though async/await made life easier, deep nesting is still a challenge.
🛑 Boilerplate Code – Every major feature requires external packages and manual setup.

Pair Node.js with Express.js, and you get a powerful but unopinionated framework. It’s like a blank canvas—you decide how to structure your app. But too much freedom often leads to spaghetti code if not managed properly.

Nest.js: The Fancy Cousin with a Plan

Enter Nest.js a TypeScript-powered, decorator-heavy framework that brings order to chaos.

🔹 Built-in Structure – Organizes your backend neatly with controllers, modules, and services.
🔹 Dependency Injection (DI) – No need to manually manage dependencies.
🔹 TypeScript-First – Prevents runtime errors with strong type safety.

Sure, it feels opinionated at first, but soon you’ll realize—it’s scaffolding for scalable applications.

Why Developers Love Nest.js:

✅ Minimal Boilerplate – Features like authentication, database connections, and validation are already streamlined.
✅ Swagger Integration – Auto-generates API documentation with decorators like @ApiBearerAuth().
✅ Enterprise-Grade – Ideal for large applications requiring scalability and maintainability.

TypeScript: The Unsung Hero

Node.js lets you choose between JavaScript and TypeScript, but Nest.js fully embraces TypeScript from the start.

✔ Static Typing – Reduces bugs by catching errors at compile time.
✔ DTOs & Interfaces – Clearly defines request and response structures.
✔ Better Code Maintenance – Large teams benefit from strict typings and modular architecture.

Yes, writing TypeScript feels like doing taxes at first, but the long-term benefits outweigh the initial learning curve.

Decorators: The Sparkle That Sticks

Nest.js decorators simplify backend logic by making everything more readable and structured.

🔹@Controller() – Defines route controllers.
🔹 @Injectable() – Marks services for dependency injection.
🔹 @Module() – Organizes related components into logical modules.

It’s like using LEGO blocks—each piece fits perfectly into place.

Swagger Wars: Nest.js vs. Express.js

One of Nest.js’s biggest wins? Effortless Swagger integration.

✔ Nest.js: Just add a few decorators, and Swagger automatically documents your API.
❌ Express.js: Swagger setup is manual—you’ll often need to define schemas yourself.

LiveAPI: Swagger for the Rest of Us
But what if you're using plain Node.js or Express and want easy API documentation without manual setup?

Introducing LiveAPI—a tool that auto-generates API docs in minutes, even for raw Node.js projects.

How it works:

1️⃣ Select your repository.
2️⃣ Wait 2–3 minutes.
3️⃣ Get fully structured API documentation—zero manual effort.

Conclusion:

Which One Should You Choose?
🔹 Choose Node.js (Express.js) if you want flexibility and control, but don’t mind handling structure and boilerplate yourself.
🔹 Choose Nest.js if you prefer a structured, scalable, and maintainable backend with built-in best practices.

Either way, npm install sanity before diving in. 😉

So, what’s your pick-classic Node.js or the well-dressed Nest.js?

Essential Websites to Boost Development Skills

Dipraj Girase — Sun, 23 Mar 2025 19:03:23 +0000

The difference between a good developer and a great developer isn’t just skill—it’s knowing where to find the right tools.

In 2025, staying ahead means leveraging powerful, time-saving, and AI-enhanced resources. Here are 12 essential websites that will streamline your workflow, boost creativity, and optimize your development process.

🛠️ Coding & Debugging

1. CodePen

A must-have for front-end developers, offering a live playground for HTML, CSS, and JavaScript to test, build, and showcase code snippets.

2. DevDocs

A blazing-fast, offline-friendly documentation hub covering all major programming languages in one place.

3. Can I Use

Ensure your CSS and JavaScript features work seamlessly across browsers before implementation.

🎨 UI/UX & Design Inspiration

4. LottieFiles

Enhance user experience with lightweight, high-quality Lottie animations for web and mobile apps.

5. SVG Repo

Access thousands of free SVG icons and illustrations to bring life to your projects.

6. Realtime Colors

Instantly create accessible, aesthetically pleasing color palettes with real-time previews.

📦 Productivity & DevOps

7. Readme.so

A simple yet powerful README generator that saves time and ensures a professional touch.

8. Public APIs

A goldmine of free APIs for various domains—weather, finance, memes, and more.

🚀 AI & Future Tools

9. Windsurf

An AI-driven UI/UX assistant that helps developers generate, tweak, and optimize designs effortlessly.

10. Agent AI

A smart AI-powered coding assistant that automates tasks, speeds up debugging, and enhances productivity.

11. Octomind

An AI-powered code reviewer that spots bugs, suggests optimizations, and refines your code.

12. Cursor AI

An AI-enhanced VS Code extension that accelerates coding, auto-completes intelligently, and improves debugging.

🎯 Final Thoughts

Great developers don’t just write better code—they use better tools. These 12 resources will boost your productivity, enhance creativity, and help you stay ahead in 2025.

💡 Which tools do you swear by? Drop them in the comments!

🔥 If this list helped you, hit the 💖 and share it with your fellow developers!

Optimize Your CSS and Improve Performance with PurgeCSS

Dipraj Girase — Sat, 01 Mar 2025 07:26:30 +0000

When building web applications, we often rely on our go-to CSS frameworks like Bootstrap or TailwindCSS. These frameworks are packed with useful utilities that help speed up our development process and normalize our UI across browsers. However, they also come with a lot of bloat — a significant portion of the framework's CSS often goes unused in most projects.

Even if you build and maintain your own Design System from scratch, you’ll still end up with unused CSS across different projects. This is where PurgeCSS becomes incredibly useful.

What is PurgeCSS?
PurgeCSS is a powerful tool that helps remove unused CSS, leaving you with a leaner, faster stylesheet that only contains the styles your project actually uses. In my personal projects, after integrating PurgeCSS, I’ve seen CSS file size reductions of 70% to 90%, along with noticeable performance improvements in render times.

Compatibility & Usage
PurgeCSS works well with most modern JavaScript bundlers and web build tools. It also offers a CLI tool for direct use. Personally, my favorite setup is using PurgeCSS with TailwindCSS in Next.js projects, where the integration is seamless.

Example & Guide
If you're looking for a practical example, here’s a helpful guide along with a GitHub repository I created when I was experimenting with PurgeCSS and TailwindCSS. It walks through my setup and shows how easy it is to get started.

👉 Check out PrugeCSS for more details.

Recommended Reading
I also recently came across an excellent article on freeCodeCamp titled "How I dropped 250KB of dead CSS weight with PurgeCSS" It offers some great insights into real-world improvements you can achieve with PurgeCSS — highly recommended!

Final Thoughts
Whether you’re working on small projects or large-scale applications, optimizing your CSS footprint is critical for performance. Tools like PurgeCSS make this process simple and highly effective.

Have you used PurgeCSS in your projects? I’d love to hear about your experience!

[Boost]

Dipraj Girase — Wed, 12 Feb 2025 03:48:52 +0000