DEV Community: Hanzla Baig

The Coding Interview Is Dead. What Should Replace It?

Hanzla Baig — Mon, 11 May 2026 09:48:17 +0000

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

Unpopular opinion: The technical interview, as most companies practice it today, is not a test of engineering ability. It's a test of how well you studied for the test.

Let's stop pretending otherwise.
https://videotik.netlify.app/

What's Actually Broken

The standard coding interview loop goes something like this: a stranger gives you a graph traversal problem you haven't thought about since college, you're expected to solve it optimally while talking out loud, on a whiteboard or shared editor, with a clock ticking and your future employment hanging in the balance.

That's not an engineering challenge. That's a game show.

The Memorization Trap

https://videotik.netlify.app/
LeetCode has become an industry unto itself — premium subscriptions, "blind 75" cheat sheets, YouTube channels dedicated entirely to pattern-grinding. Engineers spend hundreds of hours memorizing solutions to problems they will never encounter on the job.

And if you haven't done the prep recently? Doesn't matter how many production systems you've shipped. You're going home.

The signal being measured isn't engineering skill. It's proximity to studying.

Unrealistic by Design

When was the last time you:

Implemented a red-black tree from scratch at work?
Reversed a linked list under a 20-minute time constraint?
Solved a dynamic programming problem without Stack Overflow?

If your answer is "never" — congratulations, you're a normal software engineer.
https://videotik.netlify.app/
Real engineering involves reading documentation, searching for prior art, asking teammates, iterating on messy problems over days — not weeks. The whiteboard strips all of that away and replaces it with a performance ritual.

Stress as a Feature (Not a Bug)

vhttps://videotik.netlify.app/Proponents of high-pressure interviews often argue: "We want to see how you perform under pressure."

Sure. But the pressure of debugging a production incident at 2 AM is fundamentally different from the pressure of inverting a binary tree in front of a stranger who's silently judging your variable names.

One is real. The other is theater.

The Randomness Problem

Ask any engineer who's gone through multiple rounds of technical hiring and they'll tell you: it's inconsistent. The same candidate can ace one company's loop and bomb another's — not because their skills changed, but because the problems and interviewers did.

That's not a signal. That's noise masquerading as rigor.

The Industry Reality

Here's what a senior engineer's actual day looks like:

Reading a PR and leaving thoughtful comments
Debugging a service that's behaving weirdly in prod
Scoping a feature with incomplete requirements
Refactoring code someone wrote three years ago with no docs
Writing a design doc, getting it torn apart, revising it

Notice what's not on that list? Implementing Dijkstra's algorithm from memory.

The gap between what interviews test and what engineers actually do isn't a crack. It's a canyon.

Who It Hurts Most

Junior Developers

For juniors, the LeetCode gauntlet is brutal. They haven't had years to accumulate systems intuition, so they're reduced entirely to algorithmic prep. A junior who spent six months building a real, deployed product gets filtered out by a junior who spent six months grinding hard problems. That's not meritocracy — it's a different kind of memorization test.

Self-Taught Engineers

Bootcamp grads and self-taught devs often have strong practical skills — they've shipped things, debugged real issues, learned by doing. But they're disproportionately disadvantaged by a system that rewards CS fundamentals trivia. The interview loop quietly (sometimes not so quietly) filters for pedigree.

Experienced Engineers

Ironically, senior engineers can fail these interviews too. They've spent years building expertise in solving actual problems — which means they haven't been rehearsing interview patterns. A Staff Engineer with a decade of distributed systems experience might blank on the "correct" way to implement a trie. The interview doesn't care about the distributed systems.

What Should Replace It

Good news: there are better ways. Companies that have ditched the standard loop report better hires, more diverse teams, and candidates who actually want to work there.

Take-Home Projects (Done Right)

Assign a small, realistic problem relevant to the role. A backend candidate might build a simple REST API. A frontend engineer might implement a UI component with defined behavior.

The rules:

Keep it scoped to 3–4 hours max — not a week-long unpaid sprint
Review the code in a follow-up conversation, not just the output
Make it open-ended enough to reveal how people think, not just whether they got the right answer

### Pair Programming Sessions

Give the candidate a real (or realistic) codebase and work through a problem together. Watch how they read unfamiliar code. See how they ask questions. Notice if they communicate tradeoffs.

This mirrors actual work far more accurately than a whiteboard ever could.

Code Review Discussions

Hand them a PR with intentional flaws — maybe a subtle bug, maybe a design smell, maybe just some style inconsistency. Ask them to review it as if they were the assigned reviewer.

This tests: communication, technical judgment, attention to detail, and professional tone. All things that actually matter.

Real-World Debugging

Share a failing test or a broken endpoint. Give them the repo, the error message, and time. Watch how they navigate the unknown.

Because navigating the unknown is the job.

Portfolio-Based Hiring

For candidates with a body of work — open source contributions, personal projects, professional work they can discuss — let the work speak. A structured conversation about something they built tells you more than a contrived algorithm ever will.

What Good Interviews Actually Look Like

Here's a framework worth stealing:

✓ Is it realistic?
Does it resemble something they'd actually do in the role?
https://videotik.netlify.app/
✓ Is the environment fair?
Do they have access to documentation, a real editor, the internet?
https://videotik.netlify.app/
✓ Are you evaluating thinking or trivia?
Can you see how they approach problems, not just whether they solve them?\
https://videotik.netlify.app/

✓ Is there a conversation?
The best interviews are collaborative, not interrogative.

✓ Is it consistent across candidates?
Same problem, same rubric, same environment — or your comparison is meaningless.

✓ Is it respectful of their time?
Take-homes over 4–5 hours without compensation are not acceptable. Full stop.

https://videotik.netlify.app/

The Closing Argument

The industry built the coding interview for a world where CS graduates were scarce, software was narrow, and "can they code" was a reasonable binary question to answer. That world no longer exists.

Software engineering in 2026 is collaborative, contextual, and deeply dependent on communication, judgment, and adaptability. None of those things show up in a LeetCode hard problem.
https://videotik.netlify.app/
The companies that figure this out will hire better engineers, retain them longer, and build better products. The ones that don't will keep https://videotik.netlify.app/optimizing for candidates who are good at being interviewed — which is a very specific, mostly useless skill.

The question isn't whether the coding interview is broken. It obviously is.
https://videotik.netlify.app/
The question is whether your company has the intellectual honesty to admit it, and the operational will to do something different.
https://videotik.netlify.app/
Most won't. But some will. And they'll have a quiet advantage that their competitors won't fully understand for a while.

https://videotik.netlify.app/

https://videotik.netlify.app/
Written by someone who has been on both sides of this process more times than they'd like to admit.

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

Vibe Coding: Are We Building Faster or Just Building Bigger Messes?

Hanzla Baig — Sun, 10 May 2026 03:09:20 +0000

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

92% of developers use AI coding tools daily. 46% of all new code is AI-generated. Trust in that code has dropped from 77% to 60% in under a year. The speed is real. So is the chaos.

Where It All Started

On February 2, 2025, Andrej Karpathy — co-founder of OpenAI, former AI lead at Tesla — posted six words that cracked the software industry wide open:

"Fully give in to the vibes."

He described a new way of building software. Describe what you want in plain English. Let the AI write the code. Check if it works. Move on. He called it vibe coding — and specifically noted it was best for "throwaway weekend projects."

Within weeks the phrase exploded across every developer community on the internet. Merriam-Webster added it as a trending expression. By December 2025, Collins Dictionary named it their Word of the Year. MIT Technology Review listed it as a 2026 Breakthrough Technology under the name "generative coding."
https://videotik.netlify.app/
And here we are in 2026 — with half the world's new code being written by AI, and the other half of the developer community arguing about whether that is brilliant or terrifying.

This blog lays out both sides, honestly, with real data — not hype, not panic.

https://videotik.netlify.app/

The Numbers Are Wild (In Both Directions)

Before taking any position, look at what the data actually shows — because it points in two completely different directions at once.
https://videotik.netlify.app/
The adoption numbers:

92% of US developers use AI coding tools daily
82% of developers globally use them weekly
GitHub reports 46% of all new code is now AI-generated
25% of Y Combinator's Winter 2025 startups had codebases that were 95% AI-generated
Google says roughly a quarter of their new code is AI-assisted
Gartner estimates that by 2028, 40% of enterprise software will be assembled using vibe coding techniques https://videotik.netlify.app/ The quality and trust numbers:
Developer trust in AI-generated code has dropped from 77% to 60% in under a year
A CodeRabbit analysis of 470 open-source GitHub pull requests found AI-co-authored code had 1.7x more major issues than human-written code
Security vulnerabilities in AI code were 2.74x higher than human-written equivalents
45% of AI-generated code contains security flaws, according to Veracode testing across 80+ coding tasks
GitClear's analysis of 153 million lines of code found code churn is projected to double in 2025, copy-pasted code up 48%, and meaningful refactoring down 60% https://videotik.netlify.app/ Two completely different pictures from the same phenomenon. Both true. Both happening simultaneously. https://videotik.netlify.app/ ---

The Productivity Paradox Nobody Wants To Talk About

Here is the number that should make every developer pause.
https://videotik.netlify.app/
In mid-2025, METR (Model Evaluation & Threat Research) ran a rigorous, randomized controlled trial. They recruited 16 experienced open-source developers from major repositories — projects averaging 22,000+ GitHub stars. They assigned 246 real-world tasks from these developers' own codebases.
https://videotik.netlify.app/
The result? Developers using AI tools completed their tasks 19% slower than those working without AI.

That alone is surprising. What makes it genuinely fascinating is what came next.
https://videotik.netlify.app/
Before the study, these same developers predicted AI would make them 24% faster. After experiencing the measurable slowdown, they still believed the AI had made them 20% faster.

That is a 39-point gap between perception and reality. The subjective feeling of productivity was completely disconnected from the measured outcome.
https://videotik.netlify.app/
Why does this happen? METR identified the core reasons:

Time spent crafting prompts and waiting for AI responses added up faster than expected
AI tools struggle significantly in large, complex, existing codebases — which is what most professional developers actually work in
Reviewing, fact-checking, and refactoring AI output eats into the time saved on generation
Only 39% of AI code generations were accepted as-is — the rest required rework https://videotik.netlify.app/ The key nuance here: this slowdown was most pronounced for experienced developers on complex, existing codebases. For junior developers on greenfield projects and prototypes, the equation looks different. The AI can genuinely accelerate people who do not yet have a large pattern library in their heads. https://videotik.netlify.app/ But the headline claim — that vibe coding universally makes everyone faster — is not supported by controlled research.

https://videotik.netlify.app/

The Vibe Coding Hangover

https://videotik.netlify.app/
Fast Company named it in September 2025. Developers felt it long before anyone put a name to it.
https://videotik.netlify.app/
You have seen the scenario. A startup builds a full product in a weekend using Cursor. It works. Everyone is thrilled. They post about it on Twitter/X. Gets hundreds of likes. Then three months later — nobody on the team can explain how half of it works. Something breaks. The AI generates a fix. The fix breaks something else. The AI fixes that too. The codebase becomes a layered stack of AI patches on AI patches, with zero documentation and no human who understands the full picture.

This is the vibe coding hangover. And in 2026, engineering teams everywhere are cleaning it up.
https://videotik.netlify.app/
A real and widely shared case: an indie developer built a SaaS product entirely through vibe coding, proudly posting that it was "zero hand-written code." Within weeks the problems arrived — API keys getting maxed out, users bypassing subscriptions, random data appearing in the database. The developer had no idea how to debug any of it because they had never read the code. The app was eventually shut down permanently.

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

The structural problem is straightforward: AI generates code that works on the happy path. It is excellent at producing code that passes a demo. It is significantly weaker at handling edge cases, failure modes, unusual inputs, and production-scale stress — the exact conditions real users create.
https://videotik.netlify.app/
Research confirms this at scale. Vibe-coded projects accumulate technical debt roughly three times faster than traditionally written ones — not because the code looks wrong initially, but because it lacks documentation, test coverage, and the architectural coherence that comes from a human who actually thought through the system design.
https://videotik.netlify.app/
Industry analysts project $1.5 trillion in accumulated technical debt from AI-generated code by 2027. That number is not hypothetical. It is the forward projection of what is already visible in production codebases today.

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

As developer Steve Krouse put it bluntly:
https://videotik.netlify.app/

"When you vibe code, you are incurring tech debt as fast as the LLM can spit it out. If you don't understand the code, your only recourse is to ask AI to fix it — which is like paying off credit card debt with another credit card."

https://videotik.netlify.app/

The Security Problem Is Not Theoretical Anymore

