It was so tough, that I didn’t write any resolutions or plans, because I couldn’t divert any outward energy to them, and didn’t feel I was able to write candidly without self-censoring. So I wrote no plans.
This year I’m going to try to be more transparent – my current aims for this year are something like:
Find someone who’ll love and support me, and let me love and support them.
So we can explore our journeys together.
Ingest as much information and knowledge about relationships in whatever forms I can: books, talks, audiobooks etc.
So I understand more, and at least know where to look if I need to quickly develop skills I don’t have, which help me be a better partner.
Improve and polish the van to make it more desirable to live in
So that it’s more polished, more comfortable and could grace the pages of insufferable lifestyle magazines.
Get fitter by doing more hiking & climbing
So I feel physically & technically fit enough to consider more outdoor challenges.
Travel, explore and see the country (and others).
To see the world from different perspectives
So I can play around with building ideas that might make other people happy
Figure everything else out.
So there are answers to the unanswered questions in my life.
This is a snapshot (accurate only on the day it was posted) of constantly evolving plans. If I decide that one of those isn’t so important, it may be removed, changed etc – and that’s ok.
So here’s one last thought, if you’re able to help me take any small footsteps towards getting closer to any of those goals: recommending, suggesting, encouraging, supporting etc. then you’ll be helping me with exactly what I want to be – and I’ll be incredibly grateful.
If that’s anything I can do to support you then I’d love to know, to see what I can do – I appreciate you taking the time to read this.
My thought is whether artificially helping people associate letters with colours, can increase the speed of reading, specifically, in ‘specially prepared’ texts read from a computer screen, but I’m also interested in whether it might persist away from there.
Most people read by pattern matching the first two letters (ish) of a word – it’s how the neolism Typoglycemia works: for how you can largely understand:
“Amzanig huh? Yaeh and you awlyas thguoht slpeling was ipmorantt.”
Often though, we’re reading text on a computer, that the computer can help us with. That is to say, a webpage, an email, an ebook. Computer manufacturers spend a lot of time developing typefaces that are easy to read, and hard to confuse the letters of (Google even came up with an entire typeface for Android).
But it’s not always possible or desirable to read things in typefaces that are different from the original,
My theory is that the brain can probably increase its word-based pattern matching skills, by assigning each letter of the alphabet a shade of colour.
This might sound like the most ridiculous thing you’ve ever heard or seen, but if you consider that programmers used syntax highlighting to quickly derive extra meaning from great blocks of text – it seems more reasonable that there might be some way of using colours to improve up pattern matching when reading words.
So take a look at this prototype colourphabet I just threw together.
You’re not the only one thinking “this is much harder to read than ‘The quick brown fox jumps over the lazy dog'” and I don’t propose that I’ve solved this, or got anything more than the start of a stupid-sounding idea.
I wonder if it might better apply with different colour pallets, or perhaps colour pallets applied to different words in sentences – perhaps based on adjective/verb/etc… or something else?
How would you improve it? I’d love to hear your ideas!
We’re taught that annual salary/’the amount of wealth’ we have is something that matters, so if we’re going to devote our lives towards working towards something, it makes sense to think about it carefully.
If you say “Would you like to be richer?” to people, most people will easily answer “yes”.
Ask people – “How much money (in GBP) do you think is the ideal amount of wealthy?” – say by specifically how much, and it becomes an order of magnitude harder to answer.
Perhaps the most interesting thing about this question is not what is the ideal amount of money, but what you think is the ideal amount of money.
Recently there was an article that at first glance is designed to enrage you (“‘We earn £190k a year. Do we need to sell our flat to afford private school fees?'”) and maybe it does – and yet perhaps there’s a powerful lesson to be learnt: “no matter how much cash you have, you can still be really stressed”.
There’s another lesson there too: “and when you have more than everyone else, people are less sympathetic to your stress”.
And one of the many weird little problems you discover when you get rich is that a lot of the interesting people you’d like to work with are not rich. They need to work at something that pays the bills. Which means if you want to have them as colleagues, you have to work at something that pays the bills too, even though you don’t need to. I think this is what drives a lot of serial entrepreneurs, actually.
You think you can see the upsides, can you also see the downsides?
So it’s worth considering – the question: “How much money (in GBP) do you think is the ideal amount of wealthy?”.
I’ve thought about this question a great deal, and I still don’t know my answer.
Having spoken to people in less economically developed countries who earn an order of magnitude less than me, my sense is that it’s difficult for them to imagine life could be stressful when earning what I do – and when my salary is a 10x multiple of theirs – you can see how it could be tough.
Put in perspective, it seems like the easiest way for me to answer the question isn’t to answer it at all – and to wholly separate wealth from happiness. Whilst this can’t be easy to take to heart, I think this must the right way.
I guess you can link wealth with quality of life, but it seems unwise to link wealth with happiness directly.
For anyone else, it really comes down to the much harder question “What do you want from life?”. “What would you do or want *if* you had tons of cash? Once you know that, you’ll know find it easier to answer this question.
How would you answer it? What do your friends say?
I don’t write front end code. I wish I could, but my role is that well known sweet spot between systems administration, user research and sales, and so like everyone else – I was there to learn. Being able to understand, empathise and mentor customers and colleagues is a really useful skill and I strongly agreed with some of her points.
"We can mentor our colleagues, clients and team members to think in a more empathetic way"
Most of my front-end experience was gained 5-10 years ago, in xhtml 4.0 where you felt lucky if you avoided a frameset so I find HTML5 (and Web Components in particular) mindtwistingly futuristic – perhaps how the internet must feel to people who group in the era of letters and telephone operators.
In the most basic, layman’s terms (probably with inaccuracy and missed subtly), Web Components are a way to create snippets of html, and call them back later in a simpler form – perhaps slightly like creating a function in code. Say you want something to create a slider or something, but don’t want to copy all the setup code everytime you want to call it – so you can import the html library that defines it, and then simply reference it with a simple tag. It looks like this is the future.
Unfortunately, currently: Browser support = patchy.
Emma Jane Hogbin Westby’s git talk was interesting (here’s the slides and notes) – and fortunately a few days before, I’d also read this great article on git branching – so I was able to follow along and understand most of what was being said. because I don’t really touch code, and only touch git for hobby projects , I don’t have such a deep understanding of that part of software development. As a result of the talk and the article though, I now know a bit about where you might want to keep all the individual commits that make up a feature and where you might want to squash them into a single object.
Amy Philips’s talk about mobile testing gave me an incredible headsup about how little I know about testing. Basically, testing mobile software is super hard – because there are so many different platforms, software versions, levels of connectivity, accessibility settings that testing becomes super-hard! I now feel extra inspired to go listen to Gem Hill’s Let’s Talk About Tests Podcast and understand more about the subject.
Benjamin Hollway gave a talk about young people and technology – nothing out of the ordinary I thought – just another youngish developer talking about the issues of being young, and trying to get into the technology community. Then after the talk, it came to Q&A, and it was revealed that Benjamin was 17. I was floored. Of course, I should have spotted the clues, but to the organiser’s incredible credit, they hadn’t billed the talk as anything different, they hadn’t said the presenter was young. It was very well executed. The Q&A were lively, with some people clearly inspired to see 17yros doing impressive things, suggesting that perhaps agencies should be recruiting people pre-university. Other people were unconvinced, wondering if pre-university young-people would be able to concentrate through a 9-5 day. They were roundly put down when it was pointed out that most normal developers can’t concentrate through a 9-5 day, not to mention that school/college is basically a 9-5 commitment before that point!
I had a good time catching up with Katrina and talking to Nathan about design processes and how to build things, meeting Goose, working out scary tech halloween costumes with Chris, finally chatting to Nick in real life and Andy about marketing & deals.
As the first event in the upfrontconf/speaktheweb that I’ve attended, I really enjoyed it – the organisers – Simon, Rachel, Katie, Dan & Jack, deserve a high five for putting in all the effort to make such a great event happen. Thank you all!
A few months ago we built a jobboard — pieline.net. It was mostly a programming challenge — we wanted to learn more about databases and Node.js, and we thought that this would be useful and straightforward.
There used to be the Geekup Jobboard, run by Andrew Disley, free and for everyone (except recruiters). It was split up by functional areas — business, design, development and others. A few years ago, Andrew focused his efforts on a better solution — NeedHQ and the site received no new jobs.
Tim had talked to an Agency owner who was sad that the site had gone and we also knew new developers who weren’t aware of the volume of jobs available, because they didn’t know the names of all the different companies to look at their websites. Other jobboards didn’t have jobs outside of London, didn’t have a clear UX, or were full of recruiter jobs which obscure the name of the comapny you’d be working for.
The idea was to create a simple job board — listing one job from every tech company around Manchester for 30 days. Ideally, people would submit their jobs to us. In practice for the time we ran the site, we manually added ~200 jobs by hand, and never had one submission.
Learnings about companies
Companies are hiring all the time. Even the small ones. Everybody would like another developer or two.
Most companies suck at designing their websites with recruitment in mind. At least half of the sites we visited buried their recruitment page — we often found ourselves trawling sitemaps for a link. Given how competitive it is to recruit developers, we thought that every company would list the main technologies a developer would be using in the job, but all too often we found that ‘Front End developer’ really meant ‘PHP developer’, or there were just no useful details at all. When we looked over recruitment pages, we were struck by a unifying theme — they put no effort in. We rarely had enough information to say whether we could do a job, let alone if we wanted to choose one over the 200 other jobs in Manchester.
When we talked to employers, whilst they were interested in receiving better people, they were totally uninterested in yet-another-jobboard — especially without any candidates already coming in. There are many job boards, and it seemed like putting the jobspec together at all was a labour. They were understandably deeply suspicious of anything that resembled cold calling recruiters (even when we approached via email!).
A very small minority of companies listed clear breakdowns of the job and requirements, with renumeration, perks, and insight into company and engineering culture. We’d probably say AO.com has one of the best hiring pages of the companies we’ve reviewed. If your page is half as good as theirs, you’re above average.
Learnings about technical things
If you don’t know if you’re building the right thing, use duct tape, not superglue
We never had a staging site — we deployed straight from our git repo. This wasn’t ideal but did force us to test a lot, and fix it if we broke it. When we wanted to move fast and get it out the door — we got it out the door.
Learnings about UX
To figure out how it worked in the hands of users, we went to tech meetups, and asked people if they wanted to see this thing we’d been building, and when they said yes, we asked them to apply for a job on the mobile site. As we watched them use it on their phone, we saw them click on the wrong bits, expecting things to work differently, and instantly gathered feedback about which bits worked and which bits didn’t. Some more experienced developers (I’m thinking Bobby and Martin in particular) were kind enough to critique the UI for us as well, which helped us get some of the common-sense navigation in place. We were reading Lean UX at the time, which gave us some great approaches for iteratively improving the user experience.
Users said many things — often they asked for features we didn’t want to implement in an MVP like search. Almost everyone wanted a clear salary range and we just didn’t have the data.
One of the challenges was that people often didn’t know what jobs they wanted.
People who could be hired into junior or graduate jobs, didn’t know whether they had the qualifications, when all they really needed was enthusiasm, the ability to learn and not being unpleasant to work with.
For more senior people, it often wasn’t really clear what the most useful details were to put in front of them. “Can I actually do the job?” seems like an important question, but understanding what the company is like, why they might want to work there more than where they work now, is also important information, which we couldn’t figure out a way of displaying.
One idea we had was that most job adverts are sparse on details, and so it seemed like the ability to ask each company a question — in an anonymous, ebay-style public Question & Answer might be an appealing feature.
We still think it’s a good idea — imagine: You read the job advert, you’re happy with the salary, you know where they work, you have the skills, they seem nice enough — however, you have some questions…questions that might be awkward to bring up in an interview. Questions like “do people ever pull all-nighters to finish things for a deadline?” or “will I be able to leave early some days to pick up my kids from school?”. Ultimately, although we tried our upmost to seed the board with questions, and use this feature to add value — we weren’t able to get it moving. We think it’s a neat idea, and perhaps might work really well — unfortunately we didn’t hustle hard enough to see any traction.
We tried adding Optimizely A/B testing to gather data about incremental changes. We might have been better off testing more radical variations but we learnt that with the amount of traffic we had, we were never going to learn much fast with very subtle A/B testing. Ah well.
Learnings about Growth
We never had a growth strategy that was sustainable, real or existant. We tried some paid adverts to get traffic, but since we never received any revenue from the site, this was clearly unsustainable. The idea never had a ‘purple cow’ so there wasn’t much virality potential. The question feature is probably the closest we came to it.
We feel this is an area we would give more thought to next time. Really, we should have tested this part first.
One great outcome is that a several people found jobs because of pieline! This was without doubt the best part of the experience — we’ve heard from a couple of people who found companies on pieline, applied for the jobs listed and got them, which is very satisfying. One of them became a good friend, and we got to hear all her stories of starting her first development job. It was also a great side project for Clara to show off to employers as she was looking for her first coding job at the time.
We learnt a lot from the project — about technical things, about product, about UX. I think the main thing we learned, was that a job board isn’t the best way to solve this problem. We’re not sure what the best solution is, though better company careers pages are clearly somewhere to start.
The site is mostly now offline, though it survives on archive.org, Github and trello. As for us? We’re better prepared for our next adventure.
Pieline was made in the People’s Republic of South Yorkshire with love by @czmj2 & @tdobson.
We’ve just come away from the AutoTrader “Science Fair” and we’re full of thoughts, ideas and reflections and wanted to get them down somewhere.
We heard about the event at Barcamp Manchester last weekend, and decided to go along to get a better understanding of how AutoTrader works. I know AutoTrader as a customer – we bought the van off it – so it was interesting to understand how things work behind the scenes.
An open evening! Whoever thought of this mag-fucking-nificient idea should be knighted. What a great way to help people find out more about you in a low pressure, chilled way (with free drinks!).
It reminded us of school open evenings (in a good way) – lots of people, hands-on-activities and posters. It felt a bit cramped in places – there were some areas where we thought pushing the desks against the walls might have been a better use of space.
Clara is a developer, so whilst I would have found it fascinating to talk to their editorial team and learn more about their inbound marketing efforts, talking about technology is common ground to us both. So as we only had 45 minutes to spare, we decided to immerse ourselves in their ‘technical’ room.
AutoTrader organises its teams in ‘Squads’ – autonomous, cross functional product teams who take complete responsibility for an area of their business, which meant that when we asked one of their devops people who would be the best person to talk to about Front End, there wasn’t a clear functional stand. Each AutoTrader squad has design, product, marketing, development all together – creating user stories, picking them off one by one, and working through them. One of the things we found surprising about all this was that they don’t tend to have a purely front end function in their squads – it tends to be something that their Java developers have or develop on the job.
We had a great chat with Jan and Gareth in the Dealer Portal Squad, who were super helpful in filling us in on how the system works, and how their system’s AngularJS app works (with Flux, doing some cool sounding event based things!). We found it interesting how none of the squads we spoke to really seemed able to talk about how they handle their CSS – even “Do you use a CSS pre-processor?”. It’d be really interesting to understand more about Autotrader’s approach to the front end – especially since they seem to work in a cross functional way.
One of the recruitment tools we admire the most is twovideos that Spotify’s engineering team put on YouTube. These two videos outline Spotify’s engineering approach, company structure, and explain how things get made and product gets shipped. All explained concisely & knowledgeably and beautifully illustrated. To an outsider, it’s dizzying to be introduced to AutoTrader’s two dozen or so squads on the floor of their office, without a clear understanding of how the company works, and how their development processes work within it. Before we saw the Spotify engineering videos, we didn’t have any feeling about Spotify’s tech team. Now we feel they have a great (yet modest) engineering culture that we’d try to be part of if the opportunity arose. Perhaps there’s something for AutoTrader to learn there.
To be honest, we’re inspired. Perhaps not to work at AutoTrader (sorry!), though we now know the company a lot better (yay!). We’re inspired to take this open evening approach and suggest it to the companies we work for, and the ones we know across Manchester. This seems like such a great way of getting people to understand what you do, that we wish they happened more frequently, in more companies.
For the past 8 months, I’ve been completely teetotal. I’ve not drunk any alcohol since before Christmas 2014.
I’ve come to realise that the answers to my life’s problems don’t lie at the bottom of a bottle, and sometimes I found I can’t be certain there isn’t an answer there, til the bottle is empty.
I respect those who wish to keep searching for themselves, and for me, it’s time to call of the search (of alcoholic bottles).
I don’t think I realised at the time, but subconsciously I started binge-drinking self-destructively – I think subconsciously wishing for something to have a dramatic effect on my life. I say subconsciously – it was concious in a sense, but I couldn’t identify it as a serious thing to avoid. It was sort of prefixed by “loooooool, at least something interesting will happen”.
I’m lucky that apart from a few sore heads, and missing some fun opportunities, the negative impact on my life has been minimal. But it could have been huge, and very painful. I’m glad to have removed myself from those situations.
I’ve never really liked drinking. Since I turned 18, I’ve always thought that the most enjoyable drinking I’ve ever done was age 17, and it’s never really got back to that point. I enjoy being aware of the situation I’m in, and I feel able to have fun, without being drunk. Not-drinking isn’t a super-new thing for me – at one point in the past 5 years, I remember going to a popular nightclub, completely sober. The soberness wasn’t a terrible part of the experience (getting lots of glass embedded in the bottom of my shoe… that wasn’t ideal!).
It’s been 8 months now, and I don’t regret it for one moment – I’m happier, more comfortable with myself and more relaxed. There are times when I like the idea of a drink – but I know I’m happier sober.
What do you drink?
Everything. That’s not alcoholic. It’s that simple.
Shouldn’t you just drink less?
I found it really difficult to know the difference between ‘fun’ and ‘too much’. Since the ‘fun’ wasn’t really linked to the alcohol, and more the circumstances, I feel it’s easier for me to abstain.
Isn’t going out less fun?
I find it more fun. We get to do things that are actually fun, rather than just drinking. I find things that are just focused on drinking less fun, and yet I enjoy hanging out with people who are fun to hang out with.
Don’t you miss a great beer?
Yes. My favourite non-alcoholic beers are Cobra and Erdinger. I would love to try more.
Becks Blue is an alright drink, but cannot be called a great beer.
Doesn’t this help with van driving quite a bit?
There are unexpected positive side effects. Never having to think about the drink-drive limit is one.
“Imagine that money wasn’t something you had to worry about – what would you do?”
Once you figure out the answer, you’re meant to head down the most efficient path there. Working ‘to get rich’ when you’re seeking to ‘have a happy family life’ may not be the most efficient route for you. It’s not a new concept, and worth reflecting on.
Today, I want to share with you how I’m answering that question.
The plan is to buy a van, convert it into a live-in stealth campervan, and live in it. By June ~30th 2015.
Current status: I have bought a Mercedes Sprinter 2008 long wheel base 311 CDI 2.1 with ~150,000 miles – should go to ~300,000. It’s in fairly good nick.
This is my first car, and first thing I’ve driven on my own, so driving around Manchester is fun at times.
Where will you park it?
On the street, in different places – wherever we want to be at that point in time.
There will be an onboard Thetford c200 cassette toilet with SOG (so we won’t have to use chemicals). We will be using grey water from the sink for flushing.
What will you do about showers?
Not having them onboard. Showers exist in modern office buildings, swimming baths, sports centres etc.
Who’s going to do the conversion?
Me (with help from my girlfriend Clara).
What van conversion skills do you have?
Ability to read instructions, a nice powerdrill, blind optimism. You only learn when you try.
Why not buy a readymade campervan?
Most campervans are built for weekend trips away to caravan sites – where you get an electric hookup, and are never designed for constant use.
Parking up in a city, we’d prefer to look “stealth” – just like one of the unmarked white vans you saw today – that you didn’t give a thought to.
We dislike the 80-90s retro interior design of the campervans we’ve seen. The white/grey plastic makes me want to vom.
When you build something yourself, you value it more highly, so we think building our home will make us better appreciate it for what it is.
Why not buy a house?
You can’t drive a house to another place.
Why not build a house?
You can’t drive a house to another place.
Why not live in a canal boat?
You’re limited to canals, and travelling at about 8mph. So spending a week in the Lake District is kind of hard work.
What will you be doing about washing clothes?
Somehow, laundrettes still exist. Also, lovely friend’s houses.
What will you do about an address?
My parents live relatively nearby. That’s a good place to direct snail-mail to.
How will you power your electrics?
Initially, from leisure batteries and a split charge relay from the alternator. I’d love to have solar panels for charging the batteries, and as soon as I have time/money/energy, they’re on the agenda for the roof.
Once I can afford a Tesla Powerwall, and it’s easily available in the UK, it’s of serious interest to me.
Will you be on your own? (How will you ever get a girlfriend?)
My girlfriend Clara has been helping me with the CAD plans and seems open to living there with me.
How does she feel about it?
“*shrug* – it sounds like an adventure. If it’s not a fun adventure I will move back to my place in Sheffield. I’m super happy for my lovely boyfriend to do what makes him happy.”
How much will this cost you?
Hopefully less than a house, and less than rent, and more flexibility. I bought the van for £5,500.
I took some inspiration from VanDogTraveller and my friend Dan Woods who lived in a van during his University years in Manchester. I also listened to (and sometimes ignored) suggestions from Matt Bibby, Dave Crossland and others. I’m really grateful for their inspiration and advice.
In the ’50s, when my mum was little, she and her family lived in a converted double decker bus.
In the past I had an idea to travel around the country, spending a month in different AirBnBs. When I had the van idea, it felt more efficient and became the plan.
Won’t you be very cold in the winter?
Hopefully not. It will be chilly, for sure, and we’ll have to look carefully at how things are going as the temperatures start dropping, but we’re fairly optimistic that we can make it work. Staying warm in bed should be fairly straightforward, and one of the nice things about a van is that it’s a much smaller space to heat than the average house. We’re going to insulate it well.
Won’t you be very hot in the summer?
This could be an issue. The van is white and we’re planning to insulate it fairly well. The UK is hardly Morocco though. We count our very hot summer days, when it reaches 20C+, on one hand. If the van is unbearably hot we will go and enjoy the sunshine outside!
Aren’t you just demonstrating how incredibly privileged you are?
Yep. I’m a white well-educated, cis male, from a well-off background, with a great job and supportive family, in a first world country, with a social welfare system and a nationalised health service. I have to acknowledge that in almost everything I do. I have a lot of people to be grateful for, and I must be mindful not to take anything for granted and to do what I can to help those who’ve been less fortunate in the privilege lottery.
Aren’t you worried about what people will think?
In short, “no”.
I gave this some thought, I was worried my friends might instantly unfriend me. I realised that my friends don’t judge people by their living arrangements, but by what they’re like as a human being. I plan on being the same person, and anyone who wishes to pigeon-hole because of my living arrangements probably doesn’t know me.
Is this forever? Will you never get a house?
I may get a house in future. Who knows? Let’s figure that out when the future arrives.
I wouldn’t do this.
That’s absolutely ok!
Since about 2008, I’ve noticed that the internet has helped me geographically distribute myself. I noticed I didn’t seem to get homesick because the things I cared most about tended to be accessible via the internet.
I’m 24. I can make mistakes. I should make mistakes. I should make mistakes NOW.(I don’t seek to make mistakes, just be aware that they provide the most powerful opportunities to learn from, and that it’s easier to make bold decisions when you support fewer people.)
If this turns out to be a terrible idea, the downside is not fatal. It allows for learning. In the context of my life, it’s a small bet.
I feel that most of my relationships with my friends and family are location agnostic. Sure, I need turn up at my friend’s party, just like I should be at a family wedding – but the rest of the time? I’m not convinced physical proximity is super important so long as you’re there at ‘the right’ moments.
Being in one fixed location is less relevant to day to day job than it ever was. Most of my work is conducted over email and phone calls, and last summer I spent three weeks, working remotely from Bulgaria – more recently, close online collaboration in a distributed team seems to be working well.
I don’t want to buy a house, until I know I want to live there for ~10+ years. I don’t know where I want to be living in ~10+ years time, so I don’t want to buy a house.
There are two unfulfilled ambitions I think I have: one is to travel more, the other is to build something big.
It must have been a year or so ago now, I was sponsoring and exhibiting at a conference. Also exhibiting were a company I’ll call FooCorp from an industry that I have a strong distaste for. As delegates piled in, FooCorp’s team fired up this well oiled process of handing paper to people walking in. As a one man band, I felt a bit outdone.
I’d used twitter ads at events before, and so quickly I fired up a campaign. Trying to be edgy, I said something along the lines of “if you don’t want to be leafletted, and have your email added to a database, come and find me for a chat”. I can’t remember the exact wording, and whilst I don’t think it went any stronger, I can’t find the original copy so I can’t be sure. I thought “heh, why bother leafletting when this is so much more efficient”.
One might think “I don’t care about any companies in this industry, so this is a good approach”. One might think “I have no relationship with these people, so it doesn’t matter”.
Those points may be true (though these days, I have doubts), but I hadn’t anticipated the thing that happened next.
The conference organiser came up to me and said “Tim, we need to speak”, to their absolute credit took me to a private area and lividly explained that I needed to:
immediately delete the tweets
apologise to the people in question.
A wise or experienced person might have anticipated that, whilst I didn’t have a relationship with the FooCorp people, actually, lots of people around me, whose mutual support I depended on, did have a relationship with the people, and would like to continue to have one after the event. They might want to continue to ask FooCorp people to sponsor events they run etc. I realised that I’d failed to consider this point of view at all. That was poorly thought through.
When someone explains reasonably to me that I’ve upset people, and can easily avoid this, I know that I should do as they say.
Apologising to people face-to-face is hard. Apologising to people, who support an industry you have a distaste for, is harder.
But what makes it even more heart wrenching is when you notice that at the end of the day, they’re real people, trying to do good things, to help their children and families have a better life, and that I’d needlessly upset them.
As it turned out, my heartfelt apology wasn’t enough to undo the impression I’d already given them and I’m pretty sure that any memories that remain of me are about “that awful man”.
Were one anticipating this situation beforehand, one might assume one would be comfortable with that if it happened. Instead, I feel sad that I had to learn this like this.
And I have learnt from this.
I could be chatting with someone whose sector I utterly, totally cannot endorse, and I aspire to treat them with respect and humility. I reserve the right to continue to dislike their sector, even them personally – but if I meet or interact with them, I’ll treat them with the same respect and humility I show to my friends.
So I guess if either of the two parties in the story are reading this – you know who you are:
Conference organiser: I’m sorry for putting you on the spot in front of your other sponsors and for behaving poorly. I massively appreciate your approach to resolving this. You had a multitude of options, and you took the most professional route, and allowed me to do what I could to right the situation. For that, I’m forever grateful.
To the people of the company I’ve called FooCorp: I know I ruined your mood for the day, and I’m really sorry I wrote those tweets. I wish I could have done things differently now, but what’s done is done, and a lesson has been learnt. I’m sorry that my learning that day was at your expense. As you can hear, it’s a lesson I vividly remember many months later, and I hope it’s one I never have to relearn. Thanks for talking to the conference organiser and allowing this to be resolved in the manner it was. I really appreciate your professionalism under the pressure I know and regret that I put you under.