Looking at things to listen to
Over the Easter holidays, oh so long ago now, but at least this year still, we managed to park the children with the Großeltern for a happy few hours and to drive to the wholly unremarkable Black Forest town of St. Georgen near Villingen.
The town is, sorry to say, not much to look at. But it was the centre of two key industries as they rose and fell in waves; clock making, and record players. I'm not that much of a watch connoisseur, but I have always enjoyed audio and hifi, so when I saw the signs for the Deutsches Phonographisches Museum in St. Georgen, it was always going to be a place to visit.
| The famous Dual logo (from Wikipedia) |
A couple of ex-employees got together and put together a German phonographic museum in the St. Georgen town hall. It's a pleasant, light space on two floors, full of a record players from the very beginnings in the USA and France (Edison and Pathé), via the dominance of the German and Dutch manufacturers and through to the demise of Dual. Whilst the collection is ordered chronologically, we still felt that there was a lack of a "story" behind the industry. What helped its massive expansion, how it withered on the branch here in Germany and - for me, notably - how it continues to this day. There was no mention of current high-end record player production from the likes of Linn or Pro-Ject, and there was only a passing mention of new music formats (with no sign of an iPod at all).
The strangest thing for me from the collection was the sound. The main hall, with reception, is also the location of a small stage where a video of how records and music developed. This then booms across the whole collection, which I found rather distracting. Secondly, there was also a random selection of old LPs and singles with some rickety looking turntables - but no instructions as to whether playing them was permitted or not. We had the possibility of paying 1 Euro to watch a 1980s high-end turntable play and to spin around in its gyroscopic gimbal, but by that stage I didn't feel like I really wanted to.
What I wanted was something like an audio room, where we could hear how the old horn record players sounded, how a 1970's Dual turntable with the amplifiers of the day sounded, and how a modern system might sound. After all, that's what they were built for.
I fully understand the difficulties surrounding that - how to organise and to protect such systems from the grasping public - but perhaps the old chestnut of a bank of good quality headphones would be a start. (Update: I see from their website that they're holding a record playing evening on 11th May 2013. I'm not sure I can go, but it's exactly what I'd love to see - and to hear!)
I'd love to go back again in a few years, to see how and if they develop the collection. In the meantime, here are a few more smartphone photos for you to peruse whilst I try not to buy myself a Pro-Ject Debut Carbon...





