Marcus Bennett, Editor | Coding Dunia

Marcus is the editorial byline behind Coding Dunia's React, TypeScript, and Node.js guides. We say that plainly on the About page too: it's a pen name, not a stand-in for a specific person's résumé. What isn't a pen name is the code, every sample published under this byline is run against the stated versions before it goes live.

The voice behind it has a shape worth naming. It belongs to a developer who started in 1995 on a Commodore 64, writing BASIC into a screen that forgot everything when the power went out. Then HTML and JavaScript when the web showed up and made the whole thing feel new again. Then years of PHP, which is where most of the working web actually lived for a long stretch that people now politely skip over. Then the JavaScript and TypeScript stack this site covers.

Thirty years on one platform isn't a qualification. It's a vantage point, and it mostly shows up here as impatience. When you have watched a framework arrive as the obvious future and leave as a migration cost, you get less interested in what a tool promises and more interested in what it will cost to get out of it later. That bias is deliberate, and you should read these guides knowing it's there.

Right now the focus is edge rendering and signal-based reactivity, the parts of the frontend stack that keep changing every time you get comfortable with the last approach.

What Gets Covered Under This Byline

React, TypeScript, and JavaScript patterns, tested against the versions stated in each guide
Frontend performance and Core Web Vitals
Tooling and build systems (bundlers, package managers, CI pipelines)
Migration guides that show the actual diff, not a toy example

How an Article Gets Tested Before It Ships

Every guide names the versions it was written against, and those aren't decorative. Before a post goes live, each code sample is pasted into a fresh project pinned to exactly those versions and run. If it's a React 19 guide, it runs on React 19.0, not on whatever happened to be installed. If a snippet only works because of a global left over from a previous example, that's a bug in the article, and it gets rewritten until the sample stands on its own.

What happens when a sample fails? It doesn't get "fixed in the text". The article waits. Usually the failure means the API changed between a release candidate and the final version, and the right move is to say so in the post, with the before and after. I'd rather publish three days late than publish a snippet that throws on line four.

What You Won't Find Under This Name

Code that was never run. A sample either executed on the stated versions or it isn't in the article.
Tool recommendations driven by affiliate payouts. Coding Dunia earns from ads, not from pushing a particular bundler or host.
Screenshots standing in for code. Everything is text you can copy, with the exact filename it belongs in.
"It depends" with no follow-up. When an answer depends on something, the article says on what, and gives the numbers.

Corrections and Updates

Frameworks move, and a guide that was right in March can be wrong by August. When a reader reports a sample that no longer runs, the article gets re-tested on the current release and updated with a visible revision date. Substantive changes are noted in the text rather than silently overwritten, because a reader who followed the old advice deserves to know what changed and why. Found something broken? The fastest route is a message on any of the channels below, with the article URL and the version you ran.

Elsewhere

Read more about Coding Dunia's editorial policy and how articles get tested on the About page.