DEV Community: Hridoy

Consistency beats talent in coding

Hridoy — Sun, 15 Nov 2026 16:37:05 +0000

When I started, I thought great developers were just born smarter. After years of building with Flutter, React.js, and Node.js, I believe something different: consistency matters more than talent.

Coding is a skill, and skills grow with regular practice. One hour a day for a year will take you much further than a 12-hour binge once a month.

What consistency looks like:

Small daily practice: Even 30-60 minutes counts. Show up on the days you don’t feel like it.
Building, not just watching: Try to write some code every day, even a small feature or a bug fix.
Tracking progress: Keep a GitHub streak, a notes file, or a simple checklist so you can see how far you’ve come.
Learning one thing at a time: Finish one topic before jumping to the next shiny tool.
Accepting slow days: Some days you’ll understand little. That’s part of the process, so don’t quit.

Why it works:
Concepts that confuse you today become obvious in a few weeks. Small wins stack up, and then one day you notice you can build things you couldn’t before.

You don’t need to be the smartest in the room. You just need to keep showing up.

What’s your daily coding habit? Share it below, it might help someone else stay on track.

Coding #Consistency #LearnToCode #Programming #DeveloperJourney

Want to build a browser extension? If you know JavaScript, you’re already most of the way there.

Hridoy — Sun, 15 Nov 2026 16:34:31 +0000

Browser extensions are one of the most underrated things a web developer can build. They’re small, useful, and you can ship one fast. Here’s what helped me understand them.

What an extension is made of:

manifest.json: The config file. It defines the name, version, permissions, and which scripts run where (use Manifest V3 for new projects)
Content scripts: JavaScript that runs inside web pages, so you can read or change the page
Background service worker: Handles events and long-running logic behind the scenes
Popup / options page: The UI users see. It’s just HTML, CSS, and JS, and you can build it with React
Storage and messaging APIs: Save user settings and let the different parts talk to each other

Tips for getting started:

Start with a tiny idea, like a button that changes a page’s style or saves a note
Ask only for the permissions you really need. Users and store reviewers care about this
Load your extension unpacked in developer mode to test changes quickly
Use a bundler like Vite if you want React or TypeScript in your popup
Chrome, Edge, and Firefox share most of the WebExtensions API, so one codebase can often cover several browsers

Common mistakes:

Requesting broad permissions “just in case”
Forgetting that service workers in Manifest V3 can shut down, so don’t keep state only in memory
Skipping a clear privacy explanation before publishing

The best part is that you can solve a real problem you have every day, and publish it for others to use.

Have you built a browser extension, or do you have an idea for one?

BrowserExtensions #JavaScript #WebDevelopment #Chrome #React

How I use AI tools in my coding workflow (and where I don’t)

Hridoy — Sun, 15 Nov 2026 16:31:44 +0000

As a full stack developer working with Flutter, React.js, and Node.js, AI tools have become part of my daily routine. Here’s how I use them without losing control of my code.

Where AI helps me most:

Explaining unfamiliar code: Paste in a confusing function or error and get a plain-language breakdown
Boilerplate: Models, API routes, form layouts, and repetitive widgets
Debugging: Describing a bug and getting a few possible causes to check
Learning: Asking “why” and “what are the trade-offs” when picking up a new tool
Drafting: Documentation, commit messages, and README files

Where I stay careful:

Never merge code I don’t understand. If I can’t explain it, it doesn’t go in.
Security and data: I review auth, database queries, and anything touching user data myself
Don’t paste secrets: API keys, tokens, and client data stay out of prompts
Verify everything: AI can sound confident and still be wrong, so I test and read the docs

My simple rule:
AI is a fast, tireless junior pair-programmer. It speeds me up, but I make the decisions and I own the result.

Used well, these tools don’t replace developer skills. They reward them, because the better you understand the fundamentals, the better you can judge what AI gives you.

How are you using AI in your workflow? Any tips or mistakes to share?

AI #SoftwareDevelopment #Programming #Productivity #FullStack

MongoDB vs PostgreSQL: how I choose between them

Hridoy — Sun, 15 Nov 2026 16:30:21 +0000

I use both in my projects, so people often ask me which one is better. My answer is that it depends on the shape of your data.

I reach for PostgreSQL when:

Data is highly relational (users, orders, payments, invoices)
I need strict consistency and transactions
I want complex queries with joins and aggregations
The schema is fairly stable and I want the database to enforce it

I reach for MongoDB when:

