The Engineering Journal

Writing that matters.

Engineering insights, architectural decisions, and hard-won lessons from building real-world products — written from Dhaka, Bangladesh 🇧🇩. No tutorials. No filler. Production experience only.

28 Articles33 Topics65 Reads
✦ FeaturedCareer

Stop Asking for Permission: Why New Developers Need More Action and Less Validation

New developers spend months collecting opinions about what to learn, which language to choose, and which framework is best — time that could be spent building. Here's the hard truth about why endless validation-seeking delays real progress, and how to break the cycle.

May 28, 202613 min read9
Read article
001Jun 8, 2026

When Everything Goes Wrong: Why Great Teams Solve Problems Instead of Looking for Someone to Blame

Missed deadlines, production outages, failed deployments — every software team faces these. What separates great engineering cultures from dysfunctional ones is not the absence of failure, but what happens in the minutes and hours immediately after.

EngineeringLeadershipTeam Lead
13 min read7
002Jun 3, 2026

Startup Engineering Is Not Netflix Engineering

Many engineers enter startups with the mental model of Netflix, Google, or Stripe: dedicated QA teams, seasoned product managers, enterprise tooling, and months of runway for research. The startup has three developers, one founder, a few paying customers, and a deadline that passed two weeks ago. The expectations cannot be the same — and the gap between them is where many careers stall.

EngineeringCareerStartup
18 min read
003Jun 1, 2026

The Project Wasn't the Problem: When Poor Ownership Creates Technical Chaos

A project accumulates months of development, dozens of features, and significant complexity. Deadlines are missed. The client is dissatisfied. The project changes hands. And the original team spends more energy defending their decisions than helping the new team succeed. This pattern is common. It is also entirely avoidable.

EngineeringCareerLeadership
19 min read1
004Jun 1, 2026

Before n8n: How Developers Automated Workflows Long Before Visual Tools Existed

Many developers discover automation through visual workflow builders and assume that's where automation begins. In reality, developers have been automating complex business processes for decades using tools most modern engineers have never needed to touch. Here's the full history — and why understanding it still matters.

BackendNode.jsArchitecture
22 min read3
005Jun 1, 2026

Autopilot Didn't Replace Pilots: What AI Hype Gets Wrong About Human Expertise

Autopilot has existed in commercial aviation for decades. Airlines still employ highly trained pilots. The reason why is one of the clearest explanations I know for what AI will and won't do to software engineering — and why the most important skill you can develop right now is not prompting.

AIEngineeringCareer
14 min read
006Jun 1, 2026

Beyond the Paycheck: Why Great Engineers Care About More Than Just Money

There's a growing pattern in the software industry — engineers evaluating every task through a single lens: how much am I getting paid for this? This article explores why that mindset can become a ceiling, and what the engineers who build exceptional careers tend to focus on instead.

CareerEngineeringLeadership
12 min read
007Jun 1, 2026

Tutorial Addiction: Why Some Developers Keep Learning but Never Truly Grow

Many developers complete dozens of courses, collect certificates, and watch hundreds of hours of tutorials — and still freeze when asked to solve a real problem independently. This is not a knowledge problem. It is a practice problem. Here is the honest difference between learning about engineering and becoming an engineer.

CareerEngineeringMindset
18 min read
008Jun 1, 2026

The Most Dangerous Phrase in Software Engineering: 'I Know I'm Right'

Engineering maturity is not about being right more often. It is about updating your beliefs faster when the evidence says you should.

CareerEngineeringTeam Lead
14 min read5
009Jun 1, 2026

Clean Code Is Not a Personality

Some engineers can name every SOLID principle, write immaculate folder structures, lint every line, and apply DRY so aggressively the codebase has seventeen abstractions for sending an email. Their code looks impressive. Their products are often not. Aesthetic engineering and effective engineering are different disciplines, and confusing the one for the other is quietly capping a lot of careers.

EngineeringCareerMindset
13 min read2
010Jun 1, 2026

GraphQL Was the Wrong Lesson Learned From Facebook

Facebook built GraphQL to solve a real problem at genuine scale. The engineering community looked at the solution and adopted it without fully understanding the problem it was built for. Years later, many teams are maintaining schema complexity, DataLoader infrastructure, and N+1 query patterns that two well-designed REST endpoints would have prevented.

BackendAPIArchitecture
10 min read3
011Jun 1, 2026

Vibe Coding Will Make You a Worse Engineer

Vibe coding is real, it is productive, and for engineers who already understand what they are building, it is genuinely transformative. The problem is what happens when it becomes the primary way a developer learns to build software — before they ever develop the ability to build it without the AI.

AIEngineeringCareer
9 min read2
012Jun 1, 2026

Growth Begins When Excuses End: Taking Ownership of Your Career

It's easier to blame a bad manager, a toxic company, or an unfair industry than to ask the harder question — what could I have done differently? Real professional growth begins the moment you start treating setbacks as data rather than verdicts.

CareerLeadershipEngineering
8 min read2
013Jun 1, 2026

Nobody Talks About On-Call Until the Engineer Has Already Left

