F#
A few years ago (I know, I really should update this blog more often) I asked WTF is...a computation expression. Well, I'm happy to say in the meantime I discovered a great use for one that's reusable, and have finally released it as a library.
Social Media
So now that Twitter has been sold and is already in trouble, with dropping ad revenue, mass layoffs, and the prospect of accounts previously banned for hate-speech returning, it's no surprise that a lot of people are looking to move to other platforms. Enter Mastodon, a decentralised platform
F#
Announcing the first alpha release of F# support for Entity Framework Core 5.0.3
Azure
How to not have to go through multi-factor authentication every time you open Azure Storage Explorer
F#
...and why should I care? Every time computation expressions in F# are discussed it's only a matter of time before the dreaded M-word is mentioned. So let's get it out of the way early.... Monad Right, that's that done and let's not
Docker
I've written before about developing software in Docker containers and while that has been a step forward for development and being able to isolate development environments, the strength of Docker has always been in running applications without having to worry about requirements or dependencies. For managing clusters of
failure
I'm writing this up for two reasons, one is that I can find this again next time it happens. The second is simple but important, we all make mistakes and at times they can seem pretty obvious in retrospect. But it's important to share the stories
F#
We've all heard of unit testing and some of us have even been known to practice it. It has a simple premise * Have a method or some other "unit" of code you want to test * Pass in some contrived test data * Compare the result to what
F#
Setting up a new project can be a pain. Especially if you want to split it into separate folders for clarity. You might want a src folder for the project itself, a test folder for the unit and integration tests, a docs folder for documentation. You are writing documentation for
.NET Core
It is a truth universally acknowledged, that a .NET project in possession of multiple time zones, must be in want of Noda Time. Sometimes though, we have an existing project where it's just not reasonable to move everything over and we need a way to display a DateTime
C#
Back in the good old days, C# was .NET was Windows. Sure there were antique languages like VB.NET and ivory tower academia from F# but real developers used C# and the language was just fine as it was. Sure, some additions helped, generics were ok even if they did
.NET Core
Since the beginning of time .NET Core there has been one continuous annoyance about developing cross-platform solutions, including build scripts for windows and non-windows platforms. We have at least fallen into a standard pattern, most repositories will contain both a build.cmd and build.sh that will build the project
Docker
Ah, a new open source project that looks interesting. Let's pull it down from GitHub, open it up in the IDE of our choice and.... Oh... It turns out the build scripts assume you have some build tool already installed or, even worse, a specific version of it.
JavaScript
.NET Core
Publishing a .NET Core application as a single executable file, and keeping it as small as possible
F#
Recently I decided to implement a chess engine as a way to explore building a rules engine in F# GitHub link: https://github.com/simon-reynolds/FsChess F# was my choice of language as it has a number of advantages. For instance, defining the pieces is a lot simpler thanks to