Dave Cross posted a photo:

via Instagram instagr.am/p/CTwR3eXKRWR/

Dave Cross posted a photo:

via Instagram instagr.am/p/CTdEamJqDb2/

Dave Cross posted a photo:

via Instagram instagr.am/p/CTdDP4tq1uj/

Dave Cross posted a photo:

via Instagram instagr.am/p/CTc78N8qSNt/

Dave Cross posted a photo:

via Instagram instagr.am/p/CTc4pk9KlEv/

At about this time of the year, I usually write an overview of the gigs I’ve seen in the year. The post always starts with me saying how many gigs I’ve seen during the year. This is the tenth year I’ve been writing these posts and in that time I’ve seen between 35 (2018) and 60 (2013) gigs in a year.

This year, I’ve seen four gigs.

I’m going to add in a strange gig-cum-lecture that I saw a couple of weeks ago in order to list the top five gigs I saw this year. Here they are in chronological order.

• John Grant at the Roundhouse
  This is the second time I’ve seen John Grant live. The first time (at the Hammersmith Apollo a few years ago) he had a full band with him, but this time it was just him and a pianist. It was a great start to my gig-going year. I also had a ticket to see him at Alexandra Palace later in the year, but that show has already been postponed twice.
• Hate Moss at the Old Blue Last
  I don’t go to the Old Blue Last enough. It’s a tiny room above a pub in Shoreditch and every time I go there I have a really good time. This time I was drawn there because one of the support acts (M-orchestra) is an old colleague from the BBC who had just started gigging again after a long hiatus. He was great (check out his streams on Facebook) and the fact that the other two acts on the bill were also very good was a bonus.
• Ladytron at Heaven
  Another show I went to because of the support act. I try to see Stealing Sheep whenever I can so I bought a ticket for this just knowing they were on the bill. If you know anything about my musical taste then you’ll probably be surprised that I had never listened to Ladytron before buying the ticket. I investigated them before the gig and found an amazing band who I’ve been listening to a lot ever since. That’s Ladytron in the photo at the top of the page.
• Tove Lo at the Forum
  I saw Tove Lo at Mighty Hoopla in Brockwell Park in 2019. I’m not much of a festival fan but I enjoyed her and added her to my list of people to see indoors as soon as possible. This was that show and it was pretty enjoyable stuff, but subsequent events mean it has taken on rather more importance than it might otherwise have enjoyed.

I saw Tove Lo on March 12. Eleven days later, Boris Johnson put us in lockdown and my inbox turned into a sea of cancellations and postponements. I had a full schedule of upcoming gigs booked, but they’ve all been either cancelled or postponed until next year (or, in a couple of cases, 2022). I watched a couple of streamed gigs, but it’s really not the same at all. I have, however, sneaked in one more kind of gig in between London lockdowns.

• Brian Cox and the BBC Symphony Orchestra at the Barbican
  I don’t usually include classical shows in these lists. To be honest, I don’t go to a lot of classical concerts as it’s mostly not my thing at all. But this was a bit different. Brian Cox gave some brief “mini-lectures” between classical pieces that had been chosen to tie in with the questions that he raised. It was a strange show. Probably about a quarter of the seats at the Barbican were used (they sold online tickets too), walking around the venue was very tightly controlled and there was no interval. They even expanded the stage into the stalls in order for the orchestra to be socially distanced. The concert is available on the BBC web site for a few weeks if you’d like to hear it.

So what does 2021 hold? Well, it’s hard to be sure. I’ve got a fistful of tickets for shows that were postponed from 2020 but, at this point, I wouldn’t like to guess which ones I’ll actually get to see.

What about you? What did you get to see before the venues all closed down? What are your predictions for how things will go next year?

The post 2020 in Gigs appeared first on Davblog.

[Update: the CPAN Request Tracker was saved. It’s now run by a new team of volunteers and none of my suggestions below are required.]