On-call culture is the most normalized form of professional self-destruction in the software industry. Engineers accept it because everyone accepts it. Organizations celebrate it because it is cheaper than fixing the systems that require it. And the conversation about whether it is sustainable almost never happens until the engineer is already gone.

EngineeringCareerLeadership
13 min read1
014Jun 1, 2026

Technical Debt Is a Lie We Tell Ourselves

Technical debt is the most overused, most misunderstood, and most conveniently abused concept in software engineering. It was invented to describe intentional trade-offs made with clear awareness. It has become the universal excuse for poor decisions, accumulated negligence, and the consequences of years of shipping without thinking. There is a difference between debt and damage, and most codebases have the second one.

EngineeringArchitectureCareer
12 min read3
015May 14, 2026

MVPs Don't Need Kubernetes: How Engineers Delay Products by Solving Problems They Don't Have

Many developers claim to be building an MVP. Their infrastructure tells a different story. After watching teams spend four months preparing to scale a product that had zero users, I want to make the case for something unfashionable: doing less on purpose.

ArchitectureEngineeringSystem Design
14 min read2
016May 1, 2026

Building for the World from Bangladesh: A Software Engineer's Global Perspective

Bangladesh's software engineering community is quiet on the global stage — not because of a lack of talent, but because we've been building for the world while underrepresenting ourselves in it. That's changing.

CareerBangladeshRemote Work
7 min read
017Apr 16, 2026

Will AI Replace Software Developers? A Practical Perspective

AI is more likely to become a force multiplier for capable engineers than a replacement for them. But 'capable' is doing real work in that sentence. Here's a practical perspective on what's actually changing, what isn't, and what it means for engineers building their careers right now.

AICareerEngineering
12 min read1
018Apr 2, 2026

Why Programming Fundamentals Still Matter in the Age of Frameworks and AI

I've watched engineers who skipped fundamentals hit the same invisible walls — at scale, in production, in architecture discussions — where frameworks stop providing answers and the underlying mental models are all that's left. Technologies change. Fundamentals compound.

EngineeringCareerSystem Design
12 min read1
019Mar 19, 2026

AI in Production Software: Benefits, Risks, and Realistic Expectations

There's a wide gap between an AI demo and a production AI system. After integrating AI capabilities into real products, I want to offer an engineer's honest account of where AI provides genuine value, where it introduces serious risk, and what production-grade AI operations actually look like.

AIBackendArchitecture
11 min read1
020Mar 5, 2026

Mistakes Most Junior Developers Make on Real Projects

The gap between writing code that works and being a productive member of a professional engineering team is not primarily technical. It's a collection of habits, instincts, and mindsets that take time and feedback to develop — unless someone names them clearly.

CareerEngineeringNode.js
13 min read2
021Feb 20, 2026

From Engineer to Team Lead: The Architecture Decisions That Actually Defined Our Backend

When you move from writing code to being responsible for the code other engineers write, the problems that matter change completely. Here's what I learned in my first six months as Team Lead at Root Devs.

ArchitectureTeam LeadNode.js
7 min read2
022Jan 22, 2026

Stop Choosing Technologies for Their Popularity

The right technology is the one that solves your problem with the lowest total cost of ownership — not the one dominating conference talks or LinkedIn posts. Technology decisions made for the wrong reasons have a way of revealing themselves in production at the worst possible time.

ArchitectureEngineeringSystem Design
11 min read2
023Jan 8, 2026

The Hidden Cost of Overengineering

The most expensive code I've written isn't the code that was buggy. It's the code that was too clever. After years of building and maintaining systems, I've come to believe that overengineering is a more common failure mode than underengineering — and far more insidious.

ArchitectureSystem DesignBackend
11 min read4
024Dec 10, 2025

The Most Important Decisions Happen Before Development Starts

Great software projects are usually decided before anyone opens their IDE. After leading projects at Root Devs that failed in planning and ones that succeeded because of it, I've come to believe that the most consequential engineering work isn't technical at all.

ArchitectureTeam LeadSystem Design
13 min read3
025Nov 14, 2025

Type-Safe APIs at Scale: How tRPC Eliminated an Entire Class of Bugs in Our TypeScript Backend

After shipping REST APIs for two years, our team at Root Devs made a deliberate bet on tRPC. Here's what the production reality looked like — the wins, the sharp edges, and the architecture patterns that survived contact with real traffic.

TypeScripttRPCNode.js
8 min read6
026Sep 2, 2025

Message Queues in Production: RabbitMQ vs Kafka for Node.js Backends

RabbitMQ and Kafka are both message queues in the same way a scalpel and a cleaver are both kitchen tools. Here's the production playbook for when to use each and how to operate them without incident.

Node.jsRabbitMQKafka
8 min read1
027Jun 18, 2025

Engineering an NFT Minting Bot: Race Conditions, Gas Wars, and Mempool Mechanics

Building an NFT minting bot taught me more about Ethereum's transaction mechanics than any course or documentation. This is the technical reality: the mempool game, the gas auction, and why Go beat Python on the critical path.

Web3EthereumGo
7 min read1
27 Articles