Finding the right tool and language that allows you to express yourself in code isn’t an easy thing. There have been multiple tools and frameworks developed because the existing ones weren’t productive, even computer languages created for the same reason. For me though, learning to type is one of the things that allows me to be productive regardless of the tool or language. Once you’ve learnt the syntax of the language; you still have to transcribe your thinking into the language, and into the computer.
Continue reading Language is not the barrier
We’re in the middle of doing an upgrade of our systest HPCC instances to 6.4.2 so I thought it would be a good time to upgrade my local HPCC virtual machine instance to HPCC 6.4.2 + Hyper-V. This time I converted the image using qemu-img. Sadly though I couldn’t use dfuplus to spray files in. It complains about
Failed: No Drop Zone on 'xxx' configured at '/path/to/file'. When I tried to despray files using dfuplus you get a different message
Dropzone not found for network address x.x.x.x..
Continue reading HPCC 6.4.2: dfuplus fails to spray files
In any large organisation there is going to be friction between various competing dynamics; one of which is whether to decentralise certain functions or to centralise them. Sometimes it makes sense to centralise, sometimes it doesn’t. The desire for centralised control is massive, but it’s often better to let things happen organically as they need to.
Continue reading Decentralised Autonomy vs Centralised Control
Recently we purchased a watch; a purple affair with butterflies to be exact. Didn’t cost much, and we expected it to be perfectly functional until the battery ran out. As it turns out, after a day, we found out that if you press the dial knob in, the watch stops. It was a reputable high street retailer so you’d think the situation would have been quite easy to rectify.
Continue reading Cash is still king
For a number of reasons (some historical, some legacy, some just daft), the optional Interlok components live in various git providers. This isn’t a post that argues that git flow is great; it’s well understood so we use it to remove the friction of understanding a bespoke tagging/branching system. When we do a product release there’s a Jenkins pipeline that builds all the artefacts based on the release branch from
git flow release. That means that when we decide that it’s time to prepare for a release, we have to do a git release start on every project and publish that branch; all of which is nice and scriptable.
Continue reading git flow release