Two weeks ago, we learned that the CPAN Request Tracker was closing down early next year. I proposed a plan that CPAN authors could follow to ensure that their users can still find somewhere to report bugs in modules (and, perhaps more importantly, to see what bugs have already been reported in modules).

But that’s only part of the problem. In fact, it’s probably a minor part of the problem. If you’re an active CPAN author, then you probably already knew about the impending closure and had already made plans to deal with it. It’s likely that you had already moved your bug tracking to a new system. At the very least, you now know what the problem is and are considering the best way to deal with it before next March.

The far larger problem is the thousands of distributions that aren’t owned by active CPAN authors. What are we going to do about those?

How big is the problem? Well, the site cpan.rocks displays stats about CPAN. One of the panels on its front page shows a summary of the bugtracker information in CPAN distribution. You’ll see that 24,873 distributions (that’s 66% of them) have no bugtracker information included in their metadata. That’ll be for a number of reasons. Some of them will be distributions that haven’t been updated since alternative bugtrackers were supported by CPAN (originally, it was just assumed that everyone used the CPAN RT); some of them will be because the authors don’t know how to add the required metadata; and some of them (including most of my distributions) are missing it because the author just hasn’t got round to adding it yet. There will, of course, be many more reasons.

Some people will have read the recent news and will be galvanised into doing something about it (I fall firmly into that category) but others (and I’d suggest that it’s a large majority) either won’t hear about the change or won’t care about it. And why should they care? They were generous enough to donate some of their code to CPAN at some point. They don’t have any obligation at all to carry on maintaining it after they’ve lost interest in whatever project led to them writing that software.

Take, for example, Mail-Alias. That was released by someone called Tom Zeltwanger twenty years ago. He released three versions over a period of two months and then stopped. Who knows why. When he last updated the module, the CPAN search engine didn’t support alternative bugtrackers, so he never considered adding one. And that meant that the CPAN page for his module linked to the default bugtracker set up for the distribution on the CPAN RT. In the last fifteen years, four bugs have been reported against that module. But as Tom has moved on, nothing has been done about any of them. There are a lot of modules on CPAN in a similar situation.

But that leaves MetaCPAN (the current CPAN search engine) with a problem. Where does it send people who want to report a bug against an inactive module?

You might think that it doesn’t matter. But I disagree. Maybe I think that Mail::Alias would be the perfect module for a project I’m working on. Even before I start using it, it’s useful to be able to browse any existing bugs to see how they might affect my use of the module. And if someone later comes along and wants to take over maintenance of the module, then it’s useful for them to see any bugs that have been raised during the hiatus when the module was unmaintained.

So, I’m a big fan of having a default bugtracker for CPAN modules – even for ones with inactive authors. Which leads us to the question of where should that be. And I have a suggestion.

A few years ago, Micheal Schwern and Olaf Alders set up Gitpan. It’s an organisation which has a Github repo for every distribution on CPAN. And those repos each have a commit for every release of those distributions. Here, for example, is the repo for Mail-Alias – and you can see the three commits for the three releases I mentioned above.

So I’d like to suggest Gitpan as a suitable place to use as a default bugtracker for CPAN distributions. There are a couple of problems:

• It looks like the auto-population of the commits stopped a few years ago. We’d need to work out how that works and catch up on the recent uploads.
• None of the repos has the issue tracker turned on. But I expect that can be done with a relatively simple program that uses the GitHub API.

Of course, we also have the problem that some people object to using GitHub since it was taken over by Microsoft. But that’s fine, they can just point their bugtracker metadata to their preferred system.

The problem with the CPAN RT was that it needed too much maintenance – and the Perl NOC team is really overworked. Any self-hosted alternative seems likely to have the same problem eventually. So I’m all in favour of using a third-party alternative. And if you’re taking that route, then it makes sense (to me, at least) to use a third-party system that already has all (ok, most) of the repos set up.

I haven’t spoken to Schwern or Olaf about this, so I don’t know if there was some major problem that would stop this plan from working. But I think it’s worth looking at.