Of all the concerns around vibe coding, security is the one that moved from "potential risk" to "documented crisis" the fastest.
https://videotik.netlify.app/
The core statistics:

45% of AI-generated code contains security vulnerabilities (Veracode, 2025)
86% of AI-generated code failed to defend against cross-site scripting
88% was vulnerable to log injection
These are not edge-case flaws — these are OWASP Top 10 staples
AI-assisted commits expose hardcoded secrets at more than twice the rate of human-only commits (3.2% vs 1.5%)
In 2025, 28.65 million new hardcoded secrets appeared in public GitHub commits — a 34% year-over-year increase, the largest single-year jump ever recorded

A large-scale scan of 5,600 publicly deployed vibe-coded applications found 2,000 highly critical vulnerabilities, 400 exposed secrets including API keys and access tokens, and 175 instances of exposed PII including medical records and payment data.

Then there is slopsquatting — one of the most underreported attack vectors of 2025. AI models hallucinate package names roughly 20% of the time, and 43% of those hallucinated names repeat consistently across sessions. Attackers now monitor these patterns, register the hallucinated names on npm and PyPI before developers can, and load them with malicious install hooks. The attack requires no phishing, no credential theft — just a developer who clicked "Accept All" without reading the import statements.
https://videotik.netlify.app/
Linus Torvalds, creator of Linux, offered the most grounded take on this. In January 2026 he used vibe coding for a Python visualizer in a hobby project — but explicitly hand-coded the C components himself, and later said at the Open Source Summit that vibe coding was fine for getting started but a "horrible idea" for maintenance.

That is a remarkably healthy way to think about it. Even the creator of the Linux kernel uses the tool — but only where it belongs.

https://videotik.netlify.app/

What It Is Doing To Junior Developers

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

This is the conversation the industry is having quietly but not publicly enough.
https://videotik.netlify.app/
A 2025 LeadDev survey found that 54% of engineering leaders plan to hire fewer junior developers due to AI efficiencies. On the surface, that sounds like AI doing the junior work. Look closer and the picture is more complicated.
https://videotik.netlify.app/
The skills a junior developer builds in their first three years — debugging gnarly issues, reading other people's code, making mistakes and learning from them, understanding why a system works the way it does — are exactly the skills that make senior developers effective at using AI tools. Seniors can spot when the AI is wrong because they have spent years seeing what "wrong" looks like in code.
https://videotik.netlify.app/
When that learning period is replaced by "generate and accept," the fundamentals do not get built. 44% of engineering leaders now observe declining fundamental programming skills among junior developers. Over 40% of junior developers admit to deploying AI-generated code they do not fully understand.
https://videotik.netlify.app/
The downstream problem: the engineers needed in 2028 and 2030 — the ones with 4-6 years of real debugging experience — will not exist if organizations stop hiring juniors today. The AI-generated technical debt accumulating now will require deep human expertise to fix later, and that expertise will not have been grown.
https://videotik.netlify.app/
The loop is: skip junior hiring → no one develops deep skills → no one can fix the mess the AI made → hire more AI → bigger mess.

---https://videotik.netlify.app/

Where Vibe Coding Is Genuinely Excellent

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

To be fair — and fairness matters here — there are categories where vibe coding is not just acceptable but genuinely transformative.
https://videotik.netlify.app/
Prototyping and validation is the clearest win. Getting a working proof of concept in front of users or stakeholders in hours instead of days is a real competitive advantage. When the goal is "does this idea work?" rather than "is this production-ready?", speed is the right priority. For this use case, vibe coding is close to magic.

Democratizing software creation is real. A 2026 Retool report found that 35% of enterprise teams have already replaced at least one SaaS product with a custom-built internal tool — and 78% expect to build more. Blinkist publicly reported replacing ~$60,000/year in SaaS spending by building lightweight internal tools with AI platforms in days. When a non-technical team member can build the workflow tool they actually need instead of bending their process to a vendor's template, that is a genuine win.
https://videotik.netlify.app/
Boilerplate and repetitive patterns are where AI genuinely speeds up experienced developers. Setting up a REST endpoint, writing database migrations, generating test cases for well-defined functions, formatting data between schemas — these are pattern-matching exercises that AI handles extremely well. Offloading this work frees cognitive energy for harder problems.

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

Documentation and code explanation is underrated. AI is excellent at explaining what a piece of code does, generating docstrings for existing functions, and writing README content. These are tasks experienced developers often deprioritize under time pressure. AI makes skipping them less necessary.

https://videotik.netlify.app/

The Right Way To Think About It

Vibe coding is not a binary choice between "use it for everything" or "avoid it entirely." It sits on a spectrum, and the right level depends entirely on the task at hand.
https://videotik.netlify.app/
High vibe (generate and accept, light review):
Prototypes, internal tools, throwaway scripts, proof-of-concept demos. Speed is the priority, consequences of failure are low.
https://videotik.netlify.app/
Medium vibe (generate, review architecture and tests):
Standard features in established codebases, repetitive CRUD operations, test scaffolding. The developer understands the context and reviews the output against it.
https://videotik.netlify.app/
Low vibe (generate a draft, rewrite carefully):
Core business logic, payment flows, authentication systems, performance-sensitive algorithms. The AI provides a starting point; the human owns the final result.
https://videotik.netlify.app/
No vibe (write manually):
Security-critical paths, architectural decisions that shape the entire system, anything where understanding the code is inseparable from being accountable for it.
https://videotik.netlify.app/
The developers thriving in 2026 are not the ones who generate the most code the fastest. They are the ones who have developed judgment — the ability to look at a task and immediately know which level of the spectrum it belongs on.
https://videotik.netlify.app/
That judgment is built from experience, from reading code carefully, from debugging things that did not work, from understanding systems at a level that goes beyond "it runs on my machine." The AI cannot give you that. Only time and deliberate practice can.

https://videotik.netlify.app/

The Bottom Line

https://videotik.netlify.app/
Vibe coding won the adoption war in 2025. The quality war is just getting started in 2026.
https://videotik.netlify.app/
The speed is real. The productivity gains for the right tasks are real. The democratization of software creation is real and meaningful.
https://videotik.netlify.app/
So is the security debt. So is the technical debt crisis accumulating in production codebases. So is the skill atrophy happening in developers who never learned to read code carefully. So is the hangover that comes six months after the weekend sprint when nobody can explain how the system works anymore.
https://videotik.netlify.app/
The most honest version of the answer to "are we building faster or building bigger messes?" is: yes to both, depending entirely on who is driving.
https://videotik.netlify.app/
A senior developer with strong fundamentals using AI to handle boilerplate while making architectural decisions themselves? Genuinely more productive than ever before.
https://videotik.netlify.app/
A junior developer or a founder shipping AI-generated code to production without understanding it? Building on sand, and the tide is coming.
https://videotik.netlify.app/
The tool is neutral. The discipline is what determines the outcome.
https://videotik.netlify.app/

Build with AI. Review everything. Understand what you ship. The vibe is optional. The accountability never is.

https://videotik.netlify.app/

https://videotik.netlify.app/
How is vibe coding playing out in your day-to-day work? Are you seeing the speed gains, the debt accumulating, or both? Drop your take in the comments — actual developer experience beats any research paper.
https://videotik.netlify.app/

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

We Broke Our App Into 50 Microservices. Then We Put It Back Together — And Cut Costs by 90%

Hanzla Baig — Sat, 09 May 2026 15:08:01 +0000

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

The software industry has a dangerous habit of copying solutions without understanding the problems they were built to solve. This blog is about that habit — and what happens when you finally stop.

The Microservices Dream vs. The Microservices Reality

For the past decade, microservices have been sold as the gold standard of modern software architecture. Break your app into small, independent services. Deploy them separately. Scale them individually. Sleep better at night.

Sounds perfect. And for some teams, it genuinely is.

But here is the part nobody talks about at conferences: a massive wave of engineering teams that adopted microservices are quietly rolling them back. Not because microservices are bad. But because they adopted an advanced solution to a problem they did not actually have yet.

Amazon Prime Video moved a distributed microservices system back into a monolith and cut infrastructure costs by over 90%. Segment consolidated 50+ microservices back into a monolith. Stack Overflow runs one of the most visited websites on the internet on a single, well-optimized monolith.

These are not failures. These are engineering teams that ran the experiment, measured the results, and made the rational decision.

This blog breaks down exactly why this is happening, what the real cost of unnecessary microservices looks like, how to identify if your architecture is working against you, and what a better path forward actually looks like.

What Microservices Actually Promise (And Why Teams Buy In)

Before criticizing the approach, it is worth being honest about why microservices are genuinely appealing.

Independent deployability is the biggest draw. When each service is its own deployable unit, one team can ship updates without waiting on another team. No code freeze. No coordination meeting. No "who merged what into main."

Independent scalability is the second promise. Instead of scaling your entire application when only one component is under load, you scale just that component. Your payment service gets traffic spikes on Black Friday? Scale just that. The rest of the system does not need to grow.

Technology flexibility is another pitch. Each service can use the language and stack that best fits its job. Your data processing service can run Python. Your API gateway can run Go. Your legacy integration layer can stay in Java.

Fault isolation rounds it out. If one service crashes, theoretically the rest of the system stays up. A bad deploy in your notification service should not bring down your checkout flow.

These are real, legitimate benefits. The problem is not the benefits — the problem is the cost that comes with them, and whether that cost makes sense for where your team and product actually are.

The Hidden Costs Nobody Puts In The Slide Deck

Every architectural decision is a trade-off. Microservices give you the benefits listed above, but they demand serious payment in return. Here is what that bill actually looks like.

1. Network Overhead and Latency

In a monolith, service A calling service B is a function call. It happens in nanoseconds, in memory, with no failure modes beyond a software bug.

In a microservices architecture, service A calling service B is an HTTP request (or gRPC call, or message queue publish). It crosses a network. It can time out. It can fail. It adds latency. And when you have 10 services all calling each other in a request chain, that latency compounds.

A 5ms response per service call across 8 chained services adds 40ms of pure network overhead to every user request — before your actual business logic even runs.

2. Distributed Systems Complexity

This is the one that truly breaks teams.

Distributed systems introduce failure modes that simply do not exist in a single process. You now have to reason about:

Partial failures — what happens when Service B is halfway through a transaction and Service C times out?
Network partitions — services that cannot reach each other, even though both are running fine
Data consistency — when your User Service updates a record, how long before your Order Service sees that change?
Idempotency — if a request is retried, will running it twice break things?
Circuit breakers — you need logic to stop hammering a failing downstream service
Backpressure — what happens when upstream traffic exceeds what downstream services can handle?

Every one of these problems requires engineering time to solve properly. None of them exist in a well-structured monolith.

3. Observability and Debugging Complexity

In a monolith, a bug has a stack trace. You open one log file, find the error, fix it.

In a microservices system, a single user request might touch 12 services. When something fails, you need:

Distributed tracing (e.g. Jaeger, Zipkin, Datadog APM) to follow a request across service boundaries
Centralized log aggregation (e.g. ELK Stack, Loki) to query logs from all services in one place
Correlation IDs manually threaded through every request so you can link logs together
Service maps to understand which services talk to which

Without all of this infrastructure in place, debugging a production issue in a 50-service system can take hours. With a monolith, the same issue often takes minutes.

4. Infrastructure and Cloud Cost

Running 50 services means:

50 sets of compute resources (even at minimum spec)
50 log streams being collected and stored
50 health checks running continuously
50 containers with their own memory overhead
Inter-service network traffic costs (especially in cloud environments that charge for data transfer)
A service mesh or API gateway to route traffic between services
A secrets manager entry for each service
CI/CD pipelines multiplied by 50

A team that pays $3,000/month running a well-optimized monolith can easily find themselves paying $30,000–$50,000/month after a full microservices migration — without any increase in actual user traffic.

5. Cognitive and Operational Load

Every engineer on your team now needs to understand not just their own service, but how it fits into the broader system. Onboarding a new developer is dramatically harder. You cannot just clone one repo and run it — you need to spin up dependent services, configure service discovery, set up local networking, and understand a dozen contracts between services.

This cognitive overhead silently slows down development velocity, which is often the exact opposite of what the microservices migration was supposed to achieve.

The Core Mistake: Copying Netflix Without Having Netflix's Problems

Netflix, Amazon, Uber, Google — these companies built microservices at massive scale because they had massive scale problems.

Netflix was running on a single data center and a single monolith when it experienced a major database corruption incident in 2008 that took down the service for three days. They had hundreds of millions of users. They needed geographic redundancy, independent team deployments across a 1,000+ engineer organization, and the ability to scale individual components in ways a single application could not support.

Their problem was genuinely a distributed systems problem.