Data is flexible or changes shape often (content, logs, product catalogs)
I’m prototyping and want to move fast without migrations
Documents are naturally nested and read together
I’m working with Node.js and want JSON-like data end to end

Common mistakes I see:

Choosing MongoDB because it feels easier, then fighting relationships later
Choosing PostgreSQL for everything without thinking about whether the data really needs that structure
Picking based on hype instead of how the data will be queried

Neither one is “better.” The right choice comes from your data and your queries, not from trends. And sometimes using both in one project is perfectly fine.

Which one do you use most, and why?

MongoDB #PostgreSQL #Database #BackendDevelopment #FullStack

7 tips I’d give to beginner developers

Hridoy — Sun, 15 Nov 2026 16:28:05 +0000

7 tips I’d give to beginner developers

I’m a full stack developer working with Flutter, React.js, Node.js, MongoDB, and PostgreSQL. Here’s what I wish I’d known when I started:

Build projects, don’t just watch tutorials.
Tutorials feel productive, but you only learn when you get stuck and fix things yourself. Pick a small idea and build it.
Learn the fundamentals first.
Frameworks change fast. JavaScript, Dart, HTTP, databases, and Git stay useful for years.
Read error messages.
Most of the answer is usually in the error. Read it slowly before you search or ask for help.
Learn Git early.
Commit often, write clear messages, and push your work to GitHub. It becomes your portfolio too.
Don’t chase every new tool.
Pick one stack, get good at it, and then expand. Depth beats a long list of half-learned technologies.
Use AI as a helper, not a replacement.
AI tools are great for explaining code and speeding up work, but make sure you understand what they write. If you can’t explain it, you don’t own it.
Be patient with yourself.
Everyone feels lost sometimes. Getting stuck is not a sign you’re bad at this. It’s how the learning happens.

Keep building, keep shipping, and keep learning a little every day.

What’s the best tip you would give to someone just starting out?

BeginnerDevelopers #WebDevelopment #Programming #CodingTips

Why I keep choosing Flutter for mobile apps

Hridoy — Sun, 15 Nov 2026 15:52:15 +0000

One codebase, two platforms (Android and iOS), and the app still feels native. That’s the main reason Flutter is my go-to for mobile.

What I like most after building with it:

Hot reload: I see changes in under a second, so I can experiment freely.
Everything is a widget: Once you get the idea, building UI feels consistent and predictable.
Fast delivery: Shipping to both platforms from one codebase saves a lot of time for clients and small teams.
Great pairing with a Node.js backend: I use Flutter for the app and Node.js with MongoDB or PostgreSQL behind it, so I can handle the whole stack myself.

It’s not perfect. App size can be larger, and state management has a learning curve (Provider, Riverpod, and Bloc all have their fans). But for most products, the trade-off is worth it.

If you’re starting a mobile project and want to move fast, Flutter deserves a look.

What’s your experience with Flutter? Which state management do you prefer?

Flutter #Dart #MobileDevelopment #FullStack

AI a bubble?

Hridoy — Sun, 15 Nov 2026 15:33:58 +0000

Is AI a bubble? I think it’s both a bubble and a real shift.

Every few weeks someone asks me if AI is a bubble. My honest answer is that parts of it probably are.

Valuations are high, and many startups are really thin wrappers around someone else’s model. Plenty of companies say “AI-powered” without being able to show what it improved.

But the technology itself is not hype. As a developer, I use AI tools every week, and they save me real time on debugging, drafting, and learning new things.

The dot-com bubble burst, yet the internet still changed everything. The companies built on solid value survived. The ones built on buzzwords didn’t.

So my approach:

Don’t chase the label, solve a real problem
Learn to use the tools well
Be skeptical of any product that can’t say what it actually improves

Bubble or not, skills and real value will outlast the noise.

What do you think: bubble, breakthrough, or both?

DEV Community: Hridoy

Consistency beats talent in coding

Coding #Consistency #LearnToCode #Programming #DeveloperJourney

Want to build a browser extension? If you know JavaScript, you’re already most of the way there.

BrowserExtensions #JavaScript #WebDevelopment #Chrome #React

How I use AI tools in my coding workflow (and where I don’t)

AI #SoftwareDevelopment #Programming #Productivity #FullStack

MongoDB vs PostgreSQL: how I choose between them

MongoDB #PostgreSQL #Database #BackendDevelopment #FullStack

7 tips I’d give to beginner developers

BeginnerDevelopers #WebDevelopment #Programming #CodingTips

Why I keep choosing Flutter for mobile apps

Flutter #Dart #MobileDevelopment #FullStack

AI a bubble?

AI #Technology #Software