MagicAjax.NET publishes practical technical content for working .NET developers. We take the responsibility seriously: code on the internet is read for years, and bad code samples or stale advice cost real engineering hours. This page describes how we work.
Sourcing and authorship
- Every article is written by a named author. No anonymous posts, no "MagicAjax Editorial Team" bylines.
- Authors are practising .NET developers, architects, technical writers, or modernization specialists. We list their work on a dedicated authors page.
- For any opinion or review piece, the author's relevant experience and potential conflicts of interest are disclosed at the bottom of the article.
Review and fact-checking
- Peer technical review. Every article is reviewed by at least one editor or contributor with hands-on experience in the area before it ships.
- Code samples are tested. We run code in a representative environment — for legacy .NET pieces that means the actual framework version the article targets (1.1, 2.0, 4.x, etc.).
- Claims are sourced. Anything that isn't original analysis or first-hand experience is linked to its source — official Microsoft documentation, original author posts, archived SourceForge threads, etc.
Updates and corrections
- Articles are revisited periodically. Substantive technical updates are dated at the top of the article.
- If an article contains a factual error, we correct it as quickly as possible and add a short note explaining what changed.
- For breaking changes (an article's recommendation no longer holds because a tool was deprecated, a CVE was disclosed, etc.) we add a clearly marked banner at the top of the page.
Tone and editorial voice
- Technical, practical, occasionally nostalgic. We don't pretend the legacy .NET ecosystem isn't legacy — but we respect the engineers maintaining it.
- We avoid hype, vendor cheerleading, and "Top 10" listicles assembled without first-hand experience.
- Where we have opinions, we say so explicitly and explain the trade-offs rather than presenting opinion as fact.
What we will not do
- We will not publish articles that exist purely to rank in search engines, with no original technical insight.
- We will not silently sponsor articles. Sponsored content (if any) is clearly labelled and editorially separate.
- We will not let advertisers, vendors, or affiliate programs influence editorial coverage. See our Review Disclaimer for specifics.
Reader-driven corrections
If you spot a mistake, a stale code sample, or a broken assumption, email editorial @ magicajax.net. Reader corrections are one of the highest-quality signals we get and we treat them accordingly.