Let’s do the math.
If you give a speech to 200 people for 30 minutes you are consuming 100 hours of human life.
Giving an hour-long talk to a thousand people? That’s six weeks of human life devoted to your talk.
*gulp*!
Let’s assume 6 weeks of human life is at stake. It is not a loan and you cannot give it back. One hour after you finish speaking, you’ve used up 6 weeks of human life.
If you’re bad enough for long enough you kill a whole person.
Mathematically, if 1000 people witness your speech and 0 of them change any aspect of their life then you should not have given the talk. You used up 6 weeks of human life and achieved nothing.
Let’s all pledge together:
- I am valuable
- I will continue to share my ideas and my work in public
- I will continue to improve the craft of sharing publicly (for example, speech craft and blogging)
- I will respect the time of other people as a gift
- I will change lives
This pledge needs a name; anyone?
You are an incredible individual. You have done things, seen things, diagnosed things, solved things that no one else has done. No one else has the accumulated knowledge and reasoning that you have. You were the one who conclusively deduced that all solutions to World Peace involved chocolate biscuits.
You are also unique in your methods of communication. You have different stories, different mental models, and different approaches to communication. You do that thing with your voice and your posture. As a child you were beaten up for being different. As an adult it makes you extremely valuable.
There are human beings who need to have their lives changed by you. Your value is when other people behave differently because of you.
What to do next?
There is no check box, pass or fail, “crossing the finish line” in public speaking. I’d rather watch you play Guitar Hero. Aim higher. Take responsibility for your communication. Look at the human beings in front of you and rock their world.
How?
Like the craft of software development, there is the craft of communication.
Practise the craft of communication. Limit the minutes/hours/days/weeks that you use of other people’s lives. Write your speeches and then practise them to increasingly larger audiences.
“I’m not very good at speeches”
Write small speeches for small audiences. As you improve, increase the size of the audience. If it’s necessary to achieve your goal, increase the duration of your talk. Though how often can you communicate 80% of your message in just 5 to 15 minutes?
If you are given 45 minutes at a conference to speak, you are permitted by me to speak for 15 minutes only. If you know you only have 15 minutes, perhaps invite one or two other people to share during the remaining time. Or give back the remaining time to the audience. Ask them to use it to think about or explore the idea you’ve shared with them.
“Where can I find small audiences?” If you’re practising a large audience speech, then pull a handful of people into a room and they can alpha test your talk. As a small group they’ll probably do something annoying like give feedback. You’re probably self-conscious enough that your brain is full of negative self-feedback, so you may or may not want their feedback. But let them give it to you. “Thanks, that’s a good idea” is the reward you give them back.
Next, find another small audience. The jokes won’t be as funny in small audiences. Large audiences laugh louder and stronger. Do the talk again.
Follow up with the first group – did they do anything different in their lives after your talk? Did they talk about your ideas or thoughts during the week? If your speech is good then some small nugget will carry with them, regardless that they are a friend/peer/family member.
Don’t worry too much if you don’t rock their world: friends and peers tend to not learn as much from you. “You can’t be a guru in your home town.” That’s not the job of a friend. Friends are there to laugh at you and put you in embarrassing situations for their own amusement. Nonetheless, it’s interesting to see if your small friendly audiences thought about your talk in the days afterwards.
Even in a small room with friends, unload on them with energy and passion. Practise your communication as much as you practise your content.
“Where can I learn speech craft?”
Toastmasters.
You learnt to drive with your parents and a driving instructor. You learnt software development by writing small demo apps and pair programming. And yet some people have the audacity to stand on stage in front of 100s of people and be terrible. Those people are not you. You will not suck. You are going to learn the craft of speaking because you want to use people’s time well and you want to change their life.
Toastmasters is a club format. There is no “school” concept. Rather a group of 20 people meet twice a month and each time they all suck less. They stop stuttering. They tell interesting stories. Everyone learns something fascinating from other members who have different backgrounds and professions.
The practise format is interesting and successful. You give three types of speeches: 5-7 minute prepared talks, 1-3 minute impromptu talks, and 2-3 minute improptu evaluation talks about the previous speakers. That’s right, you get immediate evaluation from another club member!
Every club is different so visit a few of them to find a club that you like. Some a filled with old farts who value meeting protocol over having a good time. Some clubs like doing competitions. Some clubs meet weekly. Some clubs meet for breakfast or lunch or in the evening.
It’s relatively cheap.
You will learn the craft of speaking and leadership. And conversely, though not explicitly promised in any Toastmasters literature, you’ll stop killing people.
Is it really that important?
Personally, I think its a bit unfair of a presenter to be bad in front of a large audience for a long duration and say “I’m sorry if I was bad. I’m trying to get better.”
But! It is far far worse is the competent presenter who does no preparation, does a terrible job, and merely hopes it goes better next time. There are human lives at stake. One of them might be mine.
As a public speaker you have a gift – human lives. You have their time and their open minds. Aim high. Change lives. You are special. I hope to experience you speaking awesomely at a conference near me soon!
Thanks
Thanks to Zach Holman for our chat on the plane back from Ruby MidWest and for proof reading and fixing the post. He is a great speaker and will definitely convince you of whatever snake oil he’s selling
Ever see example shell commands like this and wish you could paste them in?
Fear no more. A pastie is at hand.
Here’s how to install it:
In your `.bash_profile` add the following:
Thanks
@dwaite and others for `$@` instead of `$0 $1 …`.
I’m interested to trial RedCar in my life, instead of TextMate. So I need RedCar
to appear on my screen whenever I think “give me an editor”.
I’ve had m bound to TextMate for years. I also have it set to my $EDITOR variable, so it is launched by git commands, etc.
To change the default to RedCar, and to allow me to toggle between RedCar and TextMate, AND to allow me to use Edge RedCar (from source instead from a RubyGem).
This file comes from my editor.sh file which is loaded into all shell terminals.
I can change to TextMate with:
use_textmate
Back to RedCar (via gem) or RedCar (from source):
use_redcar_gem
use_redcar_dev
It irked me a little that I could develop on one stack (OS X, Rubinius, Sqlite3), run continuous integration (CI) on another stack (Ubuntu, Ruby 1.8.7, Postgresql), and deploy into another stack (Gentoo, Ruby 1.9.2, MySQL). I think what irks and worries me is that there are three sets of differences to be aware of. A bug in production? Was it a missing test scenario or one of the many differences between production and CI environments?
So I think I have two solutions.
First, use a VM that matches the production environment. Each different production environment would mean another VM. If you are managing your own production environment, then all you need is the tools (described in this article) to recreate your production environment in a VM.
Second, use a clone of your production environment. That is, if you deploy to Engine Yard AppCloud then run CI in Engine Yard AppCloud; if you deploy to a single Ubuntu instance on Slicehost, the have another matching Ubuntu instance on Slicehost.
I’ll write about the first solution – using VMs – here, and I’ll write on the Engine Yard Blog about the solution for Engine Yard AppCloud customers. For AppCloud users life will be even easier because there are zero setup steps to ensure you have consistent environments. It’s been one of my favorite projects in the two months since I arrived at Engine Yard.
I’ll also introduce a CLI for talking to Hudson – one that assumes you are working on Ruby/Rails projects – and makes it really easy to get up and running with a server, your Rails/Ruby projects, and any VMs you need (optional for Hudson, but they are the point of my line of thinking).
And I’ll introduce Vagrant, a CLI for creating/managing/destroying VMs.
Oh, and I’ll introduce Hudson CI.
Ok, let’s fix all our CI problems in one go…
Hudson CI
I needed a CI tool to allow tests to run inside VMs or on remote servers/VMs. Back in May I found and fell in love with Hudson CI. Fortunately it had support for “slaves”, and a way for CI jobs (your applications or rubygems) to select which slaves can be used. Hudson is also great because it is easy to try out (one click to install and launch), easy to configure, and has 350+ plugins.
What is Hudson?
CLI for Hudson
Charles Lowell’s hudson.rb project is a CLI for launching Hudson (it’s bundled inside the gem), and a set of CLI tasks to add/remove projects (jobs), add slaves, trigger builds and more.
gem install hudson
You can launch Hudson via:
hudson server # Default: --port 3001
open http://localhost:3001
It currently assumes you are working on Ruby projects, using bundler, and attempts to create a useful set of default steps for your CI jobs.
cd /some/rails3/app
hudson create . --host localhost --port 3001 --template rails3
Hudson CI will automatically start running steps to install your application’s gems, database, and run your tests. When it does it on your local machine it’s not that impressive. When it happens on a fresh VM or slave node and you didn’t have to do anything to set it up, it’s awesome.
V is for Vagrant, VirtualBox and all things VM
If you can script it, then you can automate it. Fortunately, as a virtual machine VirtualBox is both scriptable and FREE! Secondly, if you have a VM, you’ll need to script its setup/provisioning; so fortunately there exists chef and puppet, amongst others.
Thirdly, if you are really really really lazy, like me, you will want Vagrant. Created by Mitchell Hashimoto and John Bender, Vagrant is a tool for building and distributing virtualized development environments. Everyone in your team have their own OS/configuration? Got Windows users on your team? Use Vagrant.
Once you have VirtualBox installed, getting any of your projects live within a VM is trival:
gem install vagrant
vagrant box add base http://files.vagrantup.com/lucid32.box
vagrant init
vagrant up
vagrant ssh
$ cd /vagrant/
$ ls -al
You will now see the contents of your project folder, but from within the VM instance! They are linked – a change to either is automatically reflected inside and outside of the VM.
In this example, the Guest OS being downloaded and installed into VirtualBox (note: without any GUI) is Ubuntu Lucid, but you could use any VirtualBox packaged unix system.
For wonderful guided tour of Vagrant see the Getting Started video.
Vagrant – Getting Started from Mitchell Hashimoto on Vimeo.
Hudson CI + Vagrant = Perfect CI
Whether you choose to use VMs for a production-like development environment (a good idea for anyone, a wonderful idea for Windows developers who are very far removed from their production experience), it is a very good idea to have a CI environment as similar to your production environment as possible. Here, we want a VM instance with all the components/utilities/rubies set up that you have in production.
I have created an example Rails application that is setup to use Vagrant for a CI slave VM.
See the README for complete instructions. See the Vagrantfile and the cookbooks folder for the configuration and provisioning recipes.
Once you have the VM instantiated, you add it to your Hudson CI master (either the localhost one above or your remotely hosted server) with the CLI:
hudson add_node localhost --name "VM" --label railsapp-vagrant ...
(See the example Rails application for the other flags I used to get this working). It is now available to all Hudson jobs; but has a label “railsapp-vagrant” to allow jobs (Hudson’s name for a project) to specify that slave node specifically.
To add the Rails application to Hudson CI, and force it to run the tests in this VM:
hudson create . --template rails3 --assigned-node railsapp-vagrant
If you visit the Hudson master (at http://localhost:3010 in the example) you will see the job automatically running (“building”) within your VM. It will use bundler to install the gems, and run all the tests.
That’s it?
I know, CI is historically a pain in the arse. When CruiseControl was the only CI kid-on-the-block, it was standard for people to respond “4 days” to the question “How long does it take to get set up?”
It can now be really easy.
More importantly than being easy, you are running an application’s tests within an isolated VM that you can design to match your production environment.
I think there can be a good future for CI and Rails applications. Thoughts on this solution?
Thanks
Some of the technology in this article is old, other bits are very new, but for all of it I thank all the creators and contributors. Hudson CI was created by Kohsuke Kawaguchi during his days at Sun. He is now offering Hudson support services via his company InfraDNA.
The Hudson.rb project was created by Charles Lowell to bundle the Hudson CI and some common useful plugins for Ruby/Rails projects. He came all the way to Gothenburg, Sweden for NordicRuby conference (great conference by the way!) I fell in love with Hudson and started helping Charles on Hudson.rb.
Thanks also to both Kohsuke and Charles for starting work on a JRuby plugin for Hudson CI, and writing up a progress report.
Thanks to everyone who agrees that Hudson CI is awesome.
Thanks to Mitchell Hashimoto and John Bender for creating Vagrant. It is an incredible tool for developing within a VM (on OS X or Windows).
Finally, thanks to Bo Jeanes who helped on the Engine Yard AppCloud version of this project. Coming soon!
RubyConf & RubyBayou
If you’re in New Orleans this week for RubyConf, I’ll be at the local Ruby group RubyBayou talking about Hudson CI, Vagrant, and AppCloud on Thursday night. There’s a happy hour from 5pm till the 7pm start.
Location: LaunchPad NOLA, 643 Magazine St, New Orleans, LA 70130
Come and let me convince you about the wonders of Hudson CI and having a CI test environment that matches your production env. You know you want to be convinced. It’s good for you, like fruit.
Don’t forget Chuck Norris
Always remember to install the Chuck Norris plugin for Hudson, and enable it for each job. Don’t forget Chuck Norris.
Have you ever looked at your biological watch and thought, “it looks like it’s time to change the world?”
My biological time piece has a full set of inscriptions: go to university, chase girls, get a post-graduate qualification, catch a girl, get a professional job, marry the girl, change into contracting, change into consulting (and ponder what the difference is), work overseas (and marvel at the differences), make a baby, change into training, move back to Australia, buy a home, start a consultancy (Mocra), make another baby, grow the consultancy, and …
Really, I’m not sure what comes next in the script of normal life. Retire in 30 years? Create more little open source projects? Just keep growing the consultancy? Until what?
A few weeks ago, John Dillon, the CEO of Engine Yard, drew some pictures on a whiteboard for me and asked, “Do you want to help change the world?” Sure, a classic Steve Jobs one-liner from the history books of Apple. I said, “Yes”.
On the 1st of September I will start work at 500 3rd Street, San Francisco as Engine Yard
’s VP, Technology. Job description: help web application developers win.
The daily commute
Google Maps suggests my daily commute to work will be 22,300km. Some of that will be heavy morning traffic, so at say 30km/hr, that is almost 750 hours. Each way.
So instead, my family will pack its bags and move overseas again. Though for the first time, we’re coming to America!
How to move your family to America
It hasn’t been all smooth sailing on the home front since I broached the idea with my wife. Personally, have you ever turned to your wife and said, “Honey, I think we are going to move to America!”
Try it at home for a laugh. Perhaps your wife will say something witty or clever like mine. Something like, “No.”
“No, baby, really. I have something important to do for a few years. It’s in America. San Francisco. Apparently it’s lovely!”
“Is the weather nice?” she might ask looking for any reason to want to leave beautiful, sunny Brisbane.
“No. I think it’s kind of cold there. And foggy. There was even a taxi with ‘Fog City Taxi’ on its side. But there are wonderful schools and the people are fabulous and are from all over the world!”
“So our young kids won’t get an American accent?” she might ask pleadingly.
“Well, they won’t get all of the accents, no.”
“…”
“I love you!”
And so eventually your wife will say yes.
How do we get to win as web developers?
Choose to use Rails. Improve Rails. Improve the ecosystem above/below/around Rails. Improve our daily lives. Expand the sweet spot of Rails to solve problems.
In the future, can we look back at the work we did, the fun we had, the problems we solved, the time we spent working, and feel that it was worth the effort? Will we remember when we first discovered Ruby and Rails and remember the joy?
This is a world-changing set of issues to care about. I’ve always cared about them before now, but never had resources or reach to work on them beyond my own little projects or cunningly worded, suggestive emails/tweets/chat with other open source developers.
Though from now onwards I will get to work with one of the greatest concentrations of Rails talent and one of the largest open source programs in the our community. I’m more than just a little bit excited. Imagine working with full-time contributors to Rails, JRuby and Rubinius as well as the dozens of developers, devops and more.
As Engine Yard continues to grow and win then its capacity to fund and resource more contributions will grow. And then we all win faster.
Can you imagine what else should be funded, promoted or prioritised? I have a dozen solid ideas but I would love suggestions.
Mocra
I will miss my guys at Mocra, a wonderful Rails consultancy with clients around the world whilst based out of Brisbane, Australia. I founded and ran Mocra for the last two wonderful years. It will be slightly annoying – I won’t get to take any credit for all the success the Mocra team will have in the years to come.
Definitely, if you need an awesome Rails team for your project, contact Mocra. If you need a personal introduction, let me know. I know some people there.
San Francisco
I am very excited to move to SF and to hang out on a regular basis all the people I have only been able to see at conferences.
I’d also love suggestions of where a family of four (including a 4yo and 2yo; oh, plus another one due in February) could live. I’ve briefly seen parts of SF and many of the surrounding towns in the bay area. Thanks to Randall, Tammer and Marcy for their turns as tour guides during my visit a few weeks ago.