The post Replacing CPAN RT appeared first on Perl Hacks.

CPAN RT is going away. CPAN authors have until the beginning of March to extract any useful information from it.

RT is the “Request Tracker”, a bug tracking system that is written by Best Practical. For almost as long as I can remember, anyone who uploads a module to CPAN gets a free ticket queue for their module at rt.cpan.org. MetaCPAN assumes that’s where people should report bugs in your module and helpfully adds an “issues” link that goes to the appropriate page in RT.

But now that system is going away. It will be switched off on the 1st March 2021. The Perl NOC team is spread pretty thinly and they just don’t have the resources to keep it running.

Gabor has published a video talking about what this means and some of the potential problems. But I thought it would be useful to work on a list of things that CPAN authors should be thinking about over the next three months.

Firstly, and most importantly, you’ll need somewhere new for people to report problems with your modules. For most people, that’ll be simple enough. If you host your code repos somewhere like GitHub, then you could just use the issue trackers that most of those services provide. If you host your own code repos (or don’t have public code repos), then you’ll need to find an alternative solution.

Next you’ll need to tell people where to find your new bug tracker. You do this by adding it to the metadata for your CPAN distribution. If, like most people, you provide a Makefile.PL in your distribution, then you’ll want to add a snippet like this to your code:

META_MERGE        => {
  'meta-spec' => { version => 2 },
  resources => {
    bugtracker => {
      "web" => "https://github.com/davorg/moox-role-json_ld/issues"
    }
 },

It’s likely that you already have a “resources” key in your data structure (containing, for example, a link to your code repo), in which case you just need to add the “bugtracker” key inside it. When you release this new update to CPAN, the “issues” link will change to point to your new bug tracker.

You then have the problem of dealing with the tickets that are currently in your RT queues. I suggest one or more of the following strategies:

1. Go through the list and fix any that can be easily fixed. I found two like that when looking through my list this morning. If you’re releasing new versions of the modules (to add the new bug tracker information) then you might as well fix a bug or two at the same time.
2. Look for tickets that can be closed. My list contains some very old tickets. I mean like fifteen years old. If someone had a problem installing one of your modules fifteen years ago and hasn’t followed-up more recently, then there’s a good chance that they no longer care about the solution. What I’ve been doing is to check on CPAN Testers to see if anyone else has seen a similar problem. If I see other reports, I know that it’s something that needs to be fixed. If there’s just the one in RT, then I close it with a message saying (paraphrased) “if this is still a problem that you’d like me to investigate, then please open a new ticket at [link to new bug tracker]”.
3. Then you’re left with the tickets that you’d still like to address at some point. The Perl NOC team say that they’ll probably make a static archive of the old RT tickets available. But it would be good to get those tickets over to your new bug tracker. As I’m using GitHub for my new bug trackers, and that’s currently the most popular solution other than the CPAN RT itself, I’m hoping that someone cleverer than me will write some code that will make moving the tickets easy. But if nothing happens before the end of January, I might have to look into that myself.

I’ve got a bit of work to do in this area myself. Although I’ve been using GitHub for all of my CPAN code for a long time, I haven’t been advertising the fact that I’d prefer people to use GitHub for bug reporting too. So I need to update all of my modules with the new bug tracker information included. I’ll do that over the next few weeks.

I have a couple of tools that might help in this process. Firstly, I’ve just added to CPAN Dashboard a column that links to the module’s bug tracker if one exists. I can use that to know which modules need to be updated.

You could add yourself to CPAN Dashboard if you wanted to get that information for your modules. But if you don’t want to do that, I’ve written a really short program that you can use to find your CPAN distributions that don’t include the bug tracker information. It’s available as a Gist.

Have I missed anything? I mean, yes, I know there are a large number of unmaintained CPAN distributions that no-one will get round to updating. But this post was aimed at active CPAN authors. If there’s anything else you think we should be doing, then please let me know in the comments.

The post RT – Action Plan for CPAN Authors appeared first on Perl Hacks.

Blog posts are like busses. You wait months for one and then two come along on consecutive days!

Yesterday I wrote about how we didn’t need a blogging platform for the Perl community – all we really needed was a good-looking feed aggregator. I mentioned Perlsphere as one such aggregator.

Then Matthew commented, saying that Perlsphere looked a bit broken as Dave Cantrell’s posts from a few years ago frequently pop up there as new posts. I had a quick look at the problem and couldn’t quite work out what was going on. His web feed seems valid, but Perlsphere didn’t seem to recognise the dates of the posts.

Perlsphere is implemented using Plagger, a feed aggregator written by Miyagawa a very long time ago (back when it seemed that web feeds were going to conquer the world). It’s a pretty complex beast and it seemed possible that somewhere deep in its code, it was mis-parsing Dave’s web feed. So I cloned the repo and tried to work out what was going on.

But Plagger hasn’t been updated for a very long time. As you can see from the test results, it stopped passing its tests a long while ago (I suspect when the current directory was removed from @INC). I spent a brief time trying to get it working but, ultimately, decided it was too hard a job.

So I took another look at Perlsphere. And I decided that if it’s based on bit-rotten software, it’s not going to be very easy to maintain (which gave me flashbacks to blogs.perl.org!)

But there’s another Perl tool for aggregating web feeds. And I wrote it. It’s called Perlanet (and, boy, do I regret that name now). Back in the first decade of this millennium, I was fascinated by web feeds and the idea of using them to build local “planets” – a web site that aggregated web feeds that had interesting information about your local area. Of course, that was back in the days when everything had a web feed and it was simple enough to pull them together and create really quite interesting sites. These days, of course, web feeds are rather unfashionable and almost no-one thinks to add them on to their web site.

However, they still cling to life in the world of blogging. Mainly, I suspect, because blogging platforms added them fifteen years ago and just haven’t bothered to remove them yet. And it’s blog posts that we’re interested in here – so we’re still in with a chance of building something useful.

And that’s what I did over lunch. I give you Planet Perl, a new site for aggregating Perl blogs.

Currently, it only has four blogs in the configuration. But the config file is on Github and I’ll be happy to get pull requests adding other blogs.

I hope you find it useful.

The post Down the rabbit hole appeared first on Perl Hacks.

I think it was at YAPC Copenhagen in 2008 that a small group of us first discussed the idea of building a shared blogging platform for the Perl community. It was over a year later that we launched blogs.perl.org.

I remember a lot of discussions over that time where we tried to thrash out exactly what we wanted to build. I know that one of my main drivers was that I wanted to replace the journals feature of use.perl. For those of you too young to remember, use.perl was a Perl community web site from the dawn of time. The site ran Perl news on its front page, but users could also have their own journal. For a few years, we had a nice little blogging community on the site. It used the same software as Slashdot and, like Slashdot, was looking pretty dated at the time. I remember being particularly disappointed that you couldn’t put images in a journal entry.

So that was certainly where I started from when planning blogs.perl.org. I wanted a modern blogging platform to replace use.perl. Other people wanted slightly different things. At least one person argued strongly that what we really needed was a nice-looking blog aggregator and that people could do their actual blogging on their own sites (or some other blog provider).

But, as you can see, that point of view lost out and we implemented a full blogging system using Movable Type.

Ten years on, I think that was a mistake. I think that having a community blogging platform for Perl is actively harmful to Perl.

I’ll explain why a bit later, but first let’s talk through a bit of more recent history of the site.

It’s well-known, I think, that the site is not is a good state. I’m happy to explain what happened there, but it’s a long and rather dull story. There have been a couple of attempts to build replacement systems but they both stalled before they were complete.

So we’re left in a situation where the site is broken and no-one really has the time or the expertise to fix it. And attempts to replace it seem doomed to failure.

Earlier this year I decided that the situation was untenable and that I wanted to close the site down. I spoke to Aaron and he pretty much agreed with me. We decided that we’d give people plenty of notice to take their blogging elsewhere and, rather than closing the site completely, we would make it read-only (so all the existing content would still be there). We ran the idea past the rest of the loose “management team” and Aristotle spoke up, saying that he would rather take the site over himself and try to improve matters. And that’s what happened. Over the last few months, Aaron and I have extricated ourselves from running the site and it’s all now handled by Aristotle.

I wish him all the best in those endeavours and really hope he manages to make the site better than it was (he’s already making great progress in removing loads of old spam blogs from the site).

But, really, I think that my original plan was a better idea. I don’t want people to blog about Perl on a Perl community site. I want people to blog about Perl on sites where people blog about other languages and technologies.

I’ve been giving talks about the need for the Perl community to break out of its echo chamber for almost as long as I’ve been part of the community. But I think it’s important. It’s a kind of low-key marketing. If you’re talking about your cool Perl project on a Perl community web site then only people who are looking for Perl articles will find it. But if you blog about it on a general programming web site then a) you’ll get a far bigger audience and b) some of that audience might say “oh! I never knew Perl could do that – perhaps I’ll give it a closer look.”

