Category: uncategorized
Sign you’re back in the UK
Pink Floyd – Their mortal remains

All pictures here: https://www.flubu.com/blog/pictures/pink_floyd_tmr_jul_2017
We finally got to see the exhibition. I’ve had tickets since last year! We went to Byrons for lunch, then Humming bakery, then V&A, then the Lego store in Leicester Square. We wanted to go to Taro for dinner, but turns out it’s closed ??. We went to a little pub and had very acceptable pub grub (with shite service).
The Pink Floyd Exhibition: Their Mortal Remains is an immersive journey through the world of Pink Floyd. The show begins with a look at the band’s early digs gigging in London’s underground music venues and goes on to explore the making of their most famous albums – from Animals to Dark Side of the Moon.
The exhibition was conceived by the late Storm Thorgerson and developed by his Hipgnosis creative partner Aubrey Powell. Pink Floyd’s visuals are a key focus of the show – it is as much a celebration of the band’s iconic album art and theatrical live performances as it is their music. Scaled models of set designs are shown alongside inflatable puppets, music videos, animations, tour programmes and sketches for album covers, offering a look at the process and ambition behind the band’s visual output.
The exhibition begins with a look at pyschedelia and the counter-culture movement from which Pink Floyd emerged in the 1980s.
The space – with its black-and-white walls and trippy visuals projected on to the ceiling – highlights the strong influence of psychedelia on Pink Floyd’s visual output.
Circular screens are now a signature feature of Pink Floyd gigs. The band first used one in 1974 – lighting and production designer Arthur Max created a 40-foot wide screen for the band’s tour of France that was used to project animations by Ian Emes and film sequences by director Peter Medak.
Pink Floyd’s The Wall tour was an elaborate production involving large-scale inflatable puppets, eerie masks and a wall that separated the band from the audience.
The album follows the story of a troubled rock star who isolates himself from the outside world after struggling with loss, abuse and the breakdown of his marriage. Mark Fisher and Jonathan Park designed the live show based on sketches drawn up by Waters while illustrator Gerald Scarfe designed puppets based on characters depicted in the record. The original production visited 31 cities in 1980 and 1981 and a later tour featuring more advanced puppets ran from 2010 to 2013.
Waters’ early drawings are displayed in the exhibition alongside clay models of the show’s ‘Wife’ and ‘Mother’ inflatables and masks worn by children in the video for track Another Brick in the Wall. Suspended from the ceiling is a vast inflatable ‘Teacher’ created for the 2010-13 tour – the kinetic puppet highlights the scale of the show and hangs alongside a replica of the pink pig featured on the cover of Animals. Nearby are concept paintings by Scarfe for the teacher, which show him spewing bile into the mouths of young children.
Roger Waters conceived the cover design for Animals while driving through Battersea to record at the band’s studio in Islington. The image shows a bright pink pig floating over Battersea Power Station – a reference to both the record (inspired by George Orwell’s Animal Farm) and the phrase ‘pigs might fly’.
The shoot was an eventful one – the 40-foot pig broke free and drifted into the flight path for Heathrow airport. Flights were grounded, Powell was arrested and both the police and the Royal Air Force were sent out to recover the offending animal. (It eventually landed several miles away in Kent.)
A look at the release of Dark Side of the Moon and the album’s iconic artwork closes the exhibition’s opening section. The artwork was a departure from the surreal photographic images created by Hipgnosis for the band and is one of the most recognisable album covers of all time. (The album is also the band’s most successful, with around 45 million copies sold to date.)
An adjoining room contains a holographic installation based on the cover design. Visitors are invited to gaze at the installation while listening to Pink Floyd’s music on headphones – an oddly mesmerising experience that brings the instantly recognisable image to life.
Storm Thorgerson’s cover for Pink Floyd’s 1994 album The Division Bell is inspired by the idea of communication. The image was shot in a field in Ely and shows a pair of metal heads facing each other as if engaged in conversation.
Images from the shoot are shown alongside Thorgerson’s sketches and six-metre tall models created for the Division Bell tour.
The cover for album Wish You Were Here shows a man being set alight as he shakes hands on a business deal. Like the artwork for The Division Bell – and many of Hipgnosis’ covers for Pink Floyd – it was created for real and the man really was set on fire.
The powerful image is projected on to a wall in the exhibition. It is displayed alongside the original photograph and images from the shoot that show assistants standing by with fire extinguishers. An accompanying manuscript written by Thorgerson explains the creative process and concept for the artwork.
As well as celebrating Pink Floyd’s experimental approach to visuals, Their Mortal Remains highlights the band’s innovative use of new technologies. The band was one of the first to use synthesisers in their music and a Mini Moog synthesiser owned by Richard Wright is displayed alongside hand-painted drums and custom guitars. A glass-fronted display includes over 50 instruments while an interactive element allows visitors to mix their own version of the track Money.
The exhibition opens with a larger-than-life model of the band’s Bedford Van. The replica is over twice the size of the original vehicle that the band used while touring in the early 1960s. It’s a lovely way to kick off the show – inside the model is a hand-written letter from Roger ‘Syd’ Barrett to his then-girlfriend with a small picture of the freshly painted van. “When I got back to London tonight the others had painted the van with a white stripe, which looks good with our name on it,” Barrett writes.
Capturing the scale or impact of a Pink Floyd gig in an exhibition space is an impossible task – the band played to vast audiences in some of the world’s biggest arenas – but a performance room at the end of the exhibition aims to give some sense of the spectacle. Footage of the band performing Comfortably Numb at Live 8 (their last performance on stage together) plays out across multiple screens while sound blasts from 18 loud speakers and seven sub woofers. It’s a suitably ambitious ending to a spectacular show.
We’re doing a bad thing
We’re going shopping when we’re drunk and hungry this is bad.
We’re not drunk and hungry.
OK, we’re tipsy and peckish.
[recipe] Espresso vodka
We saw this at John Lewis. For the price, it’s going to be a lot cheaper to DIY.
Lightly crush coffee beans in a mortar and pestle and drop them into your infusing vessel at a ratio of 1/4 cup beans per 2 cups (500ml) vodka. You can optionally add 1 tbsp brown sugar. Pour vodka over top and seal tightly. Let the coffee beans infuse for 2-4 days.
Place strainer over a bowl. Pour the coffee vodka over the strainer to remove the solid pieces and stop the infusing process. Pour the vodka back into your infusing vessel and seal to store.
Garden camping

