Skip to content

Citable: quotable in opinions and templates

Every source here meets all four criteria. The Since column shows the length of each record, and any independence concern, conflict of interest, or usage limit is in the source's section under Source notes.

The table lists 31 sources: 21 people and 10 publications.

id Kind Source Focus Since
aaron-stannard person Aaron Stannard: Aaronontheweb and his posts on the Petabridge blog OSS versioning and compatibility, property and performance testing, Akka.NET, checking agent code, agent skills 2010
andrew-lock person Andrew Lock: .NET Escapades ASP.NET Core internals, "Exploring .NET" per-release series 2016
ardalis person Steve Smith: ardalis.com and DevIQ Application architecture, Clean Architecture and DDD, design patterns and principles 2003
aspnet-blog publication ASP.NET Core category, .NET Blog ASP.NET Core announcements & deep-dives ~2004
avalonia-blog publication Avalonia UI blog and docs Cross-platform desktop UI, rendering ~2022
awesome-avalonia publication awesome-avalonia Curated Avalonia library/resource list 2020
awesome-blazor publication awesome-blazor Curated Blazor library/resource list 2018
awesome-dotnet publication awesome-dotnet Curated library/tool list 2014
code-with-mukesh person Mukesh Murugan: CodeWithMukesh Best-practice roundups, EF Core, benchmarks 2020
csharp-digest publication C# Digest Weekly newsletter aggregation ~2017
damien-bowden person Damien Bowden: damienbod ASP.NET Core security, OpenID Connect, BFF, passkeys 2013
derek-comartin person Derek Comartin: CodeOpinion Event-driven architecture, messaging, CQRS, DDD, modular monoliths 2012
dotnet-blog publication .NET Blog Everything .NET; canonical announcements ~2004
fsharp-weekly publication Sergey Tihon: F# Weekly Weekly F# link aggregation 2011
gerald-versluis person Gerald Versluis .NET MAUI, Xamarin, Blazor Hybrid 2015
james-montemagno person James Montemagno Xamarin/.NET MAUI, cross-platform mobile ~2012
jeremy-miller person Jeremy D. Miller: The Shade Tree Developer Messaging, event sourcing, persistence, dependency injection, testing long-lived codebases 2007
jetbrains-dotnet publication JetBrains .NET Blog C# language features, tooling ~2010s
jon-skeet person Jon Skeet's coding blog C# language semantics (records, generics, equality), date/time correctness, API design 2005
khalid person Khalid Abuhakmeh and his posts on the Duende blog Practical .NET, tooling; identity and OpenID Connect since 2025 ~2012
mark-seemann person Mark Seemann: ploeh blog Unit testing and TDD, dependency injection, type-driven and functional design in C#, code quality 2006
meziantou person Gérald Barré: Meziantou's blog C# language, analyzers, practical best practices ~2015
milan-jovanovic person Milan Jovanović Architecture, EF Core, CQRS, modular monoliths ~2020
ms-learn publication Microsoft Learn: .NET docs and Azure Architecture Center Official documentation, breaking changes, architecture e-books, cloud design patterns ~2016 (docs.microsoft.com era; MSDN before)
nicholas-blumhardt person Nicholas Blumhardt Structured logging (Serilog), DI/IoC (Autofac), tracing and diagnostics 2007
oskar-dudycz person Oskar Dudycz: Event-Driven.io Event sourcing, event-driven architecture, CQRS, vertical slices 2011
scott-wlaschin person Scott Wlaschin: F# for Fun and Profit F#, functional design, domain modelling 2012
shay-rojansky person Shay Rojansky .NET ↔ PostgreSQL mapping (Npgsql), EF Core internals 2014
stephen-cleary person Stephen Cleary Async and concurrency, SynchronizationContext and ConfigureAwait, cancellation 2008
stephen-toub person Stephen Toub (author page) Runtime/BCL performance, async internals ~2005
steve-gordon person Steve Gordon High-performance .NET, HttpClient, Span/ArrayPool ~2016

Source notes

aaron-stannard: Citable