And that’s why I think blogs.perl.org (and, probably, use.perl before it) are harmful to Perl. It encourages Perl bloggers to blog for the Perl community – when it would be far better to get your blog posts in front of more people. Perl people will still read your Perl posts (through Perlsphere perhaps, or post the link to /r/perl or the Perl Community Facebook group) but other people will see them too. On blogs.perl.org, you’re pretty much guaranteed that only Perl programmers will see your posts.

To be honest, I don’t understand why people still use blogs.perl.org. Until Aristotle’s work bears fruit it’s painfully broken. What do you get that’s worth putting yourself through all of that pain? Why not just blog somewhere else and submit your web feed to Perlsphere? Or blog where other programmers blog – somewhere like dev.to, perhaps (I’ve started publishing my more technical blog posts there).

I think it will be great if Aristotle gets blogs.perl.org working well. I really want that to happen. But it would be even better if he didn’t have to. If people stopped using it; if they went off and started spreading their interesting Perl blog posts all over the web.

Break out of the echo chamber. Find yourself a bigger audience. Spread the word beyond the Perl community.

Or, alternatively, explain to me why it’s so vital that the Perl community has its own centralised blogging platform.

The post Blogging for Perl appeared first on Perl Hacks.

author: Mary Roach
name: David
average rating: 3.75
book published: 2008
rating: 0
read at:
date added: 2020/04/27
shelves: currently-reading
review:

