Fluent Method Chaining in C#

What if there was a way to declaratively describe a chain or flow of async methods, which could be used when handling API requests or messages from a service bus queue or actually anywhere? Recently, while refactoring a growing piece of business logic, we found a way to achieve this. The logical conclusion is that related flows can be described in one place, in a single piece of orchestration, which is very easy to understand, navigate and debug. The flows are self documenting and with some thought, even readable by product owners and business analysts etc.
-About the Speaker
Andrew Poole
Andrew Poole has been writing code for a living for 15+ years, most recently as an L5 Senior Software Engineer at ClearBank since 2020. He loves solving problems, design and architecture, communicating ideas and the incredible creativity of software engineering. He’s interested in event sourcing, immutable architecture and distributed systems. He also enjoy mentoring others and building great team culture. He has previously been a successful team lead, but what really drives him is striving to write elegant, intentional code which is easy to understand and maintain. He absolutely loves C# and only really dabbles in other languages in order to write better C#. Outside of work Andrew is a husband and father of 2 who enjoys playing bass guitar and making things in his shed.
forkinthecode....
x.com/AndrewP7...
/ andrew-poole-2782494a
-
Links
dotnetsheff.co.uk
www.meetup.com...
x.com/dotnetsheff
-
The Video
Recorded by Adam Bright (x.com/adam_lx)
Mixed by Kevin Smith (x.com/kev_bite)
-
dotnetsheff
dotnetsheff is a monthly user group focused on software development, particularly in the .NET ecosystem. We welcome people with interests in software development of all ages and levels of experience

[@matthewhxq]

It looks really clean & nice but I wouldn't say it's simpler and easier to digest for the next new dev that will work on that code base.

[@avwie132]

Is it 2006? I know this was the hype back then

[@cinosz6780]

He uses minimal API, so it's not 2006

[@hellowill]

I thought C# users hate Java for exactly this reason?