<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TickerQ on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/tickerq/</link><description>Recent content in TickerQ on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 13:20:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/tickerq/index.xml" rel="self" type="application/rss+xml"/><item><title>The .NET Libraries I Reach For</title><link>https://lab.artur-rios.tech/dotnet/library-recommendations/</link><pubDate>Wed, 21 Oct 2026 13:20:00 +0000</pubDate><guid>https://lab.artur-rios.tech/dotnet/library-recommendations/</guid><description>&lt;p&gt;Every new .NET project starts with the same handful of decisions. How will I&#10;test it? Where does fake data come from? How do I validate input, survive a&#10;flaky dependency, export a spreadsheet, run something every night? The base&#10;class library answers some of these. For the rest, I have settled on a short&#10;list of NuGet packages that I add almost without thinking.&lt;/p&gt;&#10;&lt;p&gt;This page is that list, with the reasoning written down. For each library I&#10;explain what it is for, why I use it, show a small example and say when I&#10;would pick something else. A recommendation is only as good as what it&#10;leaves out, so I also flag what I would want to know before adding a&#10;dependency: licence, maintenance, breaking changes, and in two cases events&#10;that every user of the library should know about.&lt;/p&gt;</description></item></channel></rss>