What do you do when you’re stuck inside because Coronavirus means that your country is in lockdown? Well, you write a book, of course. Or, to be more accurate, you cobble together fifty or so old blog posts into a book.

So that’s what I’ve done. Now you can read some of your favourite Perl Hacks blog posts in a handy Kindle book. Other ebook marketplaces are, of course, available – but I haven’t had the time to make a version that’s available from anywhere else yet. That might follow if enough people ask for it.

The book is, predictably, called The Best of Perl Hacks and it’s available from Amazon now (that link goes to the UK store, but it should be available on all Amazon sites).

Please buy it, read it and let me know what you think.

The post The Best of Perl Hacks appeared first on Perl Hacks.

Here are brief descriptions of the various cultural things I did in the second half of January 2020.

Food: 12:51 (Islington, 2020-01-18)

Our second visit to 12:51, but the first time we tried the tasting menu. It’s a bit pricy (£75 a head, I think) but it’s well worth it. The food was wonderful. And on the night we were there, James Cochran (the chef who owns the restaurant) was there – although he was serving, rather than being in the kitchen.

Food: Wolkite Kitfo (Holloway, 2020-01-24)

This is an Ethiopian restaurant near Arsenal’s new stadium. Ethiopian food is really interesting. It’s usually served piled up on a flatbread called injera. You then tear off bits of the injera and use it to scoop up bits of the food and put it in your mouth. So the injera doubles as both plate and cutlery. If you’re interested (and I think you should be) then this is a nice local restaurant in which to try it.

