Skip to main content

Cerebral Bore, Revocation, Job For A Cowboy and Dying Fetus


Last night Cerebral Bore, Revocation, Job For A Cowboy and Dying Fetus all played in the studio (the little upstairs room) at the Waterfront in Norwich. I couldn’t understand why until I saw the size of the crowd. It was tiny and mostly young enough to be my children! This was just one of many ways I felt old this evening.

I’ve wanted to see Cerebral Bore [8] for a long time! I missed them at Bloodstock last year because I couldn’t go! It’s unusual to find a death metal band with a female vocalist (I said unusual! I know there are a few!) and Simone “Som” Pluijmers is just superb. The only shame is that the band didn’t have a good PA sound, but they were tight and I would have liked them to play longer. The vocals live are just as powerful as on the album. The highlight of the evening was when I met Som!

Revocation [7] were completely new to me. I spent quite a while trying to work out if they were a thrash band or a death metal band. Either way they were very good. There was certainly some Slayer and some Metallica in their sound, as well as some some traditional death metal. I’ll be getting some albums by them sooner or later.

Job For A Cowboy [6] are just, Job For A Cowboy. Like marmite you either love them or hate them. They’re a great band musically. Most people are turned off them because they got big on the internet. They don’t have a great stage presence or a great live sound, but they were still quite good. Better than when they headlined with Whitechapel.

Dying Fetus [6] are ok. They certainly had the best PA sound. I only bought one of their albums as I knew they were headlining when Cerebral Bore were playing and I wasn’t overly impressed. Live they were much better, but I only caught half their set due to someone elses’ inability to hold their alcohol.

It’s time Som and the boys got their second album out really. So glad they came to Norwich though.






Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...