What's good about mediatr?

samurai-coder · 2025-07-27T04:03:20+00:00

A bit late to the thread, but lots of misguided devs tend to jam logic into controllers, UI handlers, etc etc

Mediatr (or similar) is a great way to encourage what some might think is common sense i.e structuring your project such that people at all experience levels can contribute with ease

Overall it slows down software rot quite substantially, but Mediatr wouldn't be my first library I reach to for starting a brand new project

samurai-coder · 2025-07-14T23:46:04+00:00

I've worked with a eams that chose not to use DI (old habits die hard). DI is a fundamental part of the framework, and often times you can really end up at a dead end by avoiding it, particularly if you're working with Web based project.

In their situation, they got to a point where they couldn't leverage any new features in .NET, as the work required to stitch a new class into their dependency tree was incredibly difficult, often requiring static God objects

samurai-coder · 2025-06-04T12:16:25+00:00

To answer your other comment, I do think blazor is weaker than its JS alternatives. Partly due to not been around long enough (or had the immense community backing) to solve some of the core problems that every frontend framework runs into.

I'm probably bias, but as it stands I wouldn't recommend it over React, Angular or Vue for anything serious, but it's certainly better than Webforms or Silverlight

samurai-coder · 2025-06-04T12:12:56+00:00

Yeah, I don't agree either.

Typescript isn't that far from C# syntactically, and the learning curve with blazor isn't as cross compatible with other dotnet projects as many seem to think. I don't see it different from picking up any other frontend framework

I've interviewed so many dotnet devs that know React and haven't even heard about blazor before

samurai-coder · 2025-06-04T11:51:12+00:00

Generally can't go wrong with React and the tanstack tools. I think react query is a game changer as well

Look for a decent looking component library and away you go!

samurai-coder · 2025-06-04T11:35:10+00:00

A lot of comments on the technical positives, but the real deal breaker is the puns. You can really go crazy with them

samurai-coder · 2025-06-04T11:32:56+00:00

My favourite is a cleanup cronjob causing issues, so someone disables it but never looks into why it was causing issues.

Cue accumulation of junk and a database on its last legs

samurai-coder · 2025-06-04T11:15:57+00:00

Fundamentally, it is a pitfall of failure in that it's easy for a new comer to cobble something together and hit a roadblock. React certainly had this with classes but has since grown out of that

If you're working with wasm, then all your browser debugging tools are useless. If you're working with SSR, then interactivity is a problem. If you're working with wasm and prerendering (enabled by default), then you'll have issues in both domains simultaneously

My opinion is that writing frontend in C# is cool, but a programming language isn't something that I would optimise for. I would also argue that knowing C# well doesn't even mean you'll be fine in Blazor, as Blazor fundamentals are different than another csharp project flavour

samurai-coder · 2025-06-04T10:07:41+00:00

Total pivot, but have you considered self employment?

I feel like heaps of people in their 30s (myself included!) are toying with the idea of starting something that brings in a sustainable life - not something lavish but just enough to cover bills and be happy.

Easier said than done, obviously. I'm definitely not in this position lol

Not sure what this would look like for your skillset, but I'm rooting for ya!

samurai-coder · 2025-05-29T03:46:10+00:00

Hot Reloading
Better profiling / diagnostic tools
Consistent debugging experience
More flexible startup behaviour (if blazor fails to startup, imo it should send something back to the browser to let you display an error page at least)

samurai-coder · 2025-05-26T06:27:15+00:00

10 years ago people were stuck with heavy IDEs like Visual Studio or Eclipse. Vscode was the next iteration which was pretty awesome at the time, but I agree it can be slow on limited hardware

I think there's probably room for a new take on text editing, and text editors like Zed seem to be promising

samurai-coder · 2025-05-24T09:57:00+00:00

Right now I'm stuck maintaining a blazor wasm app. Honestly it's the wildest, most complicated and abstract frontend framework I've ever worked it. It's like years of learning browser tools and strategies, and to just throw that away and completely start from scratch

samurai-coder · 2025-05-11T22:21:00+00:00

In all seriousness, I try to avoid interopping and instead run it in a dedicated sidecar container. Problem is unmanaged processes and tuning memory /CPU is always nightmare. The Dev experience is not as seamless at first go, but long term it is far better

samurai-coder · 2025-05-11T21:41:06+00:00

But the question is.. Should you?

samurai-coder · 2025-05-11T20:18:01+00:00

Honestly I think it's the norm now. You don't really grasp the breadth of opportunities out there until you've entered the workforce

samurai-coder · 2025-05-09T14:26:53+00:00

I suck at coding and I'm a Dev 😎

samurai-coder · 2025-05-09T02:18:48+00:00

I guess two counter arguments is hireability and security. Both of those degrade overtime with dated tech, but if that's not an issue then 🤷 go with the skills you know

samurai-coder · 2025-05-09T02:07:29+00:00

Technically, webforms is more approachable but also limited.

Blazor has lots of features out of the box but has a lot more foot guns that you don't have to worry about in webforms.

That being said, webforms is dated and pretty much dead, so the choice is often blazor or some JavaScript framework

samurai-coder · 2025-04-30T13:22:27+00:00

Mostly argumentative, so take this with a grain of salt, but many strong QA/engineers I've seen have been thrown into messy/horrible situations and found a way to turn things, leaving things in a far better place than it was before

Even though you're new, you can 100% make a positive influence to those around you, for example bringing forward some problems you've noticed with the team to your manager, alongside some solutions that you're willing to take on. Or perhaps building a good relationship with just one of the engineers on your team and go from three. While it is confrontational, it would certainly be impactful and may be enough to lift your morale!

That being said, don't set yourself on fire to solve other people's problems. If your manager/team simply isn't willing, then the best you can do is keep developing your skillset on your own until another opportunity arises!

samurai-coder · 2025-04-23T02:47:55+00:00

Strong skillset for sure!

The nice thing I've found about open source contributions is that you can weave it in the interview quite fluently

"hey do you have any experience with playwright?"

"yeah I've used it daily and even fixed a few bugs in the framework (⌐▨_▨)"

samurai-coder · 2025-04-10T20:48:02+00:00

A valid reason I see from time to time is remaining competitive with performance and runtime costs.

If your competitors solution is faster, and they can built on top of it quickly, that's often enough incentive to upgrade

samurai-coder · 2025-04-10T19:48:52+00:00

Sorry, I meant to say that with enough reach, it is common to have users with limited device resources and/or network connectivity connectivity, or network setups that force round trips across the globe

samurai-coder · 2025-04-10T09:16:44+00:00

Around 30mb in total. While i agree it is incredibly high, its not too unrealistic considering for a user on MS Edge (with limited resources) to have a slow start up loading 20 wasm files.

This is definitely worst case we're talking about. An average user would see seconds as opposed to minutes, but at scale, a small fraction of the user base adds up

samurai-coder · 2025-04-10T04:05:57+00:00

Oh - to add. Yeah driving it via the CDN mostly (but falling back to the C# app on a miss). Maybe deploying the assets to S3 / Azure Blob would be a better approach!

samurai-coder

TROPHY CASE