Art: 24/7 (Somerset House, 2020-01-29)

The subtitle for this exhibition is “A wake-up call for our non-stop world”. The pieces here all examine the way that the world has changed over the last twenty years so we are now all more connected much more of the time and how that has affected us. It’s a very thought-provoking exhibition and I highly recommend you seeing it.

Film: The Personal History of David Copperfield (Screen on the Green, 2020-01-29)

I’ve never read David Copperfield. I don’t remember even seeing another film or TV adaptation. So I was probably one of very few people in the cinema who didn’t know the plot. And, therefore, I have no idea how much this film deviates from the book. It certainly feels like a rather modern take on the book (although it’s very much set in the nineteenth century). There’s a great cast and a cracking script. I loved it.

Gig: John Grant (Roundhouse, 2020-01-29)

I love John Grant’s music and see him live whenever I can (I already have a ticket to see him again at the start of May). This gig was part of the Roundhouse’s “In the Round” where artists play to an all-seated audience. This was a stripped-back set (just John on piano and a keyboard player) which meant that some of his more complex songs were skipped. But he played everything I wanted to hear – even finishing with a great version of “Chicken Bones”.

Gig: Hate Moss (Old Blue Last, 2020-01-30)

It is many years since I was last at the Old Blue Last for a gig. I was drawn back by an old friend who was first on the bill, playing as M-Orchestra. I stayed on to see the other two acts. Kill Your Boyfriends were a bit noisy for my tastes, but Hate Moss were well worth staying out for. I’ll be looking out for them playing London again.

Dance: Sadlers Wells Sampled (Sadlers Wells, 2020-01-31)

I’ve been in London for over 35 years and I’ve never been to Sadlers Wells. And if you’re going to fix that, then it makes good sense to go on a night where there’s a selection of different types of dance on display. There were eight different acts during the night – from traditional Indian dance and tango to really experimental dance from Company Wayne McGregor and Géométrie Variable. I’m no expert in dance and this was a great introduction to the breadth of options available.

The post Consuming Culture: 16-31 Jan 2020 appeared first on Davblog.

author: Beth Buelow
name: David
average rating: 3.50
book published: 2015
rating: 0
read at:
date added: 2020/01/27
shelves: currently-reading
review:

I want to do more blogging this year. So one thing I’m going to do is to write about the cultural experiences that I have. My plan is to write short reviews of any films, plays, exhibitions and lectures that I go to. To start us off, here’s what I did in the first half of January.

Film: Last Christmas (Vue Islington, 2020-01-01)

Yes, this got some terrible reviews, but cheesy romcoms are a bit of a guilty pleasure of mine. This isn’t up to the standards of Four Weddings and a Funeral or Notting Hill, but I really enjoyed it. And I don’t care how much you judge me for that.

Art: Wonder Factory (Dalston Works, 2020-01-03)

This was weird. Fifteen rooms have been turned into Instagram-friendly art installations. They are of variable quality, but the best installations (like the marshmallow swimming pool) are very good. It’s only around until early February (and it seems they’re now only opening at the weekend) so you should get along to see it soon.

Film: Jojo Rabbit (Screen on the Green, 2020-01-05)

The Hitler Youth isn’t the most obvious subject for comedy, but this film manages to pull it off brilliantly. It’s obviously a very delicate balance but director, Taika Waititi, gets it spot on – while also playing a very funny imaginary Adolf Hitler. I see this has been nominated for the Best Picture Oscar; and that’s well-deserved.

VR: Doctor Who – Edge of Time (Other World, 2020-01-05)

Other World is a virtual reality arcade in Haggerston and currently, one of the VR experiences they are offering is the Doctor Who game, Edge of Time. Players are put in their individual pods and loaded up with all their VR equipment (headset, headphones and a controller for each hand) by staff before being left alone to help the Thirteenth Doctor save the universe. I confess I got a bit stuck trying to get the Tardis to dematerialise, but I really enjoyed myself and am very tempted to go back for another try.

