devjoy

I don’t create cron jobs very often.

Back in 2015 I wrote a post on unit testing events and callbacks in C#.

A tweet about some C# code rewritten in F# got me interested yesterday.

The Problem When you want to unit test a method it’s usually pretty simple.

This week at our FunctionalKats meetup in Dublin, we tackled a simple programming task the Luhn checksum algorithm.

Grap The Code Mastermind, is a code breaking game for two players.

Still the best job I’ve ever had and I’ve given up hoping there’ll ever be a better one.

Here’s a really great post by Tom Moertel on squeezing every last ounce of performance out of machines back in the day.

And so, we arrive at the last post of the series.

Playing Cards are a commonly used example of discriminated unions in F#.

We close out the discussion of Single Active Patterns by adding parameters to the partial active pattern.

I’ve referred to all of the Active Patterns we have seen so far in this series as ‘Single Total’.

This post was supposed to be about Partial Active Patterns, but before we get to that, I want to take a small diversion to cover Partial Application of Active Patterns (which is a completely different thing).

We move on to the next in our series on Active Patterns, but this time we’re really just covering a slight modification to the Single Total pattern that we covered in the last post.

This is the first in a series of posts explaining Active Patterns, a very cool feature of F#.

You can’t work in this business for very long before the hope, idealism and intellectual curiosity is beaten out of you and replaced with TPS Sheets, and 15 different tools for telling your colleagues how to configure IIS so that your app will actually run

In the most recent post in this series I implemented Tic-Tac-Toe using recursion to find the best moves.

Constant Learning Being a software developer means constant learning.

Part 1 of this series was mainly sharpening the axe by covering some basics like Pattern matching.

This post looks at a hugely important part of functional programming, Recursion.

I don’t normally review books, mainly because when it comes to technical books I rarely manage to read them in their entirety.

Every movement needs an enemy, it galvanises followers, gives a community a sense of some shared identity.

Here’s a problem I come across all the time in legacy code and I have been guilty of it myself in the past.

Ladies and Gentlemen of the class of ‘14 If I could offer you only one tip for the future, simplicity would be it.

Imagine you have a long running function that you’d like to avoid running unnecessarily.

He sat in the large bay window observing the potential candidates as they approached the house.

I am growing increasingly frustrated with C#.

Why do cars have brakes?

In my last post I worked through an example that finds the range of numbers that sum to a target value, or gets as close as possible without exceeding the target.

Another F# session this evening and some more deliberate practice of Functional Thinking.

Warning, novice functional thinker here.

I like Kata’s, I’ve get a lot out of them, but if I’m truly honest, they don’t really address one area of programming where I think I need practice, and that is in working with Legacy Code.

Back in 1995 I sat in a large ballroom to listen to politicians from the North and South of Ireland talk about the peace process, which at that time was far from a sure thing.

The following is my C# implementation of the Anagrams Kata as described on cyber-dojo.com Write a program to generate all potential anagrams of an input string.

To land a plane you need to line up with the runway, figure out the right rate of descent and airspeed, then monitor and manage those, all the way down to the ground.

It’s verging on heresy to even talk of Unit Tests and Comments as being in any way related.

One session at NDC that really kicked my grasp of functional programming up a few notches was Vagif Abilov’s discussion of Conway’s Game Of Life using F#.

I’m not going to justify kludges, or apologise for kludges.

Here’s a scenario (for once not a hypothetical scenario, this is a real system I worked on).

One problem with TDD is that those who try it, often begin by writing a few trivial tests to get the lie of the land.