We’ve been making the transition from Java to Go and React at the company I work for. Over the last year or so most of our new web applications consist of a Go backend and React front end. This has been a pleasant experience for the most part, but there’s a lot to learn so I decided to write a bunch of Go programs on the side to explore the language.
I put together another mix. This one is a way of replicating some feelings of when I saw John Digweed play a monster 5hr set back in 2002. It was the best thing I ever heard. He lays down a groove and sits you in it and never lets up. Hour after hour of relentless, mesmerising tunes. A vortex that you can’t escape. It was wonderful and I wish I could hear it again.
In the first few weeks of pandemic isolation I setup Ableton again and had some fun mixing tunes. This is one I’ve been wanting to get out for a long time: big, fat progressive-house, heavy groove, shiny on the top, a bit silly in places and straight from my heart.
I store snippets of code with Github Gists to remind myself how to do things that I don’t do regularly enough to remember off hand. At first it was only a few, but my list is growing and as it grows it becomes harder to find the one I want. I’ve made myself a little Firefox extension to list all my Gists with a search field so I can quickly locate them.
There’s a task I perform regularly and it’s always a 2 step process. One of the programs I maintain queries the database and the SQL is a long series of concatenated strings in a Java source file. I copy the query into a text editor and then remove all the quotes and plus characters so I can modify and test it on the database. Ideally SQL would be kept in an SQL file and it would be easier to work with, but in this case I don’t have the liberty of making that modification.
I mixed some tunes a while ago and I’m still quite fond of the result. I made it with Ableton software and it captures a sound that I’ve been working towards over the years; techno, a little wonky, melodic, soaring in places, abrasive, with a steady, heavy groove and a few frilly bits.
Today I was given a task to extract customer account IDs from a log file. grep came to the rescue, however I was then required to add a fixed offset to each account ID so I could build an SQL query with an IN clause. I could have managed this by piping the output of grep to awk or bc, but I thought I would flex my vim muscle in this case.
