Skip to main content
HashnodeCoding DropletsCoding Droplets

Command Palette

Search for a command to run...

About Coding Droplets

Coding Droplets is a collaborative .NET publication for developers who want to build, launch and scale real products with .NET.

We don't write code snippets for the sake of it. Every article, video and repository is shaped by the same question: does this actually help someone ship better .NET software? If the answer is no, it doesn't go out.

Why Coding Droplets exists

Most .NET content online stops at "hello world". Real production teams need the next ten miles — the architecture decisions, the edge cases, the failure modes, the trade-offs nobody documents until they get burned by them in production.

Coding Droplets was built to close that gap. The publication is grounded in years of combined hands-on .NET production experience, and everything shared here comes from systems that have been built, shipped and operated at real scale.

Our vision

The .NET ecosystem evolves fast — frameworks, patterns, cloud platforms and tooling all move at the same time. Coding Droplets exists to be a steady, opinionated reference point in that motion: a publication where developers can come for clear thinking, working code and honest trade-offs, and leave with something they can ship on Monday.

Our larger goal is to grow into the default .NET resource teams and individual engineers turn to — for guides, courses, reference repositories and the kind of practical depth that's hard to find anywhere else.

What you'll find here

Coding Droplets publishes across five surfaces, each tuned for a different way of learning:

  • The Blog — Long-form articles published almost daily, covering ASP.NET Core, EF Core, CQRS, Clean Architecture, Blazor, microservices, performance, security, observability, and the design decisions behind them.
  • Courses — Structured, project-based courses for developers who want to go deeper than a blog post can take them.
  • YouTube — Video walkthroughs, tutorials and live builds for visual learners.
  • GitHub — Free, open-source reference repositories you can clone, study and ship from — covering ASP.NET Core, EF Core, CQRS, Clean Architecture and more.
  • Patreon — Early access, exclusive content, and a way to directly support the work.

Who this is for

Coding Droplets is written for:

  • .NET developers ready to move past tutorials and into production-grade code.
  • Backend and full-stack engineers building APIs, services and platforms on ASP.NET Core.
  • Tech leads and architects making real decisions about persistence, messaging, security and resilience.
  • Teams and individuals standardising the way they design, ship and scale .NET applications.

If you're serious about moving from code snippets to production outcomes, you'll feel at home here.

What we focus on

A non-exhaustive list of topics we publish on regularly:

  • ASP.NET Core — Web APIs, minimal APIs, middleware, authentication, authorization
  • Entity Framework Core — modelling, performance, migrations, value objects, owned entities
  • Architecture — Clean Architecture, Domain-Driven Design, CQRS, vertical slices
  • Distributed systems — microservices, messaging, resilience, circuit breakers, idempotency
  • Cloud & infrastructure — Azure, object storage, containers, deployment
  • Security — OWASP API risks, authentication patterns, secret handling
  • Performance — caching, profiling, memory diagnostics, async patterns

How we work

Coding Droplets is a collaborative initiative, not a one-person blog. The work is driven by combined effort and shared expertise across writing, engineering, and review:

  • Hands-on engineering. Every topic starts in a real codebase, not a documentation tab.
  • Peer review. Articles and reference repositories are checked against production constraints before publishing.
  • Reader feedback. Corrections, questions and topic suggestions from the community shape what gets covered next.
  • Open source. Working code lives publicly on GitHub so readers can verify, extend and reuse it.

Editorial principles

A few rules we hold ourselves to:

  1. Experience over theory. If we haven't shipped it or debugged it, we don't present it as production advice.
  2. Code that compiles. Every code sample is written to be runnable, not aspirational.
  3. Honest trade-offs. Every pattern has a cost. We name it.
  4. No filler. One tight article beats three padded ones.
  5. Evergreen first. We optimise for content that's still useful next year, not just this week.

Connect with Coding Droplets

You can find Coding Droplets across the web:

Get in touch

Questions, corrections, partnership ideas, or a topic you'd like covered next?

Email: codingdroplets@gmail.com

We read every message and reply to as many as we can.

Thanks for stopping by. If a single article, video or repository here helps you ship better .NET code, Coding Droplets has done its job.