Citable on his code-backed engineering posts and on the dotnet-skills he wrote himself, with a conflict on anything Petabridge sells.

  • Scope: Includes dotnet-skills, at v1.6.0 on 2026-09-16 with 37 skills and 6 subagents, which counts as authored documentation. It was watch-listed as a separate source on 2026-09-25 and merged into this ID the same day: the track record follows the person, so the repository's 2025-11-12 start doesn't hold it back.
  • Longevity: Writing on aaronstannard.com since 2010-05-14, and on the Petabridge blog since 2015. Together they show posts in every year from 2010 to 2026, and both are live, with posts on 2026-08-21 and 2026-09-23. The personal blog thins to a few posts a year from 2016 to 2019, with a longest gap of 347 days (2018-10-16 to 2019-09-28), and the Petabridge blog fills those years.
  • Depth: "Introducing NBench" starts from a throughput regression that unit tests couldn't catch. "Property Testing in C# with FsCheck" works a shuffle through to a shrunk counter-example. "Extend-Only Design" and "OSS Compatibility Standards" reason through schema and API evolution in code. His 2026 "Software 2.0" series is the most concrete .NET-specific writing found on verifying agent-written code. It reports failures as well as wins: "Planning and Verifying a Greenfield Project" records the agent writing tests that only "checked the 'has test coverage' box". dotnet-skills publishes evaluations, but they're small: 15 Akka.NET tasks, judged by the model that wrote the code.
  • Accuracy: Sound, with in-post corrections on record. ".NET Core is Boiling the Ocean" (2016) includes Miguel de Icaza's correction on WebAssembly and Mono. "The New Rules for Playing in Microsoft's Open Source Sandbox" (2020) includes an EDIT that retracts a misreading of David Fowler. dotnet-skills is weaker, because nothing compiles its samples: its own AGENTS.md says "There is no build system, tests, or compiled output." On 2026-09-25, against SDK 10.0.400, the testcontainers samples failed with CS0246 against Testcontainers 4.15.0, which their own Version="*" references restore, and a csharp-coding-standards value object failed with CS0111. The same skill's records hold collections, which breaks value equality, and with bypasses a validating record. The package examples pin xUnit v2, FluentAssertions 6 and 7, and Verify.Xunit, which pulls in xUnit v2. Six skills ship CI on dotnet-version: 9.0.x, with 22 mutable action tags and no SHA pins. Its release notes do record corrections, including "fabricated APIs, compile errors" in the OpenTelemetry skill, and guidance that wrongly called adding optional parameters binary-compatible.
  • Authorship: He made 68 of 82 dotnet-skills commits, but the skills that held up best under checking (aot-trimming, csharp-nullable-reference-types, and opentelementry-dotnet-instrumentation (sic)) came largely from Daniel Marbach, Mauro Servienti, and Tomasz Masternak of Particular Software. Their work isn't citable under this ID. Where one of them has a written track record, vet that person.
  • Conflict of interest: He's CEO of Petabridge, which sells Akka.NET support plans, consulting, and training, and sells the Phobos monitoring product through Sdkbin, a marketplace he built. Never cite him alone on adopting Akka.NET, the actor model, or Phobos. The same limit covers the six dotnet-skills skills and one subagent on Akka.NET. The posts on his workflow promote his free AI tooling (dotnet-skills, dotnet-slopwatch, and Netclaw), a milder conflict to flag where an opinion names one of them. On 2026-06-10, he removed FluentAssertions from Akka.NET on licensing grounds at a cost in convenience, which is evidence of critical distance.
  • Cite: The engineering posts. Much of the catalogue is essays on the .NET ecosystem, open-source economics, and running a business, which argue from experience, not evidence. Cite Petabridge posts for mechanism, not adoption: it's his company's blog, with Akka.NET release announcements beside the technical posts. Cite a dotnet-skills skill only after its history shows he wrote it, and only for the principle it states: never its package versions or CI pins, and never a code sample you haven't compiled against the citing file's targets.
andrew-lock: Citable