Ben wanted to camp out with Katy. It’s been 30 minutes and I can still hear his mouth flapping away.
Happy 150th Canada Day
When you decide to be bored
On the train to the airport, we all decided that we weren’t going to stare at screens. It kind of got to is…

[recipe] Homemade yogurt
Yogurt making is so simple that it should become part of a weekly routine. All that is required is to heat a pot of milk until it steams, let it cool down a bit, and stir in some yogurt to act as a starter. Then leave the pot in a warm place to ferment.
That’s it.
During fermentation, the milk thickens into something delectably custardy and satiny smooth, with a clean, fresh, tangy flavor that is even better than the fancy artisanal stuff — a pretty big payoff for what ends up being about 10 minutes of active work.
Here are a few little tricks to make the process go seamlessly.
The first is to rub an ice cube over the inside bottom of the pot before adding the milk. This keeps it from scorching as it heats.
Next is that where the pot of milk ferments doesn’t really matter as long as it’s warm. Try placing it in a turned-off oven with the oven light on, in a corner swathed in a heating pad, on the countertop wrapped in a big towel, and tucked on the top of the fridge. They all work, though the warmer the spot, the more quickly the milk will ferment.
Once the yogurt thickens and you think it may be ready, taste it before you stick it into the refrigerator. If it seems too mild, let it sit out for another couple of hours to increase the tanginess. You can leave it for up to 24 hours at room temperature if need be without worrying about spoiling.
To make Greek yogurt, the finished yogurt is left to drain in a colander lined with cheesecloth.
INGREDIENTS
1l whole milk, the fresher the better
3 to 4 tbsp plain yogurt with live and active cultures
PREPARATION
Rub an ice cube over the inside bottom of a heavy pot to prevent scorching (or rinse the inside of the pot with cold water). Add milk and bring to a bare simmer, until bubbles form around the edges, ~90C degrees. Stir the milk occasionally as it heats.
Remove pot from heat and let cool until it feels pleasantly warm when you stick your pinkie in the milk for 10 seconds, 40C-45C. Transfer 1/2 cup of warm milk to a small bowl and whisk in yogurt until smooth. Stir yogurt-milk mixture back into remaining pot of warm milk.
Transfer to a 1L mason jar. Wrap jar (without lid) in 2 clean kitchen towels, completely covering sides and top. Let stand undisturbed in a warm place until yogurt has the consistency of custard, 4 to 12 hours. The longer it sits, the thicker and tangier it will become.
Refrigerate uncovered jar; when it’s cool to the touch, about 30m-1h, screw on a tight-fitting lid.
To make moka yogurt:
1/3 cup strong brewed coffee
4 Tbsp cocoa powder
2 Tbsp sugar, or to taste (note: maple syrup is a great substitute! try 2-4 Tbsp)
Mix together and combine well, then mix in to 2 cups of yogurt.
Empathy for the coder
You read through the code. You read it again to make sure you understand what it’s doing. Your left eye starts twitching. You read the code a third time.
“WTF was wrong with the person who wrote this?”
I hate how often I react this way. It’s a quick default that’s hard to reset — immediate annoyance as if the developer or engineer responsible for writing whatever I’ve come across was scattering landmines. It’s easy to shit on the people who came before you. They’re usually not around to defend themselves or provide context. It’s much harder to calm down, and think things through. An initial reaction of “WTF?!” is entirely valid (You’re gonna feel what you’re gonna feel.), but getting stuck on the frustration and not going further is unfair to your predecessors and causes you to miss out on learning.
“How” a problem was solved/band-aided/kicked-down-the-road is usually the root of those frustrations, but the next step is thinking through the “Why” of the solution, which is often the source of useful information.
The code might be stupid, but there’s usually a reason. Maybe:
- Something stupid upstream brought its stupid with it. Alternatively, something stupid downstream needed more stupid.
- The dev/engineer was told to do it that way.
- The dev/engineer was getting pulled in 1000 different directions and needed to make a fast band-aid.
- The dev/engineer was doing the best they knew how.
- It’s actually not stupid. You just think you know more than you do.
That doesn’t rule out laziness or malice, but they’re much rarer and shouldn’t be the default assumption. When we run across goofy looking code and configs, we need to respect the constraints and context the person who wrote them faced. Note: That the person might actually be an idiot is a real, intractable constraint. How would you have fixed that?
Thinking through and learning the “whys” that caused the stupid will help you understand the context of the problem you’re currently facing. You’ll learn about not only technical pitfalls, but cultural ones as well. A lot of the stupid that shows up in code has nothing to do with the technical competence of the person who wrote it and everything to do with their manager or the company at large.
How many times has the past version of you done something stupid that harmed future you? How many times have you looked at something you made a year ago and thought “What was I thinking?” Like any skill, if you’re not embarrassed by some of the code and configs you’ve written in the past you’re 1.) an egotistical monster, and 2.) not getting better. Knowing that, allow some grace for yourself and the people who came before you.
I can’t say I’ve mastered this skill yet. Sometimes, in moments of frustration, I flat out suck at it. But I’m trying and that’s kind of the crux to all this. Everyone is trying, no one has arrived, and the more we empathize with the unknown constraints of those who came before us, the better off we’ll be.
Adapted from original link

















