Breaking maze routes, and recovering automatically
Older posts can be found at my previous blog.
Some Minecraft mod basics, with the added bonus of a Scala implementation of Prim's algorithm reworked for maze generation.
Do you actually need to error there, or is your method just badly named?
Translating safe continuous deployment into legacy enterprise contexts
Avoiding key scans by convention and supporting queries of varied sophistication
Trials getting hold of scalajs-react
A first look at Scala
Moving on from an organically-grown aggregate implementation.
SkillsMatter hosts muCon at their CodeNode in London.
Paying attention to a couple of simple signs can save you an awful lot of redundant compute time.
Understanding deadlocks won't help if you haven't engaged in some really very (very) basic thought about DB schema.
Enabling differentation of tasks by priority
At the moment all tasks are considered the same. If a client wanted to process only “widget painter” tasks it wouldn’t be able to, unless it pulled tasks fro...
In the last post it looked like the rate of submission and completion of tasks was constant in time, but that the rate of completion of workflows was not.
I’ve set up a simple benchmarking app to get a look at how my new Redis-based workflow processing system was going, and used it to create 100k workflows, eac...
This post relates to code changes in this commit to my redis workflow project on GitHub, under this issue .
One thing is certain in any live system: something will break and leave the system in an inconsistent state. If your system isn’t designed with this as a cor...
I started analysing a production crash dump at my desk, with a set of libraries that don’t match those installed on the production server. Typically windbg w...