The standard reference for ASP.NET Core internals outside Microsoft, and author of ASP.NET Core in Action.

ardalis: Citable, Corroborate.

Marked for mixed depth, and conflicted on the architecture and data-access topics he'd be cited for.

  • Scope: The ID also covers DevIQ, published by NimblePros with Sarah Dutkiewicz, and the authored documentation at specification.ardalis.com and the Clean Architecture design decisions. The documentation counts as writing; the repositories' commits and releases don't.
  • Longevity: Writing since 2003-02-04, across four earlier blogs and the current domain. He's live: the latest post is from 2026-08-19, at about one a month as his effort moves to video and courses.
  • Depth: "Domain Modeling - Anemic Models" works a concrete failure through to the principle. "From Microservices to Modular Monoliths" has no migration guidance and ends on a discount code, and the Specification v9 post is release paraphrase by his own account. DevIQ is reference-grade on definitions and taxonomy, strongest on design patterns. Its entries argue in prose and diagrams, not code or measurements, so cite a measured source beside it for any claim an opinion rests on.
  • Accuracy: Sound: no claim found reversed or left standing wrong. In "Avoid Using C# Events", the logged memory figures don't increase steadily and there's no control loop, so cite the argument, not the measurements.
  • Independence: Co-founder of NimblePros and a Microsoft MVP, not an employee, so no independence limit.
  • Conflict of interest: He sells training, mentoring, and courses, and maintains Ardalis.Specification, GuardClauses, Result, SmartEnum, and the Clean Architecture template. The DevIQ entries nearest data access recommend Ardalis.Specification, whose Include and AsNoTracking surface is a query object, not a Specification in Evans's sense, so never present that pattern as settled.
  • Cite: The .NET posts. Most of the 2026 output is AI and agent tooling. GuardClauses, Result, and SmartEnum have had no release in about two years, and his Microsoft e-book Architect modern web applications is still edition v8.0, so neither is current guidance for net10.0.
aspnet-blog: Citable

The ASP.NET Core category of dotnet-blog: the same publisher and editorial standard, narrowed to ASP.NET Core posts.

avalonia-blog: Citable

A product-team blog, release-driven and close to marketing: cite it and the docs for how something works, not whether to adopt it.

  • Scope: Widened on 2026-08-20 to the project's own documentation, which explains mechanism the blog doesn't, under the same limit.
  • Longevity: About four years, which is over the two-year minimum.
  • Independence: The concern stands however long the record grows.
awesome-avalonia: Citable, Discovery-only.

A discovery channel, not an opinion source. Backed by the Avalonia community organisation and actively maintained.

awesome-blazor: Citable, Discovery-only.

A discovery channel, not an opinion source.

awesome-dotnet: Citable, Discovery-only.

Library discovery. Verify its recommendations independently.

code-with-mukesh: Citable, Corroborate.

A blog since 2020, marked for depth: SEO-shaped roundups that lead to courses, so use the shape of the guidance, not its specifics. The 2026 output includes real benchmarks.

csharp-digest: Citable, Discovery-only.

A discovery channel, not an opinion source. Archive verified back to 2017-12.

damien-bowden: Citable

Independent depth on ASP.NET Core security, OpenID Connect, and BFF, shown in working code.

  • Longevity: Writing since 2013-01-31, technical from the first week, and still publishing on 2026-09-01. Every sampled year between has several pages of posts, at least monthly. 2014, 2017, and 2022 weren't counted, and the years either side leave no room for a gap.
  • Depth: The BFF post covers the OpenID Connect setup, a YARP transform, and a token cache, and explains why the downstream API refuses the user's delegated token. The passkey post diagnoses an ASP.NET Core defect, links the runtime issue, and gives a re-sign-in workaround against RFC 8176.
  • Accuracy: Maintained in the open: posts have dated History sections that record what each framework version changed. When Duende's co-founder commented that a 2023 post resembled Duende's own sample, he added the attribution and said so in the thread.
  • Independence: A consultant in Switzerland with no vendor attachment, who covers Duende, OpenIddict, Entra ID, and ASP.NET Core Identity in turn, so no independence limit.
  • Conflict of interest: He maintains angular-auth-oidc-client and writes tutorials that use it, and he sells application-security workshops through isolutions.
  • Cite: Much of the catalogue pairs ASP.NET Core with an Angular front end, so check what a sample configures before you cite it.
