Speaking at TEK·X
Thursday, January 7. 2010
I'm always pleased to be accepted as a speaker but I'm especially delighted to hear that I'm speaking at TEK·X in Chicago this May. They had a crazy number of submissions for the number of slots available, and I really wanted to go since I spoke there last year and enjoyed the event hugely! This year I'm giving the following sessions:
PHP Best Practices (tutorial) - This is a half-day tutorial with my good friend Matthew Weier O'Phinney covering all sorts of good stuff you can do when you develop PHP. Its a general session and the aim is that everyone in the room takes away something new from our tips and tricks (and stories of what *NOT* to do!)
SVN in a Distributed World I'm giving this talk for the first time, looking at how traditional source control (subversion) compares with the newer distributed version control solutions (git, bzr). There's been lots of buzz around git but in the PHP world we choose our tools on merit, not on cool factor, so this is a chance for me to share my experiences with both types of systems and talk a bit about which scenarios the various tools are a good fit for.
Open Source Your Career Another new talk! This one is about how much personal gain there is being an open source contributor. I've grown hugely, both personally and professionally, from my experience with user groups, events, and software in the open source space - so I'll be sharing some tips on how things can work out well all round.
If you're going to the conference, then do make sure to stop me and say "hi" - there are so many people at these events that sometimes I miss out on meeting people I'd like to have spoken to. You can't miss me, I'm the woman with the English accent and curly hair!! I had an absolutely great time last year and I'm already looking forward to this year's conference!
PHP Best Practices (tutorial) - This is a half-day tutorial with my good friend Matthew Weier O'Phinney covering all sorts of good stuff you can do when you develop PHP. Its a general session and the aim is that everyone in the room takes away something new from our tips and tricks (and stories of what *NOT* to do!)
SVN in a Distributed World I'm giving this talk for the first time, looking at how traditional source control (subversion) compares with the newer distributed version control solutions (git, bzr). There's been lots of buzz around git but in the PHP world we choose our tools on merit, not on cool factor, so this is a chance for me to share my experiences with both types of systems and talk a bit about which scenarios the various tools are a good fit for.
Open Source Your Career Another new talk! This one is about how much personal gain there is being an open source contributor. I've grown hugely, both personally and professionally, from my experience with user groups, events, and software in the open source space - so I'll be sharing some tips on how things can work out well all round.
If you're going to the conference, then do make sure to stop me and say "hi" - there are so many people at these events that sometimes I miss out on meeting people I'd like to have spoken to. You can't miss me, I'm the woman with the English accent and curly hair!! I had an absolutely great time last year and I'm already looking forward to this year's conference!
Conference Biography Help
Friday, November 20. 2009
I've been updating my conference details recently, in order to submit my talks for php|tek in Chicago (the call for papers closes on Monday - get your submissions in!). One thing which I struggled with is my biography, I used to have a paragraph which sort of said "Lorna is a PHP Developer and involved with PHPWomen", and I used that same entry for every conference for a year or more. However, just like speaker photos, biographies do date. I've taken on more responsibilities at work and I've been doing more things in the community as well so it was time for a refresh.
I'm quite happy with my new bio:
To get to this point, I started with a list of things I should include. My job, my blog, my community activity, my technical interests. There's definitely scope for including unexpected information here, I'm seriously thinking of adding my knitting hobby into this paragraph!
I then turned my points into sentences, and emailed the result to a few people to read. Even if you're secretly hoping someone else will write your bio for you, its often easier for them to criticise something you have written than to start from scratch themselves. I always take this approach even when I know I'm probably making a hash of it, if I'm asking for someone's input, I take the time to attempt it myself and send them the result. I'm enormously grateful to everyone who has reviewed my biographies and talk proposals, and I'm always happy to do the same for others when I can find the time.
Proofreaders can pick up spelling mistakes and help you put your best foot forward, it might be embarrassing to write about yourself but is it more or less embarrassing than having a lame biography printed in a conference programme?
I'm quite happy with my new bio:
Lorna Jane Mitchell is a senior developer who speaks, writes and blogs on a variety of technical topics. At Ibuildings she runs the PHP Academy, meaning she's involved in managing and coaching trainers, hosting seminars and conferences, building a training programme and representing Ibuildings within the PHP community. Lorna is the Editor-in-Chief at Ibuildings techPortal and blogs regularly at lornajane.net. In her spare time she is the European Representative of PHPWomen and is an organiser of the PHPNW user group and conference.
Getting This Far
To get to this point, I started with a list of things I should include. My job, my blog, my community activity, my technical interests. There's definitely scope for including unexpected information here, I'm seriously thinking of adding my knitting hobby into this paragraph!
I then turned my points into sentences, and emailed the result to a few people to read. Even if you're secretly hoping someone else will write your bio for you, its often easier for them to criticise something you have written than to start from scratch themselves. I always take this approach even when I know I'm probably making a hash of it, if I'm asking for someone's input, I take the time to attempt it myself and send them the result. I'm enormously grateful to everyone who has reviewed my biographies and talk proposals, and I'm always happy to do the same for others when I can find the time.
Proofreaders can pick up spelling mistakes and help you put your best foot forward, it might be embarrassing to write about yourself but is it more or less embarrassing than having a lame biography printed in a conference programme?
(Page 1 of 1, totaling 2 entries)



Comments