Play: A Kind of People (Royal Court Theatre, 2020-01-06)

The Royal Court has a brilliant scheme where they make tickets for Monday evening performances available for £12 each. That price makes it very tempting to see plays that you know nothing about. And that’s what we did for this. We really had no idea what this play was about. It turns out that it’s an investigation of the various prejudices (racism, sexism, class snobbery, …) that bubble under the surface of British society. I’d recommend you go and see it, but it closes in a couple of days.

Meeting: Tech For UK Post-Election Debrief (Onfido Ltd, 2020-01-08)

I want to get along to more tech meet-ups this year and this was my first. Tech For UK is a group of techies who volunteer their time to build tools that increase democratic engagement in the UK. You can see some examples at voter.tools (this includes my site – TwittElection). This meeting was a discussion about what the group had been doing during the election campaign and where they should focus their efforts in the future.

Art: Bridgit Riley (Hayward Gallery, 2020-01-15)

I want to make more use of my South Bank membership, and this was a free after-hours, members’ viewing of the exhibition. This is a retrospective of Riley’s whole career and, therefore, is a great introduction to the breadth of her work. She’s a fascinating artist (if one who occasionally produces art that can give you a bit of a headache). I recommend seeing the exhibition – but hurry, it closes on 26 January.

The post Consuming Culture: 1-15 Jan 2020 appeared first on Davblog.

It’s time that I wrote my now-traditional review of the gigs I saw last year.

It felt like I didn’t see so many gigs this year, but Songkick tells me I saw 43 which was more than the previous year (but still some considerable way short of the 60 I saw in 2013). I’ll get to the best ones in a minute, but let’s talk about a few of the disappointments first.

The first gig I saw in the year was the Residents at the Union Chapel. I wasn’t really sure what I was expecting, but it was all a bit disjointed and amateur-sounding, so I left before very long. Having really enjoyed the Bananarama reunion tour a couple of years ago, I was looking forward to seeing them (now Siobhan-less) again, particularly at a lovely little venue like Omeara – but they were a terrible disappointment and wanted to play their new album instead of the hits that I wanted to hear. I really wanted to enjoy the post-Pete Shelley Buzzcocks show at the Albert Hall, but it was a lot like a third-rate Buzzcocks tribute band and I left quite a while before the end.

And here, in chronological order, are my ten favourite gigs of the year.

• Tears For Fears: This was postponed from the previous year. It takes a good band to make it worth going to the O2 Arena. And Tears for Fears certainly hit the spot.
• Desperate Journalist: An up and coming band that I really want to hear more from. Oh, and they were supported by She Makes War, who is always worth seeing.
• Grant: This was a slightly strange one. A night of Scandinavian music at the Lexington. We went because we wanted to see the first act, Moses Hightower (who were great). Grant was on next and she totally blew us away. I think we left soon after she finished.
• Stealing Sheep: I don’t get to see Stealing Sheep as often as I used too, but they were touring this year because of their new album. I saw them twice. I enjoyed the show at Earth in Dalston the most. That’s them in the photo above.
• Sleeper: I never got to see Sleeper back in the 90s. But I saw them twice this year. I think I just prefered the show at the 100 Club.
• Swimming Girls: I’ve seen Swimming Girls as a support act and really wanted to see them playing a headline show. I finally got to do that at the Lexington this year. And then they announced they were splitting up.
• Cut Copy: A band that I hadn’t heard of at the start of this year. But this show at Somerset House was great and I’d certainly see them again.
• Sunflower Bean: I always love seeing Sunflower Bean and this was at the Borderline (just before it closed down) and I thought the days of seeing them in venues this small were long past.
• Midge Ure: This was pure nostalgia. Midge Ure’s current band played all Visage’s first album and Ultravox’s “Vienna” – two albums that he recorded in 1980.
• Amanda Palmer: This wasn’t really a gig. It was more of a four-hour-long, intense psychotherapy session with occasional songs. I saw the prototype for this show in Edinburgh last year, but the full version was sensational.