derek-comartin: Citable, Corroborate.

Marked for two reasons: no code or measurements, and sponsorship in the article body. Cite him for the shape of an argument, and flag the sponsorship on anything about message queues.

  • Longevity: Writing since 2012-12-11, at about 40 to 50 posts a year from 2016 to 2025, and active on 2026-08-19. He's better known for his YouTube channel, but the blog qualifies by itself: 2,000- to 2,500-word articles that argue in prose, with the companion video embedded, not replacing the text.
  • Depth: The arguments are conceptual, with no code a reader could compile and no measurements they could reproduce.
  • Independence: Particular Software's NServiceBus is a paid sponsor inside the article body, on a tracked link, in posts about the sponsor's own product category. Verified on 2026-09-03 on "Decoupling in Software Architecture Moves Complexity", from 2026-08-06. He's also a Particular "NServiceBus Champ" and a Microsoft MVP.
dotnet-blog: Citable

Includes Stephen Toub's annual "Performance Improvements in .NET" posts and the "What's new" series.

fsharp-weekly: Citable, Discovery-only.

A discovery channel for the F# ecosystem, not an opinion source.

gerald-versluis: Citable

Five books, Pluralsight courses, and active on his blog and the .NET Blog through 2026. He's on the MAUI team, with the same independence limit as james-montemagno.

james-montemagno: Citable

Cite only the pre-2024 Xamarin and MAUI catalogue, and expect nothing new from harvests.

  • Longevity: Blogging since about 2012, first at motzcod.es, then montemagno.com. Re-vetted on 2026-08-23 on his writing alone, after the Merge Conflict podcast left scope. The blog still publishes, most recently on 2025-12-31, so he isn't dormant, but it now covers Copilot and tooling, and the last .NET post is from 2024-01-19.
  • Independence: He works in Microsoft developer relations and writes to drive adoption, with little critical distance, so judge each piece on its own.
jeremy-miller: Citable, Corroborate.

Cite the design essays, never the release notes, and never cite him alone on whether to adopt Marten or Wolverine.

  • Scope: The JasperFx news feed is out of scope, because it's almost all release announcements.
  • Longevity: Writing since at least 2007-10-18 at codebetter.com, which no longer resolves, so an earlier start is likely but unverifiable. He continues on jeremydmiller.com almost daily, and was active on 2026-09-02.
  • Conflict of interest: He created StructureMap, Marten, Wolverine, Lamar, and Alba, and founded JasperFx Software, which sells licences, support plans, and CritterWatch for that stack. He writes almost only about it: on 2026-09-03, eight of the nine posts on the front page were, and five of those were release announcements. The conflict is recorded, not limited, following nicholas-blumhardt and oskar-dudycz.
jetbrains-dotnet: Citable

An institutional blog. It's about tools, but the language explainers keep critical distance, so no independence limit.

jon-skeet: Citable

Created Noda Time, wrote C# in Depth, and is Stack Overflow's top contributor.

  • Longevity: About four or five posts a year. Much of the recent output is general data modelling from a personal election-data project.
  • Independence: Formerly Google developer relations, on the Cloud .NET client libraries, and between jobs as of 2026-07. He criticises language design he doesn't own, so no independence limit.
  • Cite: The C# and BCL posts. C# in Depth 4th edition (2019) predates records and isn't current guidance.
khalid: Citable

