About Coding Dunia: Practical Engineering Guides
Practical, in-depth guides on React, TypeScript, JavaScript, and modern frontend development. Written by engineers, for engineers.
Who Writes This
Marcus Bennett
Editor, Coding Dunia
Marcus is the editorial byline for Coding Dunia's React, TypeScript, and Node.js guides. It's a pen name, and we say so plainly rather than inventing a résumé for you to take on trust. What sits behind it is worth stating instead: the editorial voice belongs to a developer who has been shipping code since 1995, starting on a Commodore 64 in BASIC, moving to HTML and JavaScript when the web arrived, spending years in PHP, and landing on the JavaScript and TypeScript stack this site covers today.
Three decades on one platform is not a credential, but it is a vantage point. It means the guides here are written by someone who watched most of the frontend's promises arrive, and watched a good number of them leave again. That perspective shows up as scepticism about whichever approach is currently being described as inevitable.
Every sample is executed against the versions stated in the article before it publishes. See "How We Test and Update Content" below for the actual process.
What We Cover (and What We Don't)
Coding Dunia publishes practical, in-depth guides on React, TypeScript, JavaScript, CSS, Node.js, and the build tooling around them, npm/yarn/pnpm, Vite, bundlers, and CI pipelines. If it ships to a browser or runs on Node, it's in scope.
We don't cover backend languages outside the JS/TS ecosystem (no Go, Rust, or Python guides), mobile-native development, or general career advice unrelated to the day-to-day work of writing and shipping frontend code. Narrower scope means less filler, and it means we're not pretending to have hands-on opinions about stacks we don't actually run.
About This Domain
This domain was bought at auction in March 2026. Before that it belonged to a different Coding Dunia, an Android and Java tutorial site that ran from 2019. This site is not a continuation of that one, is not operated by the same people, and is not affiliated with it in any way.
We're saying this because that original project still exists elsewhere, and its authors deserve not to have a stranger's site inherit their name by accident. If you arrived here looking for their Android tutorials, this is not that site.
Everything published here dates from March 2026 onward. Nothing on this site predates the day the domain changed hands.
Editorial Policy
We don't accept sponsored articles. We don't take payment to recommend a library, tool, or framework. When a guide mentions a paid product (a hosted CI provider, a managed database, an editor), it's because we use it on our own projects, not because the vendor reached out. The same applies to comparison posts: ranking comes from hands-on testing, not vendor decks.
When we link to an external library or service, it's a plain link, no affiliate redirects, no UTM tags appended for tracking, no rel="sponsored" that we forgot to disclose. If we test paid tooling, the article says so explicitly and explains how we got access (free tier, trial, or paid out of pocket).
Errors get fixed publicly. If a reader catches something wrong, a deprecated API, a benchmark that no longer holds, a TypeScript version that changed behavior, we update the article and note the change at the top. Old guides aren't deleted; they're updated or marked outdated with a link to the current version.
How We Test and Update Content
Every code example runs. Before publication, snippets in TypeScript, React, and Node.js guides are executed against the versions stated in the article, and the versions are re-tested whenever a major release lands. Benchmarks are measured on hardware described in the article (typically an M-series MacBook Pro and a Linux CI runner) rather than copied from vendor marketing.
Time-sensitive guides (anything tied to specific library versions, framework releases, or year-dated comparisons) get a freshness review every quarter. The "Last updated" date on each post reflects the most recent factual review, not just a republish for SEO purposes.
Want to reach Marcus? DM the X or Bluesky account linked above rather than email, it's a lower-friction way to get a real response than a contact-form ticket that nobody reads until Monday. All editorial decisions are independent.