Why didn't I find this great feature of Rider earlier?
It makes initialising records so much easier.
And with a quick invocation of Fantomas, the record is reformatted to match our settings regarding { } alignment. We prefer the Aligned option.
Software engineering, architecture and design stuff, mainly on .Net, F#, and Azure.
Co-Host of .Net user group Central-Switzerland.
#fsharp
#dotnet
#SoftwareArchitecture
| Blog | www.planetgeek.ch |
| www.linkedin.com/in/ursenzler/ |
Why didn't I find this great feature of Rider earlier?
It makes initialising records so much easier.
And with a quick invocation of Fantomas, the record is reformatted to match our settings regarding { } alignment. We prefer the Aligned option.
Wir starten mit der .NET Usergroup am 29. Januar um 18:00 ins 2026 mit einem Rückblick aufs 2025: https://www.meetup.com/net-usergroup-zentralschweiz/events/312897213/?utm_medium=referral&utm_campaign=share-btn_savedevents_share_modal&utm_source=link&utm_version=v2&member_id=183006099
Und es war nicht nur AI los.
As the saying goes, there are only twelve F# developers in the world. Obviously, they must have multiple jobs, according to this list of companies using F#:
https://github.com/fsprojects/fsharp-companies
By the way, if you use F# and your company is not on the list, please take the time to add it.
Hey #csharp and #fsharp fellow devs, check out https://github.com/nietras/Sep by @nietras a very well designed parsing CSV library.
First time I see sample of codes made with test assertions. Yes yes yes!
Also, very pleased to see fuzzy testing being mentioned.

World's Fastest .NET CSV Parser. Modern, minimal, fast, zero allocation, reading and writing of separated values (`csv`, `tsv` etc.). Cross-platform, trimmable and AOT/NativeAOT compatible. - n...
Currently watching "Why Rust isn't everywhere (yet)". https://youtu.be/nOSxuaDgl3s?si=FFhGEyfDCfGO7LpH
A great interview.
And as an F# developer, I see many parallels.
And I will stick with F# - fits our needs better regarding application development.

However, I find the core idea of having developers who can implement a feature end-to-end essential to efficiently and effectively delivering features to customers and users. Otherwise, hand-offs and communication synchronisation points slow the team dramatically. 2/2
Full Stack Developers seems to be a hot topic again (according to my social media feeds).
I don't like the term because what this full-stack depends on heavily is context.
For example, in our team, full-stack means: HTML, CSS, Angular, TypeScript, https://ASP.NET Core, C#, F#, SQL Server, Redis, Azure Table Storage, Azure Blob Storage, Azure Web Services, Azure ServiceBus, IdentityServer, Azure AppInsights, Dapper, Nuget, and running all these things in production - and much more. 1/2
Every decision in software development is a trade-off decision.
Should I use TDD or not to develop that piece of code?
Relational DB or table storage?
Model with bounded contexts or not?
FP or OOP?
If you think one option is always the best, you either work in a narrow context or you don't know enough about the alternatives.