Sitemap
.Net Code Chronicles

Unlocking the Power of .NET — Empowering Developers, One Byte at a Time!

Write for .Net Code Chronicles on Medium!

4 min readOct 25, 2025

--

Ship knowledge, not hot takes. If you love .NET and teaching devs real things with real code, you’re home.

Press enter or click to view image in full size

Hi, Everyone! I’m Aliaksandr Marozka, founder and courator this community. Welcome to .Net Code Chronicles — a community publication for practical, production‑minded engineering around .NET, C#, Blazor, ASP.NET Core, MAUI, EF Core, Azure, performance, testing, and beyond. We publish tutorials, case studies, deep dives, debugging war‑stories, and smart opinions backed by benchmarks, code, and receipts.

Why write here

  • Real reach, real devs. Your story appears in the publication feed, tag networks, and our socials/newsletters.
  • You own your voice. Keep your style; we help with structure, clarity, and headlines.
  • Earn on Medium. If you’re in the Medium Partner Program, your article can earn — we don’t take a cut.
  • Strong editorial help. We’ll tighten titles, TOCs, intros, and code formatting so your post lands.

TL;DR: Teach something real. Show the code. Add links. We’ll help it shine.

Submission paths

1) Already a Writer? (Fastest)

  1. Write your draft on Medium.
  2. Click ⋯ → Add to publication → select .Net Code Chronicles → Submit.

2) Need Writer access?

  1. Follow the publication: click Follow so your feed shows new calls and examples.
  2. Subscribe to the newsletter: we announce open topics, code style tips, and review queue updates.
  3. Say hi in the comments: drop “I’m in” under this page, or share 1–2 lines about what you want to write.
  4. Once your submission has been approved, we’ll add you as a Writer. From there, it’s publish‑time — can’t wait to see what you ship!
  5. Submit your first draft: ⋯ → Add to publication → .Net Code Chronicles → Submit and we’ll review.

Once we give you the green light, you’ll be added as a Writer. From there, publish away — we’ll help with titles, tags, and covers.

What we publish (and love)

  • Hands‑on tutorials (from “hello world” to advanced) with copy‑pasteable snippets.
  • Architecture & patterns: DDD, CQRS, Clean/Hex, microservices, messaging, gRPC, REST.
  • Web& UI: ASP.NET Core, Blazor (WASM/SSR/Hybrid), .NET MAUI.
  • Data & performance: EF Core, caching, BenchmarkDotNet, profiling, async pitfalls.
  • Cloud/DevOps: Azure, containers, GitHub Actions, CI/CD, Bicep/Terraform basics.
  • LLM/AI with .NET: Microsoft.Extensions.AI, GitHub Models, RAG, agents, MCP servers.
  • Case studies: migrations, outages, refactors, hard‑won lessons, postmortems.

What we don’t publish

  • Thin listicles with no code.
  • Copy/paste docs with minimal commentary.
  • Unattributed content or screenshots from paywalled sources.

Editorial checklist (use this before you submit)

  • Title: clear benefit + topic (avoid clickbait, use keywords devs actually search).
  • Intro: 3–6 sentences. Problem → promise → preview the sections.
  • Code: fenced blocks with language tags (csharp, bash, ```json). Keep lines < 100 chars.
  • Versioning: mention .NET/EF/ASP.NET versions used; note OS if relevant.
  • Repro: provide repo or Gist or a minimal snippet that compiles.
  • Screens: only where they add value; add alt text.
  • Links: docs, issues, PRs, benchmarks; prefer primary sources.
  • Conclusion: what changed for the reader? add next steps/refs.
  • Tags: add up to 5 (see recommendations below).

Voice & quality bar

We like friendly, concise, precise. Jargon is fine; explain it once. Prefer active voice, short paragraphs, real examples, and “why it matters” sections. AI tools are welcome for drafting/diagrams, but final prose must be human‑edited. If you used AI for code or text, sanity‑check, run, and disclose briefly if substantial.

Formatting guide (Medium specifics)

  • Use H2/H3 for structure. Avoid more than three heading levels.
  • Add a short TL;DR or Prereqs block if advanced.
  • Put commands in bash, responses in text, configs in json/yaml.
  • For large code, prefer a repo link and show the core slice in the post.
  • Use images at least 1200px wide; prefer SVG/PNG for diagrams.
  • Turn on Canonical link when cross‑posting from your blog (Editor → More settings → Advanced → Canonical link).

Topics / tags to use (pick up to 5)

Primary:

  • dotnet, csharp, aspnetcore, blazor, programming

Nice add‑ons (rotate as relevant):

  • software-engineering, web-development, maui, ef-core, azure, devops, performance, testing, microservices, architecture

Pitch template (copy/paste)

Title: Clear, benefit‑driven headline

Get Aliaksandr Marozka’s stories in your inbox

Join Medium for free to get updates from this writer.

Summary (2–3 sentences): Problem you solve + who it helps.

Outline:

  1. Context & pain
  2. Approach/architecture
  3. Step‑by‑step with code
  4. Gotchas/perf notes
  5. Wrap‑up + links

Assets: repo link(s), screenshots, diagrams.

Your bio (1–2 lines): What you do + links (GitHub/LinkedIn/site).

Review & publishing

  • We review for clarity, accuracy, originality, and fit.
  • We may adjust titles, headings, tags, and cover images for reach and consistency.
  • You retain ownership. If you’re in the Medium Partner Program, you keep earnings. We don’t offer direct payment.

Expect comments/suggestions right inside your draft. Quick iterations win.

Attribution, ethics, and legal

  • Credit images, diagrams, and third‑party code. Include licenses when needed.
  • No plagiarized or AI‑hallucinated content. Cite sources.
  • If republishing, set the canonical to the original.

Ready?

👉 Submit your draft to .Net Code Chronicles via Medium editor, or request Writer access using the form above.

Let’s teach the internet how to .NET — one byte at a time.

--

--

Written by Aliaksandr Marozka

Founder of AMarozka.Dev. Developer focused on Blazor, MAUI, ASP.NET Core, and Semantic Kernel. I ship fast, clean, and documented apps.

Published in .Net Code Chronicles

Unlocking the Power of .NET — Empowering Developers, One Byte at a Time!