Naming of your methods

by Apr 10, 2023Shorts

Good naming of your methods can solve a lot of customer issues.

I use NServiceBus as messaging framework in dotnet. I was using a method of this framework, which wasn’t doing what I was expected.

NServiceBus uses a UnitOfWork pattern when sending messages. I was using the method RequireImmediateDispatch(), This flags NServiceBus to dispatch messages immediate, instead of sending them at the end of the UnitOfWork.

Apparently, there is also a method to check if this flag is set. This method is called RequiredImmediateDispatch(). Did you see the problem?

I didn’t. It is only different by one letter.

I used the wrong one in my code and that resulted in strange behavior that I couldn’t explain.

In NServiceBus 8 this method is now renamed to IsImmediateDispatchSet() which hopfully prevents my mistake happing to other users.

Architecture, Eliminate Friction, NServiceBus
Remy van Duijkeren

Remy van Duijkeren

Power Platform Automator

Automation and integration aren’t just what I do—they’re what I do best.

I help businesses work smarter by removing friction, automating what slows them down, and connecting systems that should’ve been talking all along.

 

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related