Cite the personal blog in full. Cite his Duende posts for platform mechanism, and never alone on whether to adopt a Duende product.

  • Scope: Widened on 2026-09-12 to his bylined posts on the Duende blog, about two a month from 2025-03 to 2026-10-01. The publication is watch-listed separately, so this ID covers his byline and nobody else's. The documentation is evidence, not citable material, as with shay-rojansky: his 387 commits to the docs repository, the latest on 2026-09-03, author whole pages, but the published pages name no author to cite.
  • Longevity: khalidabuhakmeh.com went quiet from 2025-04-22 and resumed on 2026-10-05 with two posts. His writing continued under the Duende byline through the gap. The two new posts are introductory: one explains int.TryParse, int.Parse, and Convert.ToInt32, and one maps Rails to ASP.NET Core. Neither has measurements, and no factual errors were found.
  • Independence: Now at Duende Software. His JetBrains authorship ended in 2024. The widening follows avalonia-blog, with a stricter version of the same limit: each of the three Duende posts read in full for this pass ends on Duende BFF or IdentityServer. "Understanding .NET 11 Automatic CSRF Protection" (2026-09-01) shows the citable kind: it explains what the framework middleware does to OpenID Connect flows, and the product recommendation sits at the end, where a reader expects it. "Securing Minimal APIs with Scope-Based Authorization in .NET 10" (2026-09-29) is citable for the AddAuthorizationBuilder and RequireClaim("scope", …) mechanism. Its sample assumes IdentityServer's one-claim-per-scope token shape, so check the issuer's format before you quote it.
mark-seemann: Citable

Twenty years of writing, with depth you can verify in compiling code and real measurements.

  • Longevity: Writing since 2006-01-05 on MSDN blogs, and on the current blog since 2009-01-28, with over 800 posts there. He wrote less in the mid-2010s, and was still publishing on 2026-08-13.
  • Independence: Self-employed in Copenhagen with no vendor attachment, and he criticises design he doesn't own, so no independence limit.
  • Conflict of interest: He sells books and video courses, and created AutoFixture, a mild conflict on testing and DI.
  • Cite: The C# and .NET posts. About a third of the technical output is Haskell or F#, and from "TDD as induction" (2026-02-23), the 2026 posts turn to language-agnostic essays on AI and software philosophy. Dependency Injection Principles, Practices, and Patterns (2019) supersedes Dependency Injection in .NET (2011).
meziantou: Citable

Very high volume and consistency.

milan-jovanovic: Citable

Promoted from the watch list when the longevity bar dropped.

  • Longevity: About six years, well over the two-year bar. The start year is an estimate.
  • Conflict of interest: He sells courses and templates, and runs a sponsored newsletter. The conflict is recorded, and isn't serious enough for a usage limit.
ms-learn: Citable

The "What's new" and "Breaking changes" pages for each release.

  • Scope: Widened on 2026-08-24 from the .NET docs to first-party technical documentation across learn.microsoft.com, including the .NET architecture e-books and the Azure Architecture Center pattern catalogue. Same publisher and editorial standard, so a clarification, not an admission, following the avalonia-blog widening of 2026-08-20.
  • Cite: For mechanism and pattern trade-offs, never product marketing or a service page that argues for adoption. Quote the page's review date from its ms.date metadata field, never updated_at. updated_at is a docset build timestamp shared by every page in a bulk republish, and it can run years ahead of the text. The difference matters because the pages age unevenly. The microservices e-book is 2018 and 2021 content, unreviewed since, and its 2023 and 2024 updated_at values are republishes. The Azure Architecture Center pattern pages are revised continually, and have recent ms.date values.
nicholas-blumhardt: Citable

Created Autofac and Serilog, and founded Datalust, which sells Seq.

  • Dormancy: The personal blog has been dormant since 2024-10. He stays citable under the dormancy exception, on published writing, not repository activity. The engineering posts on the Datalust blog continue, verified on 2026-08-23 through a post dated 2026-07-20 and a January 2026 engineering update.
  • Conflict of interest: An opinion that cites him on logging, tracing, or DI must flag that he writes and sells the tools in question.
  • Cite: The personal blog and the engineering posts, never Seq release announcements.
oskar-dudycz: Citable, Corroborate.