Just outside of this list are shows by Pale Waves, Lloyd Cole, Wildwood Kin and OMD.

Oh, and I have a new regular gig-going companion this year. I asked her what her favourite gig of the year was and she voted for the Grant show at the Lexington.

2020 is already shaping up well. I have tickets to see John Grant (twice), Tove Lo and Ladytron. And there’s some heavyweight nostalgia coming – with gigs by the Pet Shop Boys and Bauhaus.

What about you? What live music did you really enjoy in 2019?

The post 2019 in Gigs appeared first on Davblog.

I’ve been working in this industry for a long time – over thirty years. For most of that time, I’ve been working as a freelancer, but it’s always been working for someone else. When I set up Magnum Solutions (my freelancing company) in 1995 I always had a vague desire to grow it into a company that wasn’t just me selling my time and skills to other companies. But I’ve never really known how I wanted to do that.

On the other hand, I’ve spent a lot of those thirty years building web sites in my spare time. Whether it’s my (now, long defunct) BBC Streams project or current sites like Line of Succession or TwittElection, there’s always something that I’m tinkering with. Some of them get some small level of popularity. None of them has ever made me enough money that I could consider giving up the freelancer life in order to spend more time on one of these projects.

This year has been slightly different. This was the year that the market for Perl freelancers in London finally hit the level at which I decided to take a permanent job. So I’ve been working for Equals (formerly FairFX) as a senior developer since February. But even that didn’t feel quite right. It felt a bit like a step backwards to go back to being an employee.

And then, while on holiday a month ago, something crystalised for me during a conversation with a friend. She asked how I’d really like to spend my time and I replied that I’d like to take time off from working nine to five and spent it trying to turn one or more of my side-projects into a real business. She asked what was stopping me from doing that and I replied that I didn’t have enough money. She laughed and asked me what the money in the ISA that I’ve been paying into on and off for the last decade was for. I’d always vaguely assumed it was for “the future” (whatever that means) but I realised that she was right. There was no reason at all why I shouldn’t use some of that money to support myself while I took time off work to do what I really wanted.

So that’s what I’m going to do. I’ve given notice at Equals and I’m leaving just before Christmas. And for the first six months of 2020, I’ll be living off my savings while I try to find some way to make a living from the various business ideas I’ve been doing almost nothing with for the last thirty years.

I’m going to be structured about it. I plan to try six things for a month each. I have an idea what the first two or three things will be but I hope you’ll forgive me if I don’t go into any detail right now. I do want to be very open about what I’m doing while I’m doing it – I’ve set up a new web site at davecross.co.uk and I’ll be writing about my projects there. Hey, even if nothing takes off, perhaps there’s a book in the reports of all my failures.

At the end of June, I’ll take stock and decide whether it’s worth continuing the experiment.

And that’s what I’m calling my “2020 Vision”. Because bad puns are the basis of good marketing – or something like that.

The post 2020 Vision appeared first on Davblog.

Some thoughts on ways to measure the quality of Perl code (and, hence, get a basis for improving it)

How (and why) I spent 90 minutes writing a Twitterbot that tweeted the Apollo 11 mission timeline (shifted by 50 years)

A talk from the European Perl Conference 2019 (but not about Perl)

author: Lindsey Bareham
name: David
average rating: 4.33
book published: 1999
rating: 0
read at:
date added: 2019/07/29
shelves: currently-reading
review:

author: Sean Platt
name: David
average rating: 4.29
book published: 2013
rating: 0
read at:
date added: 2019/06/24
shelves: currently-reading
review:

The slides from a half-day workshop on career development for programmers that I ran at The Perl Conference in Glasgow

A (not entirely serious) talk that I gave at the London Perl Mongers technical meeting in March 2018. It talks about how and why I build a web site listing the line of succession to the British throne back through history.