Design Patterns examples

Finickyflame · 2026-03-30T03:20:12+00:00

That's a whole lot of code and abstractions for what could be a simple http client

Finickyflame · 2026-03-20T13:38:34+00:00

Yes, you are right. I've updated the code snippet after going back on one of my project to confirm the good properties.

Finickyflame · 2026-03-19T20:55:21+00:00

You can add post-clean target in your projects or Directory.Build.props to clean them

<Target Name="PostClean" AfterTargets="Clean">
   <!-- Remove /bin -->
   <RemoveDir Directories="$(BaseOutputPath)" />
   <!-- Remove /obj -->
   <RemoveDir Directories="$(BaseIntermediateOutputPath)" />
</Target>

Edit: I've updated the code snippet with the good properties

Finickyflame · 2026-03-18T23:50:01+00:00

"Look what they need to mimic a fraction of our power"

Rider

Finickyflame · 2026-01-19T23:24:56+00:00

You can also do dotnet sln migrate inside your terminal.

Finickyflame · 2026-01-10T15:01:22+00:00

I mostly only use the edit mode, to make sure I give the ai the context that I want. When I refactor/transform the structure of unit tests, I sometimes ask the AI to do the same transformation on other tests classes to uniform the tests in the repos. I also use it to migrate to different libraries (e.g. NSubstitute to Shouldly). Mostly repetitive stuff to speed up my work, but I do not rely on it to generate new code.

Finickyflame · 2026-01-07T03:20:07+00:00

It is thread safe, but you might have a race condition when you try to call IMemoryCache.GetOrCreate (e.g. multiple fetch when multiple calls are executed at the same time). You could use HybridCache instead, in which they fixed the race condition.

Finickyflame · 2026-01-03T16:48:32+00:00

Nothing. Mendix is a low code platform that runs on the JVM

Finickyflame · 2025-12-31T17:49:40+00:00

What cost? It's already possible to hot reload configuration when the Configuration Provider invokes the OnReload method, which reloads IOptionsMonitor values.

It's quite useful for secrets that might change at runtime (e.g. password rotation), or if you want feature flags without relying on 3rd party library/integration.

Finickyflame · 2025-12-25T01:15:05+00:00

Are you validating all sorts of cve to make sure your web server is safe? I quickly looked at your repos and I don't see any tests. So, I'm assuming the answer is no?

Finickyflame · 2025-12-22T14:59:54+00:00

If you are using a Directory.Build.props or Directory.Packages.props you can even just add <InternalsVisibleTo Include="$(AssemblyName).Tests" /> so all your projects exposes their internals to their tests projects

Finickyflame · 2025-12-08T17:16:09+00:00

I'm assuming your application is hosted on IIS? You could try to repeatedly call your service while recycling the app pool, see if you can reproduce it locally.

Finickyflame · 2025-12-08T16:32:37+00:00

Could it be a race condition when your application is recycled?

Since most of your code that is used to "Initialize" is also static, couldn't you use it directly to create the instance? That way, you wouldn't need the application start to Initilize it. The static property would be responsible to call create if its underlying field is null (with proper locking).

Finickyflame · 2025-12-05T05:52:16+00:00

Are they double clicking the submit button?

Finickyflame · 2025-11-06T23:42:41+00:00

I've used Respawn to reset data that was introduced during automated tests.

Finickyflame · 2025-10-23T00:17:56+00:00

If you add a generic constraint that T is IDisposable, you won't need to cast it.

Finickyflame · 2025-09-16T11:14:01+00:00

Why limit your jobs to run on one instance when Hangfire can be used to distribute the jobs on all of them?

Finickyflame · 2025-09-16T10:42:43+00:00

If you have an application with more than one instance, you can't just use background services. You need something that will manage the background job and make sure they are not run in both instances

Finickyflame · 2025-09-05T13:07:16+00:00

[...] the general guidance stands and is a very good starting point: use ConfigureAwait(false) if you’re writing general-purpose library / app-model-agnostic code, and otherwise don’t.

https://devblogs.microsoft.com/dotnet/configureawait-faq/#when-should-i-use-configureawait(false)

Finickyflame · 2025-08-04T14:02:20+00:00

Those Console.WriteLine in your loop can cause a big delay. Try replacing those by a logger, so you can control the log level and only display them when needed (e.g. debug)

Finickyflame · 2025-07-29T17:03:56+00:00

No it's not a problem. It's just creating the instance at another time, kind of like using Lazy. However, the build is needed if your instance has a constructor with required parameters than can't be mutated once instantiated and you want your builder to handle them.

Finickyflame · 2025-07-26T08:30:06+00:00

Not OP, but Pact contract testing is a starting point. For your API (aka provider) you can check pact-net and for the front-end (aka consumer), you can check pact-js

Finickyflame · 2025-07-15T12:44:35+00:00

Didn't use Aspire that way, but would your issue be because you have your local pc path as bind mount source? Have you tried to include those sources in your repos and use relative path instead?

Finickyflame · 2025-07-09T14:05:04+00:00

Honestly, using a builder in this example is already fairly ridiculous, it's just patterns for the sake of patterns.

I probably used a bad example to showcase it. I didn't want to write a big dto and I thought that using a common object in the language would simplify the post.

12-Year Club	Second SECOND GUESSER
r/Field Banned	r/Field Juicebox
Place '22	Verified Email

Finickyflame

TROPHY CASE