Event sourcing and event-driven design in worked, typed examples, from someone who builds tooling for those patterns.

  • Longevity: Writing since 2011-09-21, on a Polish-language blog later moved into the current site, and steadily from 2020, at about 50 posts a year through 2023. Active on 2026-08-10.
  • Depth: Verified on worked examples, with traced scenarios and typed code.
  • Conflict of interest: He co-maintains Marten and Emmett, and sells event sourcing workshops. The conflict is recorded, not limited, following milan-jovanovic and nicholas-blumhardt. The marking states the usage rule.
  • Cite: The .NET material. He also writes about Node, so check an example's language before you cite it.
scott-wlaschin: Citable

The standard independent F# resource, and author of Domain Modeling Made Functional.

shay-rojansky: Citable

Lead maintainer of Npgsql and on Microsoft's EF Core team, with the deepest writing on .NET to PostgreSQL type mapping, which no other roster source covers.

  • Longevity: Nine years of writing, 2014 to 2023.
  • Dormancy: No long-form writing since 2023, on roji.org or the .NET Blog. He's held on the dormancy exception by the documentation he writes, re-verified on 2026-08-23: the EF Core 11 what's-new and breaking-change pages in dotnet/EntityFramework.Docs, latest commit 2026-05-12. They publish to Microsoft Learn, so they count as writing.
  • Independence: Limited, because the citable material is first-party design rationale for products he maintains.
  • Cite: For mechanism, meaning how Npgsql and EF Core behave and why. Corroborate adoption judgements elsewhere. The 2014 to 2023 blog catalogue is citable. Expect nothing new from blog harvests.
stephen-cleary: Citable

Independent depth on async and concurrency in .NET, and author of Concurrency in C# Cookbook. The cadence is thin, so watch it for dormancy.

  • Longevity: Writing since 2008-06-20, at 30 to 67 posts a year from 2009 to 2013, and fewer than 20 a year after. The blog has no posts in 2019, between 2018-06 and 2020-03. The second edition of the book (O'Reilly, 2019-08) covers that year. He wrote eight MSDN Magazine articles from 2011 to 2015, including "Async/Await: Best Practices in Asynchronous Programming" (2013-03).
  • Dormancy: Not dormant, but close: the latest post is "Debug Dumps in Visual Studio" (2025-12-04), the only post in 2025, after five in 2024.
  • Depth: "There Is No Thread" traces an async write from the library through the driver, the interrupt, and the I/O completion port back to the awaiting context. "Don't Block on Async Code" walks a SynchronizationContext deadlock step by step, and argues for async all the way over ConfigureAwait(false) as the fix. "ConfigureAwait in .NET 8" covers each ConfigureAwaitOptions value, including that SuppressThrowing throws on Task<T>, which CA2261 reports. "Cancellation, Part 6: Linking" explains why comparing OperationCanceledException.CancellationToken fails once a linked source sits between, and checks IsCancellationRequested instead. The 2025 post is a Visual Studio settings recipe, thinner than the async catalogue.
  • Accuracy: Corrections are in the posts. The .NET 8 post says an earlier version wrongly claimed EF Core avoids ConfigureAwait(false), and that EF Core added it in 5.0.0. The 2012 deadlock post has a 2014-12-01 update pointing to newer material. "ASP.NET Core SynchronizationContext" (2017) revisits the deadlock guidance for a host with no context.
  • Independence: An independent consultant and Microsoft MVP with no vendor employer, so no independence limit.
  • Conflict of interest: He sells the book and contract work, and maintains the free Nito.AsyncEx library, which some posts link. Flag it where an opinion names Nito.AsyncEx.
  • Cite: The async, concurrency, and cancellation posts. The 2012 and 2013 posts predate ASP.NET Core, so check any claim about a SynchronizationContext against the host the citing opinion targets.
  • Re-evaluate: From 2026-12-04, if no post or other writing has appeared since 2025-12-04.
stephen-toub: Citable

Publishes through dotnet-blog.

steve-gordon: Citable

Variable cadence: heavy in 2024, quiet in 2025, and active again in 2026. Works at Elastic. The back catalogue is authoritative.