Most companies adopting microservices do not have that problem. They have a code organization problem, or a team coordination problem, or a deployment pipeline problem — all of which have much cheaper, simpler solutions that do not require introducing distributed systems complexity.

The question is never "are microservices good?" The question is always "do I have the specific problem that microservices solve?"

How To Know If Your Microservices Are Hurting You

There are clear signals that your service decomposition has gone too far or was done prematurely.

Signal 1: Services that are always deployed together

If Service A and Service B are almost always deployed at the same time, they are not actually independent. They have implicit coupling that you are paying the full cost of distributed systems to manage — without getting the deployment independence benefit.

Signal 2: Services that always call each other synchronously

If your request flow is User Request → Service A → Service B → Service C → Service D before returning a response, you have a distributed monolith. You have the complexity of microservices with none of the benefits. Every hop is a latency hit and a failure point.

Signal 3: Cross-service database transactions

If your code uses distributed transactions (two-phase commit, saga patterns, etc.) to maintain consistency across service boundaries, ask yourself: are the business benefits worth this complexity? For most applications at most stages of growth, the answer is no.

Signal 4: A single-digit engineering team managing double-digit services

Microservices exist to let large teams work independently. If you have 8 engineers managing 40 services, each engineer is responsible for 5 services. That is not independence — that is overhead.

Signal 5: Debugging takes disproportionately long

If your mean time to resolve a production incident has gone up since adopting microservices — not because your system is more complex functionally, but because it is harder to trace issues — that is a direct, measurable cost of your architecture.

Signal 6: Your cloud bill scaled faster than your user base

Infrastructure cost should grow roughly proportionally with usage. If your costs tripled but your users grew 30%, the architecture itself is generating unnecessary expense.

The Modular Monolith: The Architecture The Industry Stopped Talking About

The alternative to microservices is not a tangled, spaghetti codebase where everything depends on everything else. That is a bad monolith, and it is absolutely worth avoiding.

The real alternative is a modular monolith — a single deployable application with well-defined internal module boundaries, clear ownership, enforced separation of concerns, and explicit contracts between modules.

Think of it this way: microservices enforce boundaries at the network level. A modular monolith enforces boundaries at the code level. Both can achieve good separation. One of them does it without adding a network between every boundary.

What a Modular Monolith Looks Like in Practice

/src
  /modules
    /users
      users.controller.ts
      users.service.ts
      users.repository.ts
      users.module.ts       ← exposes only what other modules need
    /orders
      orders.controller.ts
      orders.service.ts
      orders.repository.ts
      orders.module.ts
    /payments
      payments.controller.ts
      payments.service.ts
      payments.module.ts
    /notifications
      notifications.service.ts
      notifications.module.ts
  /shared
    /database
    /config
    /types

Each module owns its own data access layer, its own business logic, and exposes a clean interface to other modules. Cross-module communication goes through defined interfaces — not internal database queries or direct class instantiation from outside the module.