Excuses manifold
This blog looks to be in grave danger of becoming an orphan; no writer to care for it, only the occasional glance in from human readers and data mining bots as they continue moving swiftly on to other digital destinations, only Google’s server farm keeping it from sinking into the digital abyss. A blogging pause has happened here before, of course, as noted in my Blogging State Of the Union post from October 2012. I’ve again not posted here for several months, obviously because nothing of interest has happened to me in that time.
Perhaps that’s right. The day-to-day has been pretty overwhelming and I’ve found that whilst trying to keep my engineering blog a little more lively, there’s simply not been the headroom, or quiet time, or energy to work on this here blog. But what about the content? Has that been lacking, too? Thankfully, I think not.
What have I been up to since Shanghai? Well, I played in another symphony orchestra concert (Gershwin, Shostakovitch and Rachmaninov’s 3rd Symphony). I remixed a Jamiroquai track for their 20th anniversary remix competition, we were served notice and had to find a new house to live in, I started jogging again… and again…, I worked, and took part in general family life.
Over the Easter holidays, I enjoyed visits to the Steim Automuseum and to the Deutsche Phonographisches Museum - which I will describe in another post - and I worked.
So, lots of excuses not to keep this blog ticking over: many of those excuses could easily have been made into entries in this online diary of mine, building up my insignificant history, for as long as the Blogger servers and HTML continue…
…anyway, enough mulling and pondering, enough slumping into sofas, and onwards with the writing!
Engineering Things Done
Phew, what a day! What a lot of days! Things are pretty mad at the moment and have me racing from one fire to the next whilst juggling the other less serious blazes. Things are probably more or less the same for you (unless you work in aerospace ;-)). We need to get things done all the time and seemingly all at once. Priorities rest on ever-shifting sands, cups of coffee are gulped without enjoyment, nerves are frayed.
Having lots to do at work is both a blessing and a curse: of course we want to be gainfully employed, but there is a point beyond which the sheer number of tasks that we are responsible for becomes overwhelming. As a result, efficiency sinks to its knees, even if we physically manage to stay on our feet.
This fact has been recognised by many and has become the basis of whole careers on advising people how to do manage tasks. I’ve been on Time Management courses, as I described over at Engineer Blogs last year, I’ve tried hiding myself in empty cupboard-sized meeting rooms without my phones and I’ve tried all sorts of tools like the Tasks list in Outlook to try and find a way out of the mess, mostly to no avail.
Help is at so many hands that it’s no help at all: there’s such an uncontrollable thicket of to-do apps, self-timer apps, of notation apps and (e-) books to be bought that these have become an industry in themselves. All in the name of getting things done.
Late last year I caved and bought the book with those words capitalised by Dave Allen: Getting Things Done. I read it, too - and came away rather impressed. It’s certainly a book of two halves (it feels a little like a ‘buy one, get one free’ deal, where you don’t necessarily want or need the free item), but the first half, where the concepts and mechanisms of Getting Things Done are explained is well worth the entry price. Mr. Allen has an incredible font of quotes that are splashed liberally throughout the book, too.
This isn’t a book review, though. It’s a process review, about Getting Things Done, or, as it’s now known in the trade, GTD.
In essence, the GTD methodology is about freeing up your mind, removing all the vague projects and to-do’s lodged quaking anxiously in your brain and onto physical or digital lists. The discipline of creating lists, of categorising, of sifting and sorting into whatever systems best suit you is geared towards relieving the mental pressures of non-started or incomplete tasks and towards focussing your attention on the next thing to do.
Next steps are a key element of Getting Things Done and recognising this goes a long way towards success. When I have to update a drawing, that is not a task itself, it’s a project. The next steps for me go along the lines of: Creating a new part number or release level in the system. Printing out the current drawing. Sketching up all the changes required: whilst I’m doing that I’ll realise that I need to pull a Change Request number, so I’ll need to go onto that system and generate a form and a number. That number goes onto the new print, which, once sketched up, goes to our CAD designer for modification. I wait. I get the print back for review. I make corrections, or I don’t - I send the drawing back if I do need updates, wait again (doing something else in the meantime), then switch focus back to the print once it’s finalised. Then I need to upload it and “publish” it… And so on.
Each one of those steps are all “small” things, but there are so many of them that constitute this mini-project called “update drawing xyz” that they easily clog up my mental passages (for want of a better turn of phrase). Listing the tasks out on paper or in some kind of digital software means that I don’t have to hold them in my mental buffer. Equally, I won’t have to worry about remembering where I am whenever a distraction occurs - a colleague walks in whilst I’m sketching and requires assistance (often setting off the next mini project of Things To Do), or quite simply when I’m waiting for that drawing to come back from CAD: I can quickly find the next open task and use that,
I’ve worked according to this methodology, applying the same logic to pretty much everything I do: ideas for new developments, testing that I need to do and subsequent reporting that I need to complete.
The general methodology works very well. It took some time to sift through my projects and my emails, but surprisingly quickly, I found a decent system of project taxonomy and began to see more and more white space in my inbox.
Tool-wise, I ended up using the browser-based software Asana, mainly because I wouldn’t need to install anything on my locked and stitched-up work laptop. Outlook is too stuffed to work for me. It has all the functionality - emails, notes, to-do’s, ability to drag and drop emails into Calendar and into Tasks - but somehow I need to escape the Outlook environment and keep things as focussed as possible - Asana provides this “cleaner” environment for me.
Up until mid January, I had a good set of lists and tasks, as well as an email in-box hovering around the zero level (each email is either archived or generates a set of tasks in my list setup). It was only when I embarked on a series of business trips - to Shanghai, to Kassel - and became sucked into a series of “urgents” that things started to subside back to the old ways of inbox infinity and anxieties everywhere I looked inside my head.
The focus of GTD is very much on mastering the low-level tasks. Dave Allen addresses this regularly in the book - he acknowledges that life-goal-setting (his “50,000 ft+ view”) is a way of finding orientation and goals in life; but if you’re mentally overloaded with pending things to do, you don’t have the headspace to creatively think about the bigger picture.
Get your everyday tasks under control, unload your mind of that burden, and the bigger picture has more room to grow of its own.
Honestly speaking, I’m a bit like a dieter here: bouncing from inbox-zero and being on top of things to feeling overwhelmed. I’m back at the overwhelmed phase, which is why I feel that now is an interesting time to write about all of this: not from the perspective of a smug succeeder, but from that of the struggling disciple, trying to turn things around again.
I am starting to get back on top of my tasks and lists again. I know how it feels to be overwhelmed, to have a brain buzzing with alerts and anxieties; and I know how it feels, however briefly, to be in control.
So - here’s to engineering more efficiently, fluently and… more cannily
On Staying Engineer
originally posted on one of my several now defunct blogs, called On Engineering, on the 12th February 2013
Blogging about considering new jobs (and doing something about it) seems like a risky idea. Posts are by their nature open to the world, so conceivably my boss could read this.
(Well, it’s inconceivable, really, but let’s go with it for now)
What will he think?
In my case, there’s nothing that he can’t have been inferred from previous discussions, so there’s nothing that could surprise my boss unduly were he to read this. For you, dear reader, there are hopefully some worthwhile thoughts in here - so read on, whilst I write on.
It’s safe to say that I had a frustrating time at work in 2012, mostly for non-engineering reasons (resources, too many inputs and outputs, etc). I decided that a change of scenery would be a good way of clearing the decks and starting afresh, so I applied for a couple of new jobs.
A seemingly attractive way of making the switch to a new company or even to a new industry was, I thought, to glide along the plane of least resistance, taking a training- and background-agnostic route. In my thinking, this route would take me towards Project Management.
It’s not perhaps strictly true to say background-agnostic. Project Managers are often handed the role from within another, and that’s what happened to me at various stages in my career - so I can show a Project Management history: nominally, I am in any case a project manager right now. It forms part of my job title (the other words being “Development Engineer and-”). Whilst I officially combine the roles I also tend to fulfil both roles simultaneously (Project Manager, manage thyself!), which has added to the frustrations I have felt of late.
We were also given project management training a while back. It was in itself quite inspirational and I came top of the class in the tests at the end of it. So, in essence, Project Management is something I can do, more or less without really thinking about it - in fact, what else do I do other than manage projects? Every single task I have, be it “engineering” or “not”, is part of a project, big or small. I do have to force myself to do things like pick up the phone (I’m much more of an emailer or short messenger than a caller), but overall I can work with others and others seem to be able to accept working with (sometimes for) me.
I got invited to some interviews.
Both were within the automotive sector, so I wasn’t going to be changing industry, but I would be changing technologies - glass and engine products were the general themes.
And therein lay the rub with me wanting to switch via the PM route: I thought the technologies would be cool, not the job. You see, what happened in both interviews was something like this:
Interviewer, after some preamble: “Imagine the scenario that a task within one of your projects is delayed. What do you do?”
Me (brain whirring, thinking…): Um, what can I say to this that could possibly be interesting? I’d have to talk to the guy whose task it is, see if I can chivvy him up a bit. Talk to his manager, talk to the customer, see if we can delay - oh, this is all so dull!
Me (aloud): Well, we could, umm, talk to the person responsible for the task (etc)
Me (body language): help! I’m floundering here and both I and my interviewer have lost interest in what I’m saying. He’s staring out of the window, I’m staring at him for some kind of positive reaction…
And so on. Yet within the same interview I had to field some engineering-type questions:
Interviewer: What do you think could be the potential technical difficulties involved in developing this kind of product?
Me (internally): Yes! Easy score here
Me (aloud): Well, there’s the material selection, the coatings, how to apply them within undoubtedly very tight tolerances, how to withstand heat without distortion that would…
Me (body language): Hands waving, leaning forward, engaging the interviewer - more, please!
In the end, I have to realise that I am by nature an engineer, with everything that that entails: all the coolest development work, all the dullest admin stuff and everything in between. Anything else (commercial, purchasing, quality) would mean going against my own grain.
The only question remaining, then, is: can I become an engineering manager? From the aspect of organisation and team working, data access and transfer, deciding on what’s right for the product and for the company - yes. From the aspect of dealing with stroppy employees, an ever-increasing email and travel load, and becoming ever more involved in company politics (whichever company that may be) - who knows. But that discovery is for another day.
Have you transitioned away from pure engineering? Have you made the step up to management - either successfully or stressfully? Let us know in your comments!
Shanghai and indirectly back again...
I’m writing this on the plane from Shanghai to Bangkok (fortunately for you, I'm editing it several days later from home). It’s going to be a long post, as it's been a long several days: now, tapping this into my work laptop whilst sat in seat 8D in this Airbus A330, I’m as exhausted as I can remember being in a long time. I’m forcing myself to think and to write so that I can stay awake until we land in Bangkok: I arrive there at around 9 pm local time, which is something like 2 pm home time. I want to make the transition back to European time as quickly as possible, so I’ll wait until the homeward flight from Bangkok to Frankfurt, departing around two hours after I land, before I finally allow myself to sleep.![]() |
| Nearly home |
![]() |
| The view from my hotel room |
![]() |
| Cucumber juice! |
![]() |
| The dumpling-makers |
All good fun (and I have locked away the video evidence of that…) and all very late and all very exhausting. Perfect preparation, in other words, for being checked out and picked up at 7am to travel to a meeting with Shanghai Volkswagen.Socks: an addendum
I wrote in my post concerning socks the other day that I didn’t like my Sealskinz waterproof socks one little bit.
Today, when I ended up taking my daughter and her friend sledding this afternoon, having thought and written about those Sealskinz recently, I thought I might try them out again. Lo and behold - they were fine.
The secret this time was to wear a pair of summer ankle socks underneath; quite why I didn’t come up with that idea before I don’t know, but it helped no end to ’normalise’ the Sealskinz to something akin to socks.
And the sledding was great fun, of course!
(I also notice that the Sealskinz sock range has been refined somewhat since I bought mine all those years ago... worth another shot?)
The subtle tyrrany of the sock logo
Mine, as you might now expect, have been bothering me lately - but in a way that only socks can.
It's not that they are uncomfortable; far from it. From experiences both good and bad throughout my sock-buying life I know what I want and have settled on one main source: whenever I'm back in the UK, I stock up on socks from Next. I know that they fit, they're decent quality and - well, they just work.
So, what does a sock have to do to work? Well, first and foremost, a sock can't work unless it's one of a pair. Certainly, odd socks can be and often are worn, but that function if they are both of the same make and if the wearer is either oblivious to the fact or is being aggressively contrarian. A business sock and single cotton, knee-length Bavarian Lederhosen sock would be so wrong that the combination wouldn't make it out of the bedroom door, or the wearer is an artist. But one brown sock and one black sock? It happens. If one of a pair has a hole in it, that pair becomes separated into two individual socks - the pair is dissipated and both will be thrown away sooner rather than later. I've tried darned socks, and they're awful, the new threading putting a strange pressure on the pampered, sensitive balls of my feet: fortunately I'm not poor enough that putting up with them is a necessity.
I've tried cheaper socks that felt like cotton shopping bags - something designed for carrying potatoes rather covering feet. I also own an expensive pair of Sealskinz waterproof foot coverings (I daren't bless them with the honourable title of sock) which are so uncomfortable, they feel like a Lenten penance rather than a sporting luxury. Wet feet are more comfortable than that. They seemed a good internet purchase at the time. And most "technical" fabrics simply don't belong on feet. Some may make the promise of "wicking" sweat and all of that - but there's nothing better than cotton for me. So the precise form of a sock, the material selection and the quality of the stitching are all key.
And socks have to look good.
What is a good-looking sock? Fortunately, there is no single answer to that question. Some people can get away with massively contrasting socks, like a combination I recall seeing at the Paris Motor Show in September: blue socks against pink trousers - I think it worked brilliantly, though it's not even remotely my style. Others go for the traditional Burlington diamonds, but I find that too fussy.
No, for me it's about a single, muted colour that can theoretically work with any combination of clothes I might happen to have thrown on in the morning. The problem with socks as part of the early morning on-throwing is that, as I mentioned, for them to function properly there have to be two of them.
For the vast majority of socks that I have owned, this has not been a problem. Socks are normally symmetrical, so on they go without any further mental effort on my part. But now more often than not, socks have logos on them and that, finally, is what has been bothering me.
The problem with these logos is that I know that they they are there to be displayed - either as a vaguely personal statement of sartorial individuality or of sartorial belonging to a particular tribe; in either case, they are, as any logo is, also a form of advertising.
So, logos are there to be displayed and to be seen, meaning they should be worn on the outside of the ankle where, when you're sat with one leg crossed over the other and the trousers have rucked up to the top of the sock, others can glance at said logo and appreciate it for whatever symbol that is.
The thing about these logos is, though, that they are nearly always sewn on one side of the sock only. And, appreciating the necessity of displaying the logo, one sock always has to go on one dedicated foot, every time.
Everybody applies the pressures of footfall to particular areas on the foot, in their own way, but usually it starts with the balls of the feet. With the socks now dedicated to one foot each, it means that these socks are no longer being eroded on the "inside" or the "outside" of the sole at random times, like flipping a coin - no, they are being pressed and rubbed and squashed at the same point each and every time, meaning that one of these socks is going to wear out more quickly.
I have no idea if the rate of erosion to a hole is significantly greater with a foot-dedicated sock than for randomly applied socks, but the theory holds, and that's been bugging me of late.
Am I man enough, then, to throw the shackles of logo duress? Or shall I go meekly back to buy the next pair of replacements, and the ones after that? You know, I think I will - it's a small price to pay for the comfort of conformity...
Hit or miss: fun on the mountain bike
Mountain biking (an all to rare occurrence for me these days) is not a purely physical exercise; the brain is given a real workout, too. I’ll concede straight away that it’s by no means an intellectual exercise - I’m not necessarily thinking of anything at all (also a rare occurrence, one to be encouraged). But sometimes I become aware of the sheer mass of calculations that the brain is performing whilst I’m on the bike. It’s thinking almost as hard as the legs are pumping.
Of the many types of calculations buzzing around in my head, the most satisfying for me is the “hit or miss” question. I’m pedalling along a trail, at best upwards, and there’s a rock in the way. Now, I can miss the rock with my wheels simply by steering away from it. But if things are tight and there isn’t much room for manoeuvre, I start wondering if I’m going to bottom out with my pedals - which is usually a worse situation than hitting a rock with the wheel.
![]() |
| Is that pedal going to hit that rock (and who's going to come of worse?) |
Pedals don't have big fat tyres or squishy suspension. What they feel, you feel.
With the pedals entering a zone of uncertainty, the brain embarks upon a series of vector-style calculations, that goes something like this:
- my current gearing (including wheel size) is such that
- if I keep pedalling at the same rate
- from this current rotational position
- and with my pedals at this height from the ground, I will
- miss / just miss / hit that rock
If I am going to grind the pedal on that rock, with all the ensuing discomforts, I can take action with a few more calculations:
- at this vertical incline I have sufficient momentum to be able to stop pedalling briefly without completely losing forward motion
- I can change gear to change the rate of rotation of the pedal in question
- I can incline the bike to one side, raising the pedal height
- I can attempt to raise the height of the whole bike (by trying something silly like a bunny-hop)
- I will need to ride over the rock (thereby starting a new set of calculations)
But by far the most satisfying result of all of this is the near miss. It's a confirmation that everything the brain worked out was correct, and that gives it an immense sense of pride - whatever that means in brain-speak (hormones, of course).
So, whenever you're next out on your bike, even if you're out and about in town rather than downhilling, just be aware of and amazed at all the things you don't hit.
Variations on the theme of Rock-a-bye baby
One of the lullabies that I sing to our daughters has, by necessity, developed over the years. When our eldest was old enough to express her thoughts and consternations, it became clear how the original lyrics of Rock-a-bye baby (originally not intended to be a lullaby, I believe) were deeply worrying to her:
Rock-a-bye baby, on the tree-top
When the wind blows, the cradle will rock
And when the bough breaks, the cradle will fall
And down will come baby, cradle and all
It sounded very much like at least a big “Ouch” for the baby, and L was uncomfortable with that. Now, I know that there will always be howls of protest at how traditional childrens’ songs are being softened, made more “correct” and in a way neutered - but English childrens’ songs in particular are a strangely brutal bunch with lots of head choppings and smashings to pieces and I’m not totally at ease with that. So, over the years, our version of Rock-a-bye baby changed and gained a few verses as I sang, waiting and hoping for the child finally to go to sleep. There are often more ad-libbed verses, often to do with the day’s events, but these are the current standards:
Rock-a-bye baby, on the tree-top
When the wind blows, the cradle will rock
And when the bough breaks, the cradle will fall
Down into the arms of Daddy so tall
Rock-a-bye baby in- the car,
Wheels going round and round so far
And when the car stops and we take out the key,
We’ll all be back home in time for our tea
Rock-a-bye baby on- a bike
Pedalling so fast to places we like
To the butchers and the bakers, to get our croissants
Then off to the Hostig* to play and sing songs
Rock-a-bye baby on- a boat
We like our toast and Marmite afloat
But when we find out we’ve less tea than we thought,
We turn the boat round and head back to port
True, there’s a certain fixation with cups of tea: but what else sums up the goodness of sitting together and having a chat about nothing in particular?
*Hostig is a local playground.









