u/devensawant1

▲ 139 r/dotnet

Which C# 14 feature actually changed how you write code day-to-day?

I've been running .NET 10 in a couple of side projects since the LTS drop. When it launched I assumed that the big C# 14 win for me would be extension members. It's nice but the feature that I actually ended up using the most is turned out to be the boring one: the field keyword.

Every time I needed a little validation in a property, I used to write the full backing-field:

Before (C# 13):

private string _name;
public string Name
{
    get => _name;
    set => _name = value?.Trim()
        ?? throw new ArgumentNullException(nameof(value));
}

After (C# 14):

public string Name
{
    get;
    set => field = value?.Trim()
        ?? throw new ArgumentNullException(nameof(value));
}

No hand-declared _name. Tiny change, but it shows up multiple places, which is exactly why it wins.

The other one which impressed the most is the file-based apps which quietly replaced half of my throwaway scripts:

Before:

mkdir tool && cd tool
dotnet new console
// edit Program.cs + csproj, then:
dotnet run

After:

// tool.cs — no project, no folder
Console.WriteLine("Just run me.");

dotnet run tool.cs

Type-safe code with the full BCL and zero .csproj turned out to be more useful than I expected.

So I'm curious where everyone actually landed:

  • Which C# 14 feature earned a permanent spot in your muscle memory, and which turned out to be a demo-only feature?
  • Anyone using extension members from C# 14 in real code yet, or still letting it settle?
  • And for the folks still on .NET 8 what's holding up the jump to 10?
reddit.com
u/devensawant1 — 4 days ago

I made a beginner explainer video on the reconcile loop (via a "call-center floor manager" analogy) - feedback on where the analogy oversimplifies?

Disclosure up front : this links a video on my own YouTube channel. The narration is AI-voiced; the script and the stick-figure animation are mine. I'm posting because I'd genuinely like feedback from people who run k8s for real on where the analogy leaks - not just for the click.

The video explains orchestration to people brand new to k8s using a call-center floor manager with one rule: keep ten agents on the phones. Not "hire ten people" - keep ten on the phones, always. All he does is loop: count who's actually on, compare to the target, fix the difference. Forever. When you write it out, the logic is simple: all those separate features are actually handled by just one reconcile loop.

  • Self-healing: an agent walks out -> nine on the phones -> he drops a fresh identical agent in the seat. The controller doesn't nurse the dead pod back to health, it replaces it (cattle, not pets). Restart-in-place when it can, reschedule elsewhere when it can't.
  • Rolling update: swap agents one desk at a time so nine are always answering and the new one only takes real calls after it passes a test call. That test call is the readiness probe. A failed one pauses the rollout; it doesn't auto-revert (someone has to call it off).
  • Autoscaling: the target itself moves. The rule was never "ten agents," it was "enough for the queue." Load climbs -> seat more; quiet at 3am -> send them home.
  • The trap I spend the most time on: "still running" != "working." Liveness asks "is the agent at their desk?"; readiness asks "can they take a call right now?" A pod can be up, pass liveness, and still serve garbage "green light, dead app" because the loop only checks the exact thing you told it check.

Where I'd like the feedback: for a first-exposure audience, does "replace, don't repair" + the liveness/readiness split do more good than harm, or does compressing it this hard set people up for wrong mental models they have to unlearn later? Where does the floor-manager analogy actually break?

Video : https://youtu.be/-DYyGk28_kk

u/devensawant1 — 15 days ago

SaaS spend management for SMBs - is the gap between "spreadsheets" and "enterprise SMP" real?

Thinking about building a focused tool and wanted to gut-check the idea before writing code.

The problem: Companies use 30-100+ SaaS tools but most don't have a single view of what they're paying for. Duplicates, forgotten subscriptions, and surprise renewals quietly drain budgets. Enterprise tools exist (Zylo, Torii) but they cost $30K+/year and take months to set up.

The idea: Upload a credit card CSV or PDF and the tool identifies every SaaS vendor, categorizes them (project management, design, communication, etc.), flags overlapping tools, and alerts before renewals.

What it doesn't do (intentionally): No usage tracking, no SSO integration, no browser extension. Just financial data analysis. Keep the scope tight.

Tech: Planning to build with .NET Core + SQL Server. The hard part is the vendor matching engine - mapping messy transaction descriptions like "ATLASSIAN* JIRA" or "FIGMA INC 4029" to actual SaaS products.

Revenue model I'm thinking:

  • Free: one-time upload, basic report
  • $29/month: recurring tracking, renewal alerts, trend analysis
  • $99/month: team dashboards, multiple cards, recommendations

My questions:

  • Is $29-99/month reasonable for this, or would SMBs balk?
  • Has anyone seen this done well already? I found enterprise tools but nothing lightweight
  • The vendor matching engine feels like the real moat here - am I right or is that easily replicable?

Would love honest feedback. "Don't build this because X" is just as valuable as encouragement.

reddit.com
u/devensawant1 — 2 months ago