The boundaries are real. The enforcement is through code review, linting rules, and architecture tests (tools like ArchUnit for Java or dependency-cruiser for JavaScript can enforce that Module A does not import directly from Module B's internals).

The difference is that these boundaries live in one deployed application, one process, one set of compute resources — and they communicate through function calls, not HTTP requests.

Which Services Actually Deserve To Be Separate

This is not an argument to never use microservices. Some services genuinely benefit from being extracted.

Keep separate if the service has fundamentally different scaling requirements. A video transcoding pipeline that needs GPU instances and takes minutes per job should not live in the same process as your fast, lightweight API server. The operational profiles are incompatible.

Keep separate if the service has regulatory or compliance isolation requirements. Payment processing under PCI DSS, healthcare data under HIPAA — these often benefit from strict process and network isolation for compliance and audit purposes.

Keep separate if the service is owned by a completely separate team with no shared codebase. If an entirely different engineering team in a different department maintains a service, a clear API boundary with separate deployment is the right call.

Keep separate if the service needs independent release cycles that are genuinely different from the rest of the system. A machine learning inference service that is updated by a data science team on a different cadence from the main product is a reasonable extraction.

The key question to ask every time: Is this service separate because it has a different operational profile, or is it separate because someone drew a box on an architecture diagram?

A Framework For Making The Architecture Decision

Use these questions before committing to any architectural direction.

Question	Microservices Makes Sense	Monolith Makes Sense
How many engineers?	20+ actively shipping	Under 15
How well-understood are your domain boundaries?	Stable, clear, proven over time	Still evolving, new product
What is your deployment frequency?	Multiple teams, multiple times/day	One team, a few times/week
What is your current scale?	Millions of users, heavy load	Growing, under 500k users
Do you have platform engineering capacity?	Dedicated platform/infra team	Developers wear multiple hats
What is your operational maturity?	Distributed tracing, observability in place	Basic logging and monitoring

If the answers lean consistently toward the right column, start with a modular monolith. You can always extract services later — once the boundaries are well-understood and the team genuinely needs the independence.

Extracting a service from a clean modular monolith is a well-understood, manageable engineering task. Collapsing a poorly-conceived microservices architecture back into something coherent is significantly harder.

The Performance Reality

Beyond cost, there is a direct performance story here that often gets overlooked.

Modern hardware is extraordinarily fast. A well-optimized monolith running on a single large instance can handle more throughput than most products will ever need.

Stack Overflow handles over 1.3 billion page views per month with a handful of servers running a monolith. They have published detailed benchmarks showing their primary SQL server idles at around 10% CPU under normal load.

The argument for microservices-based performance usually comes down to horizontal scaling — the ability to spin up more instances of a single service under load. But you can also horizontally scale a monolith. Running 4 instances of your monolith behind a load balancer is a completely valid, simple, and well-understood approach to scaling.

The performance case for microservices becomes real only when different components of your system genuinely have different resource profiles and different traffic patterns that justify running them on different hardware configurations. For most applications, that is not the reality.

What The Real Cost Comparison Looks Like

Here is a realistic infrastructure cost comparison for a mid-sized SaaS product with approximately 50,000 active users.

Microservices architecture (40 services):

Cost Category	Monthly Estimate
Compute (ECS/Kubernetes, 40 services)	$8,000 – $12,000
Load balancers (one per service)	$3,000 – $5,000
Log aggregation and storage	$2,000 – $4,000
Service mesh / API gateway	$1,500 – $3,000
Distributed tracing infrastructure	$1,000 – $2,000
Inter-service networking costs	$500 – $1,500
Total	$16,000 – $27,500

Modular monolith (2–3 services: monolith + background worker + media processor):

Cost Category	Monthly Estimate
Compute (2–3 large instances)	$800 – $1,500
One load balancer	$200
Centralized logging	$300 – $600
Basic monitoring	$100 – $300
Total	$1,400 – $2,600

The same product. The same users. The same features. A cost difference of 10–15x.

What "Moving Back" Actually Requires

If you are in the situation of managing an overengineered microservices system and considering consolidation, here is a practical approach.

Step 1: Audit coupling.
Map which services call each other. Any pair of services that communicate synchronously on the critical path and are deployed together more than 80% of the time is a merge candidate.

Step 2: Identify data ownership.
The hardest part of merging services is unifying databases. Start by merging services that already share a database, or where one database is a clear superset of another. These are the low-hanging fruit.

Step 3: Merge one pair at a time.
Do not attempt a big-bang consolidation. Pick the two most tightly coupled services and merge them into one module within a shared codebase. Deploy that. Measure it. Then continue.

Step 4: Keep the interfaces.
Even after merging, keep the internal module interfaces clean. The fact that it is now one deployed service does not mean the internal code structure should collapse. Maintain clear module boundaries — you might extract again someday if scale genuinely demands it.

Step 5: Decommission completely.
Once the merged version is running stably in production, decommission the old individual services. Delete the repositories, remove the CI/CD pipelines, close the log streams. The goal is to actually reduce operational surface area, not just merge code while keeping all the old infrastructure running in parallel.

Microservices vs Modular Monolith: Side-by-Side Comparison

Factor	Microservices	Modular Monolith
Deployment	Independent per service	Single deployment unit
Scaling	Per-service granularity	Horizontal scaling of full app
Debugging	Requires distributed tracing	Single log file / stack trace
Team independence	High (each team owns a service)	Medium (shared repo, clear modules)
Infrastructure cost	High	Low
Operational complexity	High	Low
Onboarding new devs	Slow (multiple repos, service mesh)	Fast (one repo, one local run)
Technology flexibility	High (per-service stack)	Low (shared runtime)
Network latency	Present on every service call	Zero (in-process calls)
Data consistency	Hard (distributed transactions)	Easy (shared database)
Best for	Large teams, stable domains, high scale	Small/mid teams, evolving product

The Broader Lesson About Architecture Decisions

Architecture decisions should be driven by specific, measurable problems — not by industry trends, conference talks, job posting requirements, or what the large tech companies do.

Every architecture has trade-offs. The job of a good engineer is not to pick the most sophisticated option available. It is to pick the option that best fits the current constraints: team size, product maturity, operational capacity, budget, and expected growth trajectory.

A well-structured modular monolith that ships features quickly, runs reliably, and costs $2,000/month to operate is a better technical decision for most products than a microservices architecture that costs $25,000/month, requires a dedicated platform team to maintain, and makes debugging a multi-hour exercise.

Simplicity is not a compromise. In engineering, simplicity is one of the hardest things to achieve and one of the most valuable things to protect.

The engineers who built the original Unix philosophy had it right: do one thing, do it well. That applies not just to the services themselves but to the decision of how many services you actually need.

Build the simplest architecture that solves your current problems well, with room to evolve as your real problems grow. That is not settling. That is engineering judgment.

Key Takeaways

Microservices solve specific, large-scale organizational and operational problems. They are not a default best practice for every product at every stage.
The hidden costs are real and compounding. Distributed systems complexity, debugging overhead, infrastructure cost, and cognitive load add up fast.
A modular monolith gives you clean boundaries without the operational overhead of a distributed system. Most products are better served by it during their growth phase.
The decision should be data-driven. Assess team size, domain maturity, scale, and operational capacity. Let those answers drive the architecture.
Consolidation is a legitimate engineering decision. If you are already in microservices and feeling the pain, audit coupling, merge incrementally, and keep internal module boundaries clean.
The goal is always maximizing value delivered to users per unit of engineering effort. Sometimes that means microservices. More often than the industry admits, it means a very good monolith.

Are you running microservices that work brilliantly, or ones that are costing more than they give back? Drop your architecture setup and team size in the comments — real data from real engineering teams is more useful than any conference talk.

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

Roshan Fitness

RoshanFitnessZone offers workout plans, weight loss tips, muscle building guides, and healthy diet plans to help you stay fit and achieve your fitness

roshansfitnesszone.blogspot.com

🤔 Questions Only Developers Will Lose Sleep Over (And Secretly Love Answering)

Hanzla Baig — Fri, 08 May 2026 10:28:27 +0000

🤔 Questions Only Developers Will Lose Sleep Over (And Secretly Love Answering)

By a Developer, For Developers — Who Else Would Actually Read This?

Published · 12 min read · ☕ Grab your coffee. Or your third one. We don't judge.

Introduction: Welcome to the Developer Brain

There's a very specific kind of person who, at 2 AM, is staring at a blinking cursor, asking themselves existential questions — not about life, love, or the universe — but about whether an undefined and a null are truly different in spirit.

That person is a developer. And that person is you.

This blog post is not a tutorial. There's no npm package to install. No boilerplate to clone. No .env file to forget to add to .gitignore (we've all done it, we don't talk about it).

This is a collection of the most delightfully cursed questions that every developer has thought about at some point — questions that have no right answer, only stronger opinions. Read them, argue in the comments, and forward this to the developer friend who will get personally attacked by at least three of these.

Let's go. 🚀

🐛 Question 1: If a Bug Is Fixed But No One Writes a Test for It, Did the Bug Ever Really Exist?

Imagine this scenario:

A user reports a bug.
You reproduce it.
You fix it in 20 minutes.
You close the ticket.
You do NOT write a test.
Three weeks later, the bug is back.

Now here's the philosophical dilemma: Is this the same bug returning, or a brand new bug that happens to look exactly like the old one?

If there's no test to define the expected behavior, does the bug have a legal right to exist again?

This is basically the Schrödinger's Bug of software development. Until you observe it (via a failing test), the bug exists in a superposition of fixed and not-fixed.

The uncomfortable truth: The bug was never truly fixed. It was just scared away temporarily. Like a raccoon in a dumpster — you can shoo it, but it will come back when you're not looking.

Hot take: A fix without a test is just a wish. A very confident wish.

💻 Question 2: Is It Still "Clean Code" If It Works But You Can't Explain It the Next Morning?

You wrote it at 11 PM. It was elegant. It was clever. It used a reduce inside a map inside a filter and you felt like an absolute genius.

const result = data
  .filter(x => x?.meta?.active && !x?.flags?.includes('deprecated'))
  .map(({ id, payload: { nested: { value } = {} } = {} }) => ({ id, value }))
  .reduce((acc, { id, value }) => ({ ...acc, [id]: (acc[id] || 0) + value }), {});

Next morning. Fresh eyes. Coffee in hand.

...what

You added a comment:

// This works. Please don't touch it.
// I'm serious. Don't.
// — Past Me (who was clearly unwell)

Is it clean code? Robert C. Martin says clean code reads like well-written prose. This reads like a ransom note written in a hurry. And yet — it ships. It works. The tests pass (because you wrote the tests when you were also unwell).

The real question: Is "clean" about readability, or about results? And does the answer change depending on whether your team can read it?

Rule of thumb: If you can't explain the code to a rubber duck without whispering, it's not clean. It's haunted.

🔢 Question 3: Are `null`, `undefined`, `0`, `""`, and `false` the Same Thing — or 5 Different Ways to Ruin Your Day?

JavaScript decided that the concept of "nothing" needed five distinct representations. Let's honor that decision by understanding exactly how each one will destroy you:

Value	What It Technically Means	What It Feels Like
`null`	Intentional absence of value	"I deliberately put nothing here"
`undefined`	Variable declared but never assigned	"I forgot this existed"
`0`	The number zero	"Something happened. It was just zero."
`""`	An empty string	"I had a field. It had no content."
`false`	Boolean false	"No. Just no."

They are all falsy. They will all evaluate to false in an if statement. They are not the same. This matters when you're trying to tell the difference between "the user didn't answer" (undefined), "the user answered nothing" (null), and "the user answered zero" (0).

if (!userScore) {
  console.log("No score recorded");
  // This runs for 0, null, undefined, false, and ""
  // Congrats, you just told a user who scored 0 that they didn't play
}

The correct fix:

if (userScore === null || userScore === undefined) {
  console.log("No score recorded");
}
// Now 0 is treated as a valid (if humbling) score

Life lesson: Always use === null or === undefined. Never trust !value. JavaScript is not your friend here. It's chaotic neutral.

🤯 Question 4: If You Google the Same Stack Overflow Answer 5 Times, Is It Time to Just Memorize It?

Let's be honest about something: there are answers you have Googled so many times that Stack Overflow should just start auto-completing your name in the "viewed by" section.

The top questions developers Google on repeat:

"How to center a div CSS"
"How to reverse a string in [language]"
"Git undo last commit"
"Python read file line by line"
"SQL left join vs inner join"
"How to exit vim" (this one is eternal)

The question is: at what point does repeatedly Googling the same thing cross from "healthy reference behavior" into "I should probably just know this"?

The answer, backed by zero research but strong feelings:

1–3 times: Completely normal. You're still learning the context.
4–7 times: The knowledge is there, you just don't trust yourself.
8–15 times: At this point you could write the Stack Overflow answer yourself.
16+ times: You ARE the answer. You are a living documentation page. You have ascended.

Fun fact: The most-viewed Stack Overflow question of all time is "How do I exit Vim?" with over 4 million views. We are, as a species, collectively unable to exit a text editor.

🚀 Question 5: Is "Deploying to Production" the Same as "Sending a Prayer to the Cloud"?

There is no ritual more sacred, more terrifying, more heart-rate-elevating in software development than the Friday afternoon production deploy.

The pre-deploy internal monologue:

"Tests pass. Staging looks fine. Code review was... mostly positive. Jenkins is green. But what if — WHAT IF — there's something I missed? What if this breaks payments? What if this breaks auth? What if the migration takes 10 minutes and the app times out? Should I just wait until Monday? It's 4:58 PM on a Friday. I should wait. But the ticket says HIGH PRIORITY. I'll deploy. No — I won't. I will. Here goes."

The deploy checklist every developer actually runs:

[x] Code reviewed ✅
[x] Tests pass locally ✅
[x] Staging environment validated ✅
[x] Database migration tested ✅
[x] Rollback plan exists (kind of) ✅
[ ] Told the team (they'll find out) 🤐
[ ] Made peace with whatever happens next 🙏

The three outcomes of every production deploy:

It works perfectly. You feel like a god. You close your laptop and go home like a champion.
Something breaks immediately. You revert. You learn. You survive. (Usually.)
Nothing breaks... yet. This is the worst one. The bug is waiting. It's learning. It knows.

Golden rule: Never deploy on a Friday unless you enjoy working weekends. This is not a joke. This is sacred scripture.

⌨️ Question 6: When You Rename a Variable from `data` to `theData` — Is That Refactoring?

Let's define our terms.

Refactoring (noun): The process of restructuring existing code without changing its external behavior, in order to improve its internal structure, readability, or maintainability.

Now. You have a variable called data. It's confusing. You rename it to theData. Your IDE updates it across 12 files. You commit:

git commit -m "refactor: improved variable naming for clarity"

Is this refactoring?

Technically: Yes. You changed internal structure. Behavior is unchanged. It meets the definition.

Practically: Your senior dev will raise one eyebrow during code review and say nothing. That eyebrow contains multitudes.

The real refactoring spectrum:

Action	Level	Respect Gained
Rename `data` to `userData`	Naming improvement	+1
Extract a 200-line function into 5 focused functions	Actual refactoring	+10
Replace nested callbacks with async/await	Pattern improvement	+15
Rewrite the entire module with proper SOLID principles	Architecture work	+50
Rewrite it in Rust "for performance"	You've seen too much	+0 (everyone is scared)

The uncomfortable truth: Most "refactoring" is really just "I couldn't read this at 9 AM so I made it slightly more readable and called it refactoring." That's fine. That's valid. Keep doing it.

🧪 Question 7: Are Unit Tests Just Very Angry Comments That Run Automatically?

Consider:

A comment says:

# This function should return the sum of two numbers
def add(a, b):
    return a + b

A unit test says:

def test_add_returns_sum_of_two_numbers():
    assert add(2, 3) == 5
    assert add(-1, 1) == 0
    assert add(0, 0) == 0

The comment describes the intent. The unit test enforces it — and yells at you when you violate it.

FAILED tests/test_math.py::test_add_returns_sum_of_two_numbers
AssertionError: assert 6 == 5

That's a comment that fought back.

Types of test emotions:

AssertionError — Betrayal. Disappointment. How could you.
TypeError — Confusion. "You passed WHAT type?"
TimeoutError — Exhaustion. "I waited. You never came."
All tests passing — Pure, unconditional love. Cherish it.

The stages of a developer's relationship with testing:

Denial: "I don't need tests, I know what my code does."
Anger: "Writing tests takes longer than writing the code!"
Bargaining: "I'll just write tests for the important parts."
Depression: [stares at 23 failing tests at 11 PM]
Acceptance: "Tests are love. Tests are life. Tests are the only thing standing between me and 3 AM production incidents."

Wisdom: Write the test first. Hear me out. Write the test first. You'll thank yourself at 3 AM when you're not debugging a production incident.

🕰️ Question 8: Does "It'll Take 2 Hours" Ever Actually Mean 2 Hours?

Short answer: No.

Long answer: No, and here is why, presented with scientific rigor (loosely defined):

The Developer Time Dilation Table:

What the Developer Says	What It Actually Means
"5 minutes"	45 minutes to 2 hours
"Quick fix"	Entire afternoon
"It's almost done"	40% done, actually
"Just one more thing"	3 more things minimum
"Should be simple"	It's not simple
"2 hours"	2 days
"2 days"	End of sprint
"End of sprint"	Next sprint
"Next sprint"	Q3
"Q3"	"We're reconsidering the feature"

Why does this happen?

It's not laziness. It's not incompetence. It's called Hofstadter's Law:

"It always takes longer than you expect, even when you take into account Hofstadter's Law."

Translation: Even when you know you're underestimating, you still underestimate. The universe is conspiring against your timeline.

What actually takes 2 hours:

Setting up a new dev environment (if you're lucky)
Reading the codebase of a project you've never seen before
Debugging one off-by-one error in a nested loop
A meeting that was supposed to be 30 minutes

Pro tip for non-developers reading this: When a developer gives you an estimate, multiply by π. It's not a guarantee, but it's closer to the truth than whatever they said.

🌐 Question 9: If the Frontend Works AND the Backend Works, But Together They Don't — Whose Fault Is It?

This is perhaps the most ancient and sacred debate in all of software development. Let us examine it with the nuance it deserves.

The scene:

Frontend dev: "I'm sending the correct data. Look."
[shows network tab, request payload is perfect]

Backend dev: "I'm receiving and processing correctly. Look."
[shows logs, response is perfect]

The integration: 💥 500 Internal Server Error

The usual suspects:

CORS — It's almost always CORS. The browser is not your friend. It has opinions about who talks to whom.
Content-Type mismatch — One sends application/json, the other expects application/x-www-form-urlencoded. Classic.
Auth token format — "Bearer " vs "bearer " vs no space vs the wrong header entirely.
Date format — Frontend sends "2024-01-15", backend expects "15/01/2024". Timezones cry.
Null vs missing field — One sends { "name": null }, other expects {} with no name key. These are different. They will be treated differently.
Someone updated the API contract and didn't tell anyone — This is a people problem disguised as a tech problem.

Who is actually at fault?

Both. Neither. The real fault lies in the absence of a shared contract (like an OpenAPI spec) that both sides agreed to beforehand.

But in practice, the conversation goes:

Frontend: "This is a backend problem."
Backend: "This is a frontend problem."
DevOps: opens ticket, assigns it to both, goes back to managing Kubernetes

Solution: Write the API contract first. Both teams agree. Both teams implement. Both teams are friends. It's beautiful when it works.

🤖 Question 10: When You Use AI to Write Code You Don't Understand — Are You a Developer or a QA Engineer?

We need to talk about this. Productively. Without judgment. (A little judgment.)

The new developer workflow (2024 edition):

Have a problem.
Describe the problem to an AI.
Receive code that looks correct.
Copy the code.
Run the code.
It doesn't work.
Ask AI why it doesn't work.
Receive a fix.
The fix breaks something else.
Ask AI to fix the thing the fix broke.
Repeat from step 6.
Ship it because it seems fine now.

Is this bad? Not inherently. Using tools is what developers do. Every IDE, linter, framework, and library is a tool that abstracts complexity away.

Is there a risk? Yes. The risk is shipping code you fundamentally don't understand — which means you can't debug it when it breaks at 3 AM, you can't optimize it when it becomes slow, and you can't explain it in a code review without saying "the AI wrote it."

The healthy balance:

Use AI to speed up what you already understand.
Use AI as a learning tool, not a replacement for learning.
Read the code before you ship the code.
If you can't explain it, you don't own it yet.

The uncomfortable truth: AI is an incredible accelerator. But acceleration in the wrong direction just gets you to the wrong place faster. Understand first. Accelerate second.

🔄 Question 11: Is `git commit -m "fix"` an Acceptable Commit Message?

No.

But let's talk about why we do it anyway.

You've been debugging for 4 hours. You finally found it — a missing semicolon, a wrong variable name, a race condition that only manifests under specific load. You're exhausted. You're relieved. The last thing in the world you want to do is write a thoughtful commit message.

git commit -m "fix"

Done. Shipped. Moving on.

The git log of every developer's personal project:

abc1234 - fix
def5678 - fix2
ghi9012 - actually fix
jkl3456 - fix for real this time
mno7890 - ok this is the real fix
pqr1234 - FINAL fix
stu5678 - final FINAL fix
vwx9012 - why
yza3456 - it works don't ask
bcd7890 - please work
efg1234 - it works (don't touch)
hij5678 - hotfix
klm9012 - hotfix2

What a good commit message looks like:

fix(auth): prevent token refresh loop on expired session

When the access token expired and the refresh token was also
invalid, the refresh logic entered an infinite loop. Added a
max retry count of 3 before clearing credentials and
redirecting to login.

Fixes #4821

Why it matters: Future you — or your teammate — at 2 AM, bisecting the git history to find when this broke, will either bless you or curse you based on your commit messages. Choose who you want to be.

Commit message template to live by:
type(scope): short description
[blank line]
Longer explanation of what and why (not how)

💡 Question 12: Is Dark Mode a Preference or a Personality Trait?

This is not a technical question. This is a deeply personal one.

Evidence that dark mode is a personality trait:

Dark mode developers have opinions about which dark mode is "too dark."
They will audit your VS Code theme on the first day of pair programming.
They have a physical reaction — a genuine, visceral flinch — when a webpage opens in full white background.
They have adjusted the brightness of every screen in their home.
Their phone, IDE, browser, OS, email client, and notes app are all in dark mode. Consistency is a value, not a preference.

The dark mode developer when exposed to light mode:

System: "Light mode enabled."
Developer: looks directly at screen
Developer: "I need a moment."

The light mode developer (they exist):

"I find it easier to read."
universal confusion from the rest of the team

The scientific question: Is dark mode actually better for your eyes? The research is mixed. Dark mode reduces blue light emission (good for nighttime). But light mode may have better readability in bright environments. Contrast ratios matter more than the background color itself.

The real answer: Use whatever works for you. But know that the dark mode community has prepared arguments, and they are ready to deploy them at any standup.

Ranking of developer dark mode opinions:

One True Dark (pure black #000000) — Purist. Respect.

Soft Dark (like #1e1e1e) — Sensible. Popular.

Solarized Dark — Vintage. Respected.

"I use light mode at work" — uncomfortable silence

☕ Question 13: How Many Cups of Coffee Does It Take to Write One Function?

This is a highly scientific question with a highly variable answer.

The Coffee-to-Complexity Scale:

Task	Coffee Required
Write a utility function	½ cup
Debug someone else's code	2 cups minimum
Understand legacy code with no comments	1 full pot
Implement a feature with unclear requirements	2 pots + tea
Fix a production bug on a Friday afternoon	Mainline it directly
Read through the entire codebase of a new job	Consider switching careers

The four stages of developer caffeine:

Pre-coffee: "I can't even look at the IDE."
One coffee: "Okay. I understand the problem."
Two coffees: "I am the problem AND the solution."
Three coffees: "I rewrote the entire module and I have opinions about architecture now."

Health note: Please hydrate. Drink water. Your editor will still be there after you drink some water. The bugs will wait. Probably.

🔥 The Ultimate Developer Debates: Pick Your Side

These are not questions with right answers. These are questions with your answers. Choose wisely. Your reputation in the team Slack channel depends on it.

Debate 1: Tabs vs. Spaces

Team Tabs:

Tabs have semantic meaning (this is an indent).
Tab width is configurable. My 4-space indent is your 2-space indent, and that's beautiful.
More accessible — visually impaired developers can configure tab size.

Team Spaces:

Spaces look the same everywhere. In every editor, every terminal, every code snippet on the internet.
"But what about alignment?" Spaces. Always spaces.
Python agrees with us. (This argument ends conversations.)

The actual resolution: Use .editorconfig and let the file decide for the whole team. Then argue about something more interesting.

Debate 2: `===` vs. `==` in JavaScript

Team === (Strict Equality):

Checks both value AND type.
0 === false is false. As God intended.
No type coercion. No surprises.
This is the only acceptable choice.

Team == (Loose Equality):

null == undefined being true is actually useful sometimes.
JavaScript's type coercion is a feature, not a bug.
[no serious engineers are on this team]

Verdict: Use ===. This is not a debate. This is a teaching moment.

Debate 3: Semicolons vs. No Semicolons in JavaScript

Team Semicolons:

Explicit is better than implicit.
ASI (Automatic Semicolon Insertion) has edge cases that will ruin you.
The famous return followed by an object on the next line? ASI eats it. Semicolons prevent that.

Team No Semicolons:

Cleaner to read.
Prettier enforces it anyway.
If you know the ASI rules, you're fine.
"But what about the edge cases?" — Linters. We have linters.

Verdict: Pick one per project. Enforce it with a linter. Don't let this become a 30-minute PR comment thread. (It will become a 30-minute PR comment thread.)

Debate 4: camelCase vs. snake_case

The rule that almost everyone follows:

JavaScript/TypeScript: camelCase for variables and functions, PascalCase for classes.
Python: snake_case for everything (PEP 8 says so).
SQL: snake_case for columns and tables (the database doesn't care, but consistency matters).
CSS: kebab-case for class names.
Constants: SCREAMING_SNAKE_CASE everywhere.

The one who breaks the rule: The developer who writes Python in camelCase because "that's how I think." They know who they are. They are at peace with it.

Debate 5: MongoDB vs. PostgreSQL

Team MongoDB:

Flexible schema. Ship fast, evolve later.
JSON-native. Perfect when your data IS documents.
Great for certain use cases: catalogs, logs, content stores.

Team PostgreSQL:

ACID compliance. Transactions that actually work.
Joins. Real, beautiful, efficient joins.
JSON support INSIDE a relational database (best of both worlds, checkmate).
30+ years of battle-tested reliability.

Honest verdict: Use the right tool for the job. If your data is genuinely document-shaped and schema-less by nature — MongoDB has merit. If you have relational data, business logic, and need data integrity — PostgreSQL. The "MongoDB vs PostgreSQL" debate is usually a "I chose the wrong tool for the job" debate in hindsight.

🧠 Bonus Round: Questions With No Good Answers

Just to end on pure chaos:

"Should I use a framework or vanilla JS?" — Depends. [everyone groans]
"Is microservices or monolith better?" — Start with a monolith. You can always split it. You can't easily merge microservices back together. Fight me.
"How many files is too many files in one folder?" — The answer is one more than you currently have.
"Should I rewrite this or refactor it?" — Refactor. Almost always refactor. Rewrites are how projects die.
"Is it worth automating something that takes 3 minutes to do manually?" — [long pause] Yes. The automation will take 4 hours and save you 3 minutes per month, and you will find it entirely worth it.

🏁 The Final Question: After Everything — Why Do We Keep Coding?

After the bugs. After the 3 AM production incidents. After the merge conflicts, the unclear requirements, the legacy codebases that look like they were written by someone who hated future developers personally.

After all of that — why do we keep showing up?

Because of this:

✅ Build successful
✅ All 247 tests passed
✅ Deployed to production
✅ No errors in logs

Because of the moment when a user sends a message saying "this feature is exactly what I needed." Because of the satisfaction of a function that does exactly one thing and does it perfectly. Because of the weird, specific joy of finally understanding why the bug happened and watching the fix work in real time.

Because we build things that didn't exist before. Because code is one of the few crafts where you can go from "I have an idea" to "the idea exists and other humans can use it" in a matter of hours or days. Because there is no feeling quite like it.

We keep coding because, underneath all the frustration and the complexity and the coffee and the CORS errors, we actually love it.

Even when we won't admit it. Especially when we won't admit it.

Now: which question got you? Which one are you forwarding to your team right now? Drop a comment, argue in the replies, and tag the developer in your life who definitely Googles "how to center a div" every single week.

They know who they are.

About This Post
Written for every developer who has ever whispered "please work" to their terminal at midnight. You are not alone. The terminal cannot hear you. But we can.

The Life of a Developer in One Loop ❤

Hanzla Baig — Wed, 25 Mar 2026 13:21:43 +0000

Ever notice how being a developer is basically living in a constant loop of:

Wake up → Coffee → Code → Debug → Repeat

Some days, you’re the hero fixing bugs at 2 AM and the next day, you’re staring at your console wondering why nothing works. But here’s the funny part—every broken build, every weird error, every mysterious undefined is secretly teaching you more than any tutorial ever could.

We love automating things, yet somehow we end up spending hours manually debugging the thing we automated. We fight with Git like it’s our mortal enemy, only to realize we actually love it… eventually. And yes, there will always be that one commit you wish you could erase from history.

But despite the chaos, there’s nothing quite like that moment when your code finally runs perfectly on the first try… and then you realize you forgot to save.

Shoutout to all the developers who have ever:

Googled an error message like it’s sacred scripture
Spent more time naming variables than writing logic
Accidentally broken production at least once
Felt a weird pride when a project finally works

If you’re a dev, you get it. If you’re not… just know, we have fun in our own chaotic way.

💻 Keep coding, keep breaking things, and keep laughing at the madness.

React Is Not Slow — Your Architecture Is

Hanzla Baig — Fri, 16 Jan 2026 13:10:28 +0000

I'm going to say something that might sting a little: if your React application is slow, it's almost certainly not React's fault. I've been building production React applications for years now, and I've seen this pattern repeat itself over and over again. A team builds something, it starts getting sluggish, and suddenly React becomes the scapegoat. "React is too slow," they say. "We should've used Svelte," someone suggests in a retrospective. "Maybe we need to rewrite this in vanilla JavaScript," another developer proposes, half-seriously.

Here's the uncomfortable truth: React is fast. Incredibly fast, actually. What's slow is the architecture you built on top of it. The tangled mess of components that re-render on every keystroke. The global state that's subscribed to by half your application. The 500-line component that's trying to do everything at once because "it's all related functionality." The Context providers nested twelve levels deep, each one triggering cascading updates through your component tree like dominoes falling in slow motion.

I'm not here to shame anyone. I've made every single one of these mistakes myself, often multiple times, because that's how you actually learn this stuff. You don't learn good React architecture from reading the docs once and building a todo app. You learn it by shipping a feature, watching it grind your app to a halt, spending three days debugging why a dropdown causes the entire page to freeze, and finally understanding—deeply, viscerally understanding—what you did wrong. This blog post is the distillation of all those painful lessons, the architectural mistakes I've made and seen others make, and what I've learned about building React applications that actually perform well.

Why Developers Think React Is Slow

Let's start by acknowledging that the perception of React being slow is incredibly common, especially among developers who are either new to React or who learned it in a specific way that encourages bad patterns. And honestly, I get it. When you first start building with React, everything seems fine. Your todo app renders instantly. Your small dashboard feels snappy. Then your application grows, you add more features, more state, more components, and suddenly everything feels sluggish. The interface starts lagging. Inputs feel unresponsive. You open the React DevTools profiler and see this horrifying cascade of components re-rendering, and you think, "This framework is the problem."

But here's what's actually happening: you're running into the natural consequences of architectural decisions you made when your app was small, decisions that don't scale. The problem isn't that React is slow—it's that React is extremely good at exposing bad architecture. React will happily re-render your entire component tree on every state change if you tell it to. It will dutifully run every expensive calculation you put in your render functions. It will obediently trigger effects and updates in whatever tangled dependency chain you've created. React is not opinionated enough to stop you from doing these things, which means it's incredibly easy to build something that performs poorly if you don't understand what you're doing.

One of the biggest reasons developers perceive React as slow is poor component structure. I see this constantly: components that are too big, too complex, and doing way too much. A single component handling data fetching, state management, business logic, conditional rendering for a dozen different scenarios, and managing side effects all at once. When that component re-renders—and it will re-render often because it's touching so much state—everything inside it runs again. Every function gets redefined. Every calculation gets recomputed. Every child component receives new props and has to decide whether it needs to re-render. This isn't React being slow; this is you forcing React to do an enormous amount of work every single update cycle.

Another massive issue is unnecessary re-renders. This is probably the number one performance problem I see in React applications, and it stems from a fundamental misunderstanding of how React's rendering model works. Developers will structure their state in a way that causes huge portions of their component tree to re-render when only a tiny piece of data changes. They'll lift state way too high up the tree because "these components need to share data," not realizing that they've just made 47 components re-render every time a user types in a search box. They'll create Context providers for convenience without understanding that every component consuming that context will re-render whenever any value in that context changes, even if they're only using a small piece of it.

And then there's the overuse of state. Not all data needs to be state. I've reviewed codebases where literally everything is in state, including data that could be derived from other state, data that never changes, data that's only used in event handlers, and data that should actually be refs. Every piece of unnecessary state is another potential trigger for re-renders, another moving part that makes your application harder to reason about and slower to update. React's useState and useReducer hooks are powerful, but with great power comes great responsibility, and apparently also the great temptation to put absolutely everything into state "just in case."

Bad data flow decisions compound all of these problems. When you don't have a clear strategy for how data moves through your application, you end up with state scattered everywhere—some in components, some in Context, some in a global store, some in URL params, some in refs, some passed through props five levels deep. Nobody knows where the source of truth is. Updates are unpredictable. You fix a performance issue in one place and cause three new ones somewhere else. This isn't a React problem; this is a failure to design a coherent data architecture.

The Architectural Mistakes That Kill Performance

Let me walk you through the specific architectural mistakes that I see destroying React application performance. These aren't obscure edge cases or advanced optimization failures. These are fundamental design problems that slow down applications, make them hard to maintain, and lead developers to incorrectly blame React.

Massive components that do everything. This is the cardinal sin of React architecture. You've seen these components. Hell, you've probably written these components. I know I have. They're 500, 800, sometimes over a thousand lines long. They manage five different pieces of state. They have ten useEffect hooks, half of which have dependency arrays that nobody fully understands anymore. They fetch data, process it, display it, handle user interactions, manage forms, coordinate with other parts of the application, and probably make coffee too if you dig deep enough into the code.

These monolithic components are performance killers because when they re-render, everything inside them runs. Every single line of JSX gets processed. Every inline function gets redefined. Every calculation happens again. And because they're often at the root of some section of your UI, their re-renders cascade down to dozens or hundreds of child components. The worst part is that these components usually re-render way more than necessary because they're touching so much state. A user updates a form field? Re-render the whole thing. Data comes back from an API? Re-render the whole thing. A child component calls a callback? You guessed it—re-render the whole thing.

The reason this happens is usually because developers start with a simple component that does one thing well, and then they keep adding to it. "Oh, we need to handle this edge case, I'll just add a bit more state." "This related functionality needs access to the same data, I'll just put it in here." "We need to coordinate these two things, might as well keep them together." Before you know it, you have a component that's responsible for an entire feature area, and extracting logic from it seems impossible because everything is so tangled together.

Prop drilling chaos. Prop drilling gets a bad rap, and honestly, a lot of that criticism is deserved. But the real problem isn't prop drilling itself—it's what prop drilling represents: a failure to properly structure your component hierarchy. When you're passing props down through five or six levels of components, that's usually a sign that your component tree doesn't match your data flow. You've created intermediate components that don't actually care about the data they're passing through, they're just dumb conduits, and every time you need to add a new piece of data or change how something works, you have to modify every single component in that chain.

But here's where it gets really bad for performance: developers often "solve" prop drilling by lifting state higher and higher up the tree, thinking they're making things simpler. Now the state lives in some common ancestor component that's far removed from where the data is actually used, and every update to that state causes a huge portion of your component tree to re-render. You've traded the inconvenience of prop drilling for a massive performance problem, and you probably didn't even realize you were making that trade-off.

Global state abuse. Oh man, global state. This is where things get spicy. Global state management libraries like Redux, Zustand, MobX, and others are incredibly useful tools. They're also incredibly easy to misuse, and when you misuse them, you create performance nightmares. I've seen applications where almost all state is global. Every piece of UI state, every form value, every loading flag, every error message—it's all in the global store. The reasoning is usually something like "we might need this data somewhere else" or "it's easier to access from anywhere" or "this is how we do state management."

The problem is that when everything is in global state, everything is connected to everything else. Components subscribe to slices of the global store, but often they subscribe to more than they need, or the slices aren't granular enough, or the selectors aren't optimized. A user types in a search input in one corner of your application, updating global state, and suddenly twenty components in completely unrelated parts of your UI are re-rendering because they're subscribed to the same store slice or because you didn't properly implement selector equality checks.

Global state should be for actually global concerns: user authentication, theme preferences, data that truly needs to be shared across distant parts of your application. It should not be your default choice for all state. Yet time and time again, I see developers reach for the global store first, local component state second, and then wonder why their application is slow and hard to reason about.

Context API misuse. The Context API is one of React's best features and also one of its most dangerous. Context is fantastic for dependency injection, theming, providing stable values throughout a tree, and avoiding prop drilling for data that truly needs to be accessed at multiple levels. But Context has a fundamental characteristic that many developers don't fully appreciate: when a Context value changes, every component consuming that Context re-renders. Every single one. Even if they're only using a tiny piece of the Context value.

I've seen developers create a single massive Context provider for an entire feature area, stuffing everything into one Context value—user data, UI state, API responses, form values, you name it. Then they sprinkle useContext calls throughout dozens of components, and suddenly the entire feature re-renders whenever any piece of that Context changes. A loading flag flips from true to false? Everything re-renders. A form field updates? Everything re-renders. Some unrelated data gets updated? You get the idea.

The solution isn't to avoid Context—it's to use it thoughtfully. Multiple smaller Contexts are often better than one large one. Context values should change infrequently. If you need frequently-changing values to be available throughout a tree, Context probably isn't the right tool—you need a proper state management solution with subscriptions, or you need to rethink whether that data really needs to be globally available.

Treating React like jQuery. This is a more subtle mistake, but it's incredibly common among developers who came to React from imperative programming backgrounds or who haven't fully internalized React's declarative model. These developers write React code that's constantly fighting against React's design. They store references to DOM nodes and manipulate them directly. They try to coordinate updates imperatively instead of declaratively. They reach for useEffect for things that should just be derived state or regular event handlers. They treat state updates like direct mutations instead of transitions from one UI state to another.

This approach leads to confusing code that's hard to reason about and often performs poorly because you're working against React's optimizations instead of with them. React is designed around the idea that you describe what the UI should look like for any given state, and React figures out how to make that happen efficiently. When you try to manually orchestrate things imperatively, you bypass those optimizations and create code that's both slower and more bug-prone.

How React Actually Works (And Why It's Fast By Design)

To understand why React is not inherently slow, you need to understand what React actually does under the hood. I'm not going to walk you through the source code—that's not useful for most developers—but I am going to explain the conceptual model that makes React fast by design, because once you understand this, a lot of performance optimization becomes intuitive.

React's core job is to keep your UI in sync with your state. That's it. That's the whole ballgame. You have some state, and you have a description of what the UI should look like for that state, and React's job is to make the actual DOM match that description. The genius of React is in how it does this efficiently, even when state changes frequently and the UI descriptions are complex.

Reconciliation is the process React uses to figure out what actually needs to change in the DOM when your state updates. This is crucial because DOM manipulation is expensive—it's one of the slowest things you can do in a web browser. Creating DOM nodes, updating them, removing them, and especially causing layout recalculations and repaints—all of this is computationally expensive. So React's fundamental goal is to minimize DOM operations.

Here's how it works conceptually: when your state changes and React needs to re-render, it doesn't immediately touch the real DOM. Instead, React calls your component functions to get a description of what the UI should look like—this description is your JSX, which becomes a tree of React elements. React then compares this new tree with the previous tree it rendered last time. This comparison process is reconciliation, and React's algorithm for doing this efficiently is pretty clever.

React walks through the tree, comparing elements. If an element's type hasn't changed (still a div, still the same component), React can reuse the existing DOM node and just update its properties. If the type changed (was a div, now a span), React knows it needs to destroy the old DOM node and create a new one. For lists of elements, React uses keys to match up which elements correspond to which, so it can efficiently handle reordering, additions, and deletions without recreating everything.

The Virtual DOM is often misunderstood. It's not some magical performance silver bullet—in fact, maintaining the Virtual DOM has overhead. The Virtual DOM is simply React's way of representing your UI as JavaScript objects (React elements) instead of actual DOM nodes. The advantage is that comparing JavaScript objects is much faster than manipulating the real DOM, so React can diff the old and new Virtual DOM trees, figure out the minimal set of changes needed, and then apply those changes to the real DOM in a batch.

Some people criticize the Virtual DOM as unnecessary overhead, and in some cases they're right—frameworks that compile to optimal imperative updates can be faster for certain workloads. But the Virtual DOM gives React a huge advantage: it makes React declarative and predictable. You don't have to manually track what changed and update the DOM accordingly. You just describe the entire UI for your current state, and React figures out the efficient way to make it happen. This makes React code much easier to write and maintain than imperative DOM manipulation, and for most applications, the performance is more than good enough.

Rendering versus committing is a crucial distinction that many developers don't understand. When React "renders" a component, it just calls your component function to get a React element tree. This is a pure operation—it doesn't cause side effects, doesn't touch the DOM, doesn't do anything except execute JavaScript to build a description of what the UI should be. Rendering is relatively cheap because it's just running JavaScript functions.

The "commit" phase is when React actually applies changes to the DOM. After React has rendered your components and diffed the new tree against the old one, it enters the commit phase and performs the actual DOM mutations. This is more expensive because DOM operations are expensive. But here's the key insight: React batches commits. Even if multiple state updates happen in quick succession, React groups them together, renders once, and commits once. This batching is a massive performance win.

Understanding this distinction helps you understand why some things cause performance problems and others don't. A component re-rendering is not necessarily expensive—it's just JavaScript execution. What's expensive is when that re-render leads to actual DOM updates, especially if those updates are large or cause layout recalculations. And what's really expensive is when you cause React to render and commit multiple times in rapid succession, bypassing the batching optimizations.

React is fast by design because it's built around these principles: minimize expensive DOM operations, batch updates, reuse existing work when possible, and give developers a declarative API that lets React handle the optimization details. When people say React is slow, what they usually mean is that their application is causing React to do far more work than necessary—rendering huge component trees on every update, triggering excessive DOM mutations, or bypassing React's optimizations through poor architectural choices.

The performance characteristics of React are actually pretty straightforward: rendering components is cheap until you have huge components or very deep trees, commits are expensive but React minimizes them, and side effects (like API calls, animations, or complex calculations) are as expensive as you make them. If you design your architecture around these characteristics—keep components small and focused, minimize unnecessary re-renders, and be thoughtful about expensive operations—React will be blazingly fast.

The Performance Killers Nobody Talks About

Everyone talks about re-renders and memoization, but there are performance killers in React applications that don't get nearly enough attention. These are the issues that cause real, user-facing slowness, yet they often go undiagnosed because developers are too busy optimizing the wrong things.

Over-fetching data is probably the most common performance problem in modern React applications, and it's barely a React issue—it's an API design and data fetching issue. Your component loads, fetches data from an API, gets back a massive JSON payload with ten times more data than you need, parses it all, processes it all, stores it all in state, and then renders based on a tiny slice of it. Then you do this for five different endpoints on the same page load, and you wonder why your application feels slow.

The problem is compounded when you're fetching data in individual components without coordination. Component A fetches data. Component B fetches overlapping data. Component C fetches related data. None of them know about each other. You end up with waterfall requests—A loads, triggers B to load, which triggers C to load—when you could have fetched all the necessary data in parallel or in a single request. Or worse, you have multiple components fetching the same data because you didn't implement any caching or deduplication.

The solution isn't in React—it's in your data layer. You need proper API design that returns only what you need. You need a data fetching strategy that coordinates requests and caches results. Libraries like React Query, SWR, or Apollo Client solve a lot of these problems, but only if you use them thoughtfully. I've seen developers use these libraries and still over-fetch constantly because they didn't design their queries properly or because they're invalidating caches too aggressively.

Poor memoization strategy is another silent killer. And by "poor strategy," I don't just mean "not memoizing enough"—I mean having no coherent strategy at all. Developers either memoize nothing and suffer through unnecessary re-renders, or they memoize everything "just in case" and end up with code that's harder to read, harder to maintain, and sometimes actually slower because they're paying the memoization overhead for things that didn't need it.

Here's the thing about memoization: it's not free. Every useMemo, useCallback, and React.memo call has overhead. You're trading CPU cycles spent on memoization checks against CPU cycles spent on re-rendering or recomputing. For simple components and cheap calculations, the memoization overhead can actually be more expensive than just doing the work again. I've profiled applications where aggressive memoization made things slower because developers were memoizing simple arithmetic or shallow component renders that would have been faster to just recompute.

The right strategy is to memoize selectively based on actual measurement. Profile your application, identify the expensive operations, and memoize those. Don't memoize preemptively. Don't wrap every function in useCallback "because it's a dependency." Don't throw React.memo on every component "for optimization." Understand what's actually expensive in your application and optimize that specifically.

Expensive calculations inside render is such an obvious mistake when you see it, but it's incredibly common. I've seen render functions that do complex data transformations on large arrays. Render functions that perform expensive regular expression operations on every render. Render functions that recursively traverse object trees or do distance calculations or parse dates in loops. All of this work happening on every single render, even when none of the relevant data has changed.

The insidious part is that these expensive calculations often start out small and innocent. You have a simple sort or filter operation on a small array, and it's fine. Then your data set grows. Or you add another transformation. Or you nest these operations. Before you know it, you're spending 50 milliseconds on calculations in your render function, and your UI feels sluggish because React can't commit the update until your render function finishes running.

This is where useMemo actually shines—not for memoizing components or callbacks, but for memoizing expensive derived state. If you have a calculation that depends on props or state but doesn't need to run on every render, memoize it. If you're transforming data structures in your render body, that's a code smell. Pull it out, memoize it, and only recompute when the dependencies actually change.

Bad list rendering is another performance killer that deserves way more attention than it gets. Rendering lists efficiently in React requires understanding a few key concepts that many developers ignore or misunderstand. First, keys. Everyone knows you need keys, but not everyone knows that keys need to be stable and unique. Using array indices as keys is fine if your list never reorders and items are never added or removed from anywhere but the end. Otherwise, you're going to confuse React's reconciliation and cause unnecessary DOM operations.

But keys are just the start. The bigger issue is what you're rendering in each list item. If your list items are complex components that take many props, and those props change frequently, you're going to render your entire list constantly. This is especially brutal for long lists—imagine a list of 500 items where each item re-renders on every parent update because you're passing down inline functions or derived data that gets recreated on every render.

For very long lists, you need virtualization—rendering only the items that are currently visible and recycling DOM nodes as the user scrolls. Libraries like react-window and react-virtualized exist for this reason. But even for moderately sized lists, you need to be thoughtful about minimizing list item re-renders through proper memoization, stable prop references, and component design that limits what data each item depends on.

What Good React Architecture Actually Looks Like

Let me paint you a picture of what good React architecture actually looks like in practice. This isn't about following some dogmatic pattern or religiously applying a specific state management library. Good architecture is about understanding the principles of component design, state management, and data flow, and applying them thoughtfully to your specific application's needs.

Component responsibility boundaries are the foundation of good React architecture. Each component should have a single, clear purpose. Not a single line of code—a single conceptual responsibility. A button component renders a button. A form component manages form state and validation. A list component renders a list. A data fetching component fetches data and passes it to presentational components. When a component starts doing multiple things, when you struggle to name it clearly, when you find yourself reaching for "and" in the component name—that's a signal to split it up.

The way I think about component boundaries is to ask: if this piece of state changes, what needs to re-render? If the answer is "just this small part of the UI," then that state should live in a component as close to that UI as possible. If the answer is "several different parts of the UI that aren't directly related," then you might need lifted state or a more sophisticated state management solution. But if the answer is "everything, even though most of it doesn't care," then your component boundaries are wrong.

Good component design also means thinking about what data a component owns versus what data it receives. A component should own state that's entirely internal to its operation—form field values, open/closed states for dropdowns, animation states, things like that. A component should receive data through props when that data is determined by parent components or external state. Mixing these concerns—having components that both own critical state and receive critical state—leads to confusion and bugs.

Smart versus dumb components is an older pattern that fell out of fashion for a while, but the underlying principle is still incredibly valuable. You want a clear separation between components that contain logic, manage state, and handle side effects (smart components, sometimes called container components) and components that just receive data through props and render UI (dumb components, sometimes called presentational components).

This separation gives you several huge benefits. First, your presentational components become incredibly easy to test—you just pass in props and verify the output. Second, they become highly reusable—the same presentational component can be used with different data sources and in different contexts. Third, your application becomes much easier to reason about because you can look at a component and immediately know whether it's going to do anything surprising or if it's just going to render what you give it.

In practice, this means you might have a UserProfile component that fetches user data, manages editing state, and handles save operations, and then it renders a UserProfileView component that just takes that data as props and displays it. The smart component is ugly and imperative and full of business logic. The presentational component is clean and declarative and easy to understand. You've separated concerns, and your architecture is better for it.

State colocation is one of those principles that sounds simple but has profound implications. State should live as close as possible to where it's used. If only one component needs a piece of state, that state should live in that component. If several sibling components need to share state, it should live in their nearest common ancestor. If components across your entire application need access to state, then and only then should it be in global state.

The reason this matters so much for performance is that React's re-rendering is based on state changes. When state changes, React re-renders the component that owns that state and all of its descendants. If you lift state higher than necessary, you're re-rendering a bigger portion of your tree than you need to. If you put state in a global store when it's only used in one small section of your UI, you're paying the coordination and subscription overhead for no benefit.

I've reviewed applications where almost all state was lifted to the root component or put in Redux, and the developers justified this by saying "we might need it somewhere else later" or "it's easier to have all state in one place." But when I asked them to identify which state was actually shared across multiple parts of the UI, it was maybe 10% of what they had lifted. The other 90% was causing unnecessary re-renders and making the application harder to understand.

Composition over configuration is another principle that dramatically improves React architecture. Instead of creating configurable components with lots of props and conditional rendering logic, create simple, focused components and compose them together to build more complex UIs. Instead of a Button component with props for isLoading, isDisabled, hasIcon, iconPosition, variant, size, and ten other configuration options, create simple composable pieces and let the consuming code combine them as needed.

Composition leads to more flexible and maintainable code because you're not trying to anticipate every possible use case in a single component. You're creating building blocks that can be combined in ways you might not have predicted. It also tends to lead to better performance because simpler components with fewer props are easier for React to optimize and less likely to re-render unnecessarily.

A concrete example: instead of a Card component that has props for headerContent, bodyContent, footerContent, isCollapsible, isExpanded, and various styling options, create Card, CardHeader, CardBody, and CardFooter components that can be composed together. The parent code becomes more verbose, but it's also more flexible and clearer. Each piece does one thing well, and performance characteristics are more predictable.

How to Actually Fix Performance Problems

Let's get practical. You've identified that your React application has performance problems. You've measured, you've profiled, and you know where the bottlenecks are. How do you actually fix them? And just as importantly, how do you know when to fix them and when to leave well enough alone?

When to optimize and when not to is the first question you need to answer, and it's not always obvious. The conventional wisdom is "don't optimize prematurely," which is good advice but not very actionable. Here's my rule: optimize when you have evidence of a user-facing performance problem and you've identified the cause through profiling. Don't optimize based on assumptions about what might be slow. Don't optimize because a component "feels" like it might re-render too much. Don't optimize because you read a blog post about React performance and now you're worried.

Performance optimization has costs. It makes your code more complex. It makes it harder for other developers (including future you) to understand what's happening. It introduces potential bugs when your memoization dependencies are wrong or your optimization assumptions become invalid. You should only pay these costs when you're getting clear benefits in return, and the only way to know that is through measurement.

When you do optimize, start with the biggest problems first. If you have a component that takes 200ms to render and another that takes 5ms, fix the 200ms one first. This sounds obvious, but I've seen developers spend days optimizing small issues while ignoring the elephant in the room. Profile your application under realistic conditions—realistic data sizes, realistic user interactions, realistic network conditions—and fix the problems that actually impact users.

How to think about useMemo, useCallback, and React.memo is crucial because these are the main tools React gives you for performance optimization, and they're widely misunderstood. These tools are not magic. They're trade-offs. They have overhead. They add complexity. They should be used judiciously, not reflexively.

useMemo is for expensive calculations. If you're doing complex data transformations, sorting large arrays, performing recursive operations, or calculating derived state that's expensive to compute, useMemo can help. It caches the result and only recomputes when dependencies change. But if your calculation is simple—basic arithmetic, accessing object properties, simple array operations on small arrays—useMemo's overhead might exceed the cost of just doing the calculation again.

useCallback is for stable function references. This is useful when you're passing callbacks to child components that are wrapped in React.memo or when function identity matters for dependency arrays. But here's the thing: in many cases, creating a new function on each render is completely fine. Functions are cheap. If your child component isn't memoized or the render is cheap anyway, useCallback adds overhead for no benefit.

React.memo is for preventing component re-renders when props haven't changed. It's great for expensive components that receive the same props frequently, like list items in a long list or complex visualizations that are expensive to render. But for simple components—a button, a text label, a simple div with a few children—the memo check might be more expensive than just re-rendering. Measure first.

The pattern I follow is: write code without memoization first, profile to identify actual performance problems, then add memoization surgically to fix those specific problems. Don't memoize preemptively. Don't wrap everything in useMemo and useCallback "just to be safe." Start simple, measure, optimize what matters.

Measuring before optimizing can't be stressed enough. React DevTools has an excellent profiler that shows you exactly what's rendering, how long it takes, and why it rendered. Use it. Record a profile of a slow interaction. Look at the flame graph. Identify which components are taking the most time. Look at what caused them to render—was it a props change, a state change, a context update? Once you know what's slow and why, you can fix it intelligently.

Network performance matters too. Use your browser's network tab. Are you making too many requests? Are your requests too slow? Are you fetching data you don't need? Are you triggering waterfalls? Sometimes what feels like a React performance problem is actually a data fetching problem. You can optimize your React code all day, but if you're waiting 2 seconds for an API response, your app will still feel slow.

Real user monitoring is valuable for production applications. Tools that track actual user experience metrics—First Contentful Paint, Time to Interactive, interaction latency—give you insight into what real users experience, not just what you see in your development environment. Sometimes performance problems only manifest at scale, with slow devices, or with poor network conditions. Synthetic benchmarks in your dev environment won't catch those.

Bad Architecture vs Good Architecture: A Real Comparison

Let me contrast what bad versus good architecture looks like in practice, with specific examples of how architectural choices cascade into performance problems or smooth user experiences.

Bad architecture: You're building a dashboard with multiple widgets that display different kinds of data. You decide to manage all the state in a single component at the root of the dashboard. This root component fetches all the data for all widgets on mount. It stores everything—data for each widget, loading states, error states, filter selections, sort orders, pagination state—in a massive state object. Each widget is a child component that receives its slice of data through props that are derived in the root component's render function. When any piece of state changes—a user changes a filter, data comes back from an API, a widget refreshes—the entire dashboard re-renders. All widgets re-render, even though only one widget's data changed. The derived data calculations run again for all widgets. The entire component tree gets processed. The UI feels sluggish because every interaction causes a large re-render cycle.

Good architecture: The same dashboard, but structured differently. Each widget is a self-contained component that manages its own data fetching, loading states, and error handling. The root dashboard component just renders the widgets and provides shared context like the current user or theme. Each widget only re-renders when its own state changes. When one widget fetches new data, the others are unaffected. Filtering a widget only re-renders that widget. The dashboard is fast because work is localized—only the part of the UI that needs to update actually updates.

Bad architecture: You have a form with twenty fields. Every field is controlled—you have state for each field value. You lift all this state to the form's parent component. You have an onChange handler that updates state on every keystroke. Because all the state is in the parent, every keystroke triggers a re-render of the entire form and all twenty fields. Each field re-renders because it receives new props on every update, even if its own value didn't change. The form feels laggy because you're processing twenty field components on every keystroke. You try to fix it by wrapping each field in React.memo, but that doesn't help much because the field components are receiving new onChange handlers on every render (they're defined inline in the parent's render function). You add useCallback to stabilize the handlers, which helps some, but the form is still slow because you're fundamentally doing too much work.

Good architecture: Each form field is its own component with its own internal state. Fields are uncontrolled by default—they manage their own values until form submission. When you need to validate or submit the form, you read the values from the fields. This way, typing in one field only re-renders that field. The rest of the form is unaffected. The form feels instant because each interaction is localized to a single component. For fields that need to interact with each other (like a "password confirmation" field that needs to validate against the "password" field), you lift just that shared state to the nearest common ancestor, not all state to the form root.

Bad architecture: You need to share some user data across multiple parts of your application. You create a UserContext that includes everything about the user—profile data, preferences, recently viewed items, shopping cart, notification settings, UI state like which modals are open, everything. You wrap your entire application in this UserContext provider. Now you have dozens of components throughout your app consuming this context with useContext(UserContext). When any piece of the user data updates—the user changes their theme preference, adds an item to their cart, dismisses a notification—every single component consuming UserContext re-renders. A user typing in a search box that updates a "recent searches" array in the UserContext causes your navigation bar, your sidebar, your footer, and twenty other components to re-render even though they don't care about recent searches. You try to fix this by splitting the context into smaller pieces, but now you have eight different context providers nested at the root, and you're not sure which components should consume which contexts. The performance is still bad because your context values aren't stable—you're creating new objects on every render, which causes all consumers to re-render even when the actual data hasn't changed.

Good architecture: You create multiple, focused context providers. AuthContext for authentication state (user ID, auth token, login/logout functions). ThemeContext for theme preferences. CartContext for shopping cart state. Each context has a single, well-defined purpose. Context values are stable—you use useMemo to ensure that the context value object only changes when the actual data inside it changes. Components only consume the contexts they actually need. Your navigation bar consumes AuthContext and ThemeContext but not CartContext. Your product list doesn't consume any contexts at all—it receives data through props. When cart data changes, only components that care about the cart re-render. The rest of your application is unaffected.

Bad architecture: You're building a data table with sorting, filtering, and pagination. All the logic lives in one giant component. The component maintains state for the current page, sort column, sort direction, filter values, and the data itself. Every time any of these change, the entire table re-renders. You're rendering all rows in the dataset, even though only 20 are visible at a time—you're just hiding the others with CSS. The row rendering logic is complex, with lots of conditional formatting based on cell values, and it's all inline in the main component's render function. The component is 800 lines long. Sorting the table feels slow because you're re-rendering potentially thousands of hidden rows. Changing filters is slow because you're running the filter logic on the entire dataset and then re-rendering everything. The code is hard to modify because all the logic is tangled together.

Good architecture: The table is composed of several focused components. A Table component handles layout. A TableHeader component handles the column headers and sorting UI. A TableBody component handles rendering visible rows. A useTableData custom hook handles the data fetching, filtering, sorting, and pagination logic. The hook returns only the data for the current page, already filtered and sorted. Row components are simple, memoized presentational components. When you sort, the hook recalculates which rows should be visible, and only those rows get rendered. The table only renders what's actually visible on screen—20 rows, not 2000. Each piece of the system has a clear responsibility. The code is maintainable because you can modify the filtering logic without touching the rendering code, or update how rows display without touching the data management logic.

Bad architecture: You have a complex workflow with multiple steps—a checkout process, a multi-step form, a wizard interface. You manage all the state for all steps in a single reducer at the root. Every step is a separate component, but they all receive the entire state object as props. You pass down dispatch functions to allow steps to update state. As users move through the workflow, you keep all previous steps mounted in the DOM (just hidden with display: none) because you need to preserve their state. The entire workflow re-renders whenever state changes, even though only one step is visible at a time. You have conditional logic scattered throughout to handle different workflow states. Some steps have their own internal state that conflicts with the centralized state, leading to bugs where the UI gets out of sync.

Good architecture: Each step is a self-contained component that manages its own internal state. A workflow manager component handles navigation between steps and maintains only the minimal shared state (current step index, data that needs to persist across steps). When you navigate to a step, that step mounts, initializes its state from any persisted data, and operates independently. When the step completes, it calls a callback with its final data, which the workflow manager stores. Previous steps unmount—they're not kept in the DOM. This keeps memory usage down and ensures only the current step re-renders when its state changes. The workflow manager doesn't know or care about the internal workings of each step; it just coordinates the flow.

The Truth Developers Don't Want to Hear

Here's where I'm going to be blunt, because I think this needs to be said: blaming React for performance problems is often intellectual laziness. It's easier to say "React is slow" than to admit "I structured this poorly" or "I don't fully understand how React works" or "I made architectural decisions that seemed fine at the time but don't scale."

I get it. I really do. When you're under pressure to ship features, when you're working with tight deadlines, when you're learning React while building production applications, you make mistakes. You take shortcuts. You do things the quick way instead of the right way. You think "I'll refactor this later" but later never comes because there's always another feature, another deadline, another fire to put out. Before you know it, you have an application with architectural problems baked into its foundation, and those problems are now incredibly difficult to fix because so much code depends on the current structure.

But here's the thing: acknowledging this is the first step to actually getting better. Every senior React developer I know has built terrible React applications. We've all created components that were too big, state that was too global, re-renders that were too frequent. We've all looked at our own code six months later and wondered what we were thinking. The difference between a developer who grows and one who stagnates is whether they learn from these mistakes or just keep blaming the tools.

React gives you an enormous amount of rope to hang yourself with. It's not opinionated enough to prevent you from making bad architectural decisions. It won't stop you from putting everything in global state. It won't force you to split up your 1000-line component. It won't automatically optimize away your unnecessary re-renders. This is both a strength and a weakness. The flexibility that makes React powerful for building complex UIs also makes it easy to build poorly-performing UIs if you don't understand what you're doing.

Some frameworks are more opinionated and thus harder to misuse. Svelte compiles away a lot of potential performance problems. Solid.js has fine-grained reactivity that makes unnecessary re-renders much less common. Angular has strong conventions about how to structure applications. These frameworks make certain classes of mistakes harder to make, and that's genuinely valuable, especially for teams that don't have deep expertise in frontend performance.

But switching frameworks isn't a magic solution. If you don't understand why your React application is slow, you'll probably build a slow Svelte application too, just with different performance characteristics and different footguns. The fundamental principles of good frontend architecture—component design, state management, data flow, performance-conscious rendering—apply regardless of which framework you use. A developer who doesn't understand these principles will struggle with any framework.

I've seen teams rewrite applications from React to something else, and you know what happens? Sometimes they get better performance, because they're effectively doing a full architectural redesign and they learn from their mistakes. Sometimes they get worse performance, because they bring their bad habits to the new framework. And sometimes they get the same performance, because the framework was never the bottleneck—their API design, their data fetching strategy, their component architecture, those were the real problems, and those problems follow you regardless of which view layer you use.

React's performance characteristics are well-understood. The rendering model is documented. The reconciliation algorithm is explained. The profiling tools exist. The best practices are written down, discussed in conferences, debated in blog posts. If your React application is slow, the information you need to fix it is available. What's required is the intellectual honesty to diagnose the real problem instead of blaming the framework, and the discipline to actually refactor your architecture instead of just slapping useMemo on everything and hoping it gets better.

I say this with empathy, not judgment, because I've been there. I've been the developer who thought Redux would solve all my state management problems, only to discover I'd just moved the complexity to a different place. I've been the developer who wrapped every component in React.memo because I read that it improves performance, only to discover I'd made my code harder to maintain for negligible benefit. I've been the developer who blamed React's re-rendering model for my application's slowness when the real problem was that I was fetching data inefficiently and calculating expensive derived state on every render.

The path to building fast React applications isn't about learning secret optimization tricks or advanced techniques that only senior developers know. It's about understanding the fundamentals deeply, thinking carefully about architecture before you build, measuring instead of guessing, and being willing to refactor when you realize your initial approach doesn't scale. It's about being honest about what you don't know and taking the time to learn it properly instead of cargo-culting patterns you don't understand.

Closing: React Is Not the Problem

So let's bring this all back to where we started. React is not slow. React is a tool, and like any tool, its performance depends on how you use it. A hammer isn't defective because you tried to use it to cut wood. A car isn't slow because you left the parking brake on. And React isn't slow because you structured your application in a way that causes excessive re-renders, poor data flow, and architectural complexity that works against React's design.

The React applications you've used that feel fast—and there are plenty of them, from complex enterprise applications to consumer products used by millions—aren't fast because their developers discovered some secret optimization technique. They're fast because they were built with solid architectural principles: components with clear responsibilities, state that lives at the appropriate level, data flow that's predictable and efficient, and optimization applied judiciously where measurement shows it matters.

When you encounter a performance problem in a React application, the question shouldn't be "Is React the right choice?" The question should be "What architectural decision led to this problem?" Is state lifted too high? Are components doing too much? Is data being fetched inefficiently? Are expensive calculations running on every render? Is the component tree structure causing excessive re-renders? These are the real questions, and these are the questions that have actionable answers.

Building fast React applications is a skill, and like any skill, it requires learning, practice, and sometimes painful mistakes. You have to build something slow to really understand why it's slow. You have to debug performance problems to internalize how React's rendering model works. You have to refactor bad architecture to appreciate good architecture. This learning process is frustrating, but it's also how you get better.

The good news is that React gives you all the tools you need to build performant applications. The reconciliation algorithm is efficient. The hooks API gives you fine-grained control over rendering and side effects. The profiling tools let you see exactly what's happening. The component model encourages good architectural patterns if you're thoughtful about how you use it. React's not perfect—no framework is—but it's more than capable of handling complex, performant UIs when used well.

So the next time you're tempted to blame React for performance problems, take a step back. Profile your application. Identify what's actually slow. Understand why it's slow. Then fix your architecture. Split up that massive component. Move that state closer to where it's used. Stop re-rendering components that don't need to update. Optimize your data fetching. Apply memoization where it actually matters. Make conscious, measured architectural decisions instead of reaching for patterns because you saw them in a tutorial.

React is not slow. Your architecture is. And the beautiful thing about architecture is that you can change it. It takes work, it takes learning, it takes discipline, but you can do it. You can build fast React applications. Millions of developers have done it before you, and you can too.

The framework isn't the limitation. Your understanding and application of good architectural principles is the limitation. Invest in deepening that understanding, building that skill, developing that discipline. Measure, learn, refactor, improve. That's the path to building React applications that perform well.

React is a powerful, flexible, and yes, fast tool for building user interfaces. Use it well.

Hanzla BaigFollow

Front-end dev & Founder at TheBitForge. I ship clean UI with HTML, CSS, JS, and a splash of Java—building fast, accessible web products with old-school craft and a future-first mindset.

Thanks for reading! 🙏🏻 I hope you found this useful ✅ Please react and follow for more 😍 Made with 💙 by Hanzla Baig

The Death of Vanilla JavaScript (And Why It's Actually Stronger Than Ever)

Hanzla Baig — Wed, 14 Jan 2026 17:18:57 +0000

Liquid syntax error: Tag '{% embed https://roshansfitnesszone.blogspot.com/ %}' was not properly terminated with regexp: /\%\}/

DEV Community: Hanzla Baig

The Coding Interview Is Dead. What Should Replace It?

Hanzla BaigFollow

What's Actually Broken

The Memorization Trap

Unrealistic by Design

Stress as a Feature (Not a Bug)

The Randomness Problem

The Industry Reality

Who It Hurts Most

Junior Developers

Self-Taught Engineers

Experienced Engineers

What Should Replace It

Take-Home Projects (Done Right)

Code Review Discussions

Real-World Debugging

Portfolio-Based Hiring

What Good Interviews Actually Look Like

The Closing Argument

Hanzla BaigFollow

Vibe Coding: Are We Building Faster or Just Building Bigger Messes?

Hanzla BaigFollow

Where It All Started

The Numbers Are Wild (In Both Directions)

The Productivity Paradox Nobody Wants To Talk About

The Vibe Coding Hangover

The Security Problem Is Not Theoretical Anymore

What It Is Doing To Junior Developers

Where Vibe Coding Is Genuinely Excellent

The Right Way To Think About It

The Bottom Line

Hanzla BaigFollow

We Broke Our App Into 50 Microservices. Then We Put It Back Together — And Cut Costs by 90%

Hanzla BaigFollow

The Microservices Dream vs. The Microservices Reality

What Microservices Actually Promise (And Why Teams Buy In)

The Hidden Costs Nobody Puts In The Slide Deck

1. Network Overhead and Latency

2. Distributed Systems Complexity

3. Observability and Debugging Complexity

4. Infrastructure and Cloud Cost

5. Cognitive and Operational Load

The Core Mistake: Copying Netflix Without Having Netflix's Problems

How To Know If Your Microservices Are Hurting You

The Modular Monolith: The Architecture The Industry Stopped Talking About

What a Modular Monolith Looks Like in Practice

Which Services Actually Deserve To Be Separate

A Framework For Making The Architecture Decision

The Performance Reality

What The Real Cost Comparison Looks Like

What "Moving Back" Actually Requires

Microservices vs Modular Monolith: Side-by-Side Comparison

The Broader Lesson About Architecture Decisions

Key Takeaways

Hanzla BaigFollow

🤔 Questions Only Developers Will Lose Sleep Over (And Secretly Love Answering)

Introduction: Welcome to the Developer Brain

🐛 Question 1: If a Bug Is Fixed But No One Writes a Test for It, Did the Bug Ever Really Exist?

💻 Question 2: Is It Still "Clean Code" If It Works But You Can't Explain It the Next Morning?

🔢 Question 3: Are null, undefined, 0, "", and false the Same Thing — or 5 Different Ways to Ruin Your Day?

🤯 Question 4: If You Google the Same Stack Overflow Answer 5 Times, Is It Time to Just Memorize It?

🚀 Question 5: Is "Deploying to Production" the Same as "Sending a Prayer to the Cloud"?

⌨️ Question 6: When You Rename a Variable from data to theData — Is That Refactoring?

🧪 Question 7: Are Unit Tests Just Very Angry Comments That Run Automatically?

🕰️ Question 8: Does "It'll Take 2 Hours" Ever Actually Mean 2 Hours?

🌐 Question 9: If the Frontend Works AND the Backend Works, But Together They Don't — Whose Fault Is It?

🤖 Question 10: When You Use AI to Write Code You Don't Understand — Are You a Developer or a QA Engineer?

🔄 Question 11: Is git commit -m "fix" an Acceptable Commit Message?

💡 Question 12: Is Dark Mode a Preference or a Personality Trait?

☕ Question 13: How Many Cups of Coffee Does It Take to Write One Function?

🔥 The Ultimate Developer Debates: Pick Your Side

Debate 1: Tabs vs. Spaces

Debate 2: === vs. == in JavaScript

Debate 3: Semicolons vs. No Semicolons in JavaScript

Debate 4: camelCase vs. snake_case

Debate 5: MongoDB vs. PostgreSQL

🧠 Bonus Round: Questions With No Good Answers

🏁 The Final Question: After Everything — Why Do We Keep Coding?

The Life of a Developer in One Loop ❤

🔢 Question 3: Are `null`, `undefined`, `0`, `""`, and `false` the Same Thing — or 5 Different Ways to Ruin Your Day?

⌨️ Question 6: When You Rename a Variable from `data` to `theData` — Is That Refactoring?

🔄 Question 11: Is `git commit -m "fix"` an Acceptable Commit Message?

Debate 2: `===` vs. `==` in JavaScript