RSS
Facebook
Twitter

Thursday, October 4, 2012

Yesterday dawned, with a sense of foreboding (actually it dawned with me coughing my lungs out, but we've heard enough about the sub-optimal state of my respiratory system this week).   On this day, I was giving the talk I was dreading when I got asked to do it.  It's the talk I actually put more work into than any of the other sessions I was presenting at this JavaOne.  It was the Women In IT talk.

It's timely, given that conference season has one again led to cries of sexism and discrimination.  So although I really hate banging on about the subject (you'd never believe it from my blog) it's still necessary to cover.

I feel, and have felt for a long time, that the way we're approaching the "problem" of the lack of women techies is just wrong.  Obviously painting stuff pink is just not going to cut it (I hope that's obvious).  I think the fundamental problem is that we keep thinking about women.  While that should be great for someone like me, it actually triggers a whole bunch of gender stereotyping in our poor human brains which prevents us seeing the big picture - the fact that we're not attractive as an industry for women suggests we're losing a whole heap of talent because of some sort of image problem.  We just don't see the other missing minorities, or we're not comfortable talking about them.  I mean, can you image running a session about attracting more black people into programming?  I suspect there would be uproar in singling out a minority based on something as arbitrary as skin colour.

To be fair, even before the session there was a tiny bit of controversy:


It is nice though to see guys (because indeed this was someone of the male persuasion) getting upset at the thought of someone taking a shot at the girls again.  I think it probably would have been a little more helpful to the session if they'd put my name on it...

Maybe the publicity helped, because there was a really decent turnout for the talk.  I'm terrible at estimating numbers, and of course I completely forgot to take a photo of my lovely audience.  But I'd say there were... 60? 80? people there?  Between 50 and 100 anyway, and seemed like a roughly even split of men and women, and there were people of different backgrounds.  Which is great, it's more women than you normally see at a conference, and more men than you usually see at an event talking about "women's issues".  I really love running sessions about this subject with guys there, I'm of the opinion that talking about this with just women is almost completely useless, and isolates us from the rest of our community.


I took the novel approach of actually trying to treat the problem the same way coders treat any problem: break it down logically.  So I had the problem, the requirements, a retrospective, and the aim was to come up with a list of tasks going forward.

Georges Saab from Oracle was great as our "Business Analyst" - not only did he outline the business value in increasing diversity in the workplace:
  1. Greater pool of talent to hire from
  2. Happier and more productive employees
  3. Greater retention rates
He also gave examples of how this is a bigger problem than just "Women in IT" - he spoke about being the outsider as an American who had relocated to Sweden, and how he benefitted from being in a country that recognises a father's rights when his daughter was born there.

At LMAX we're super-Agile (something we'll actually be talking about at Devoxx this year), so the logical thing to do is to have a retrospective.  The question was somewhat fluffy - tell me about working as a techie, specific points about being female not essential.  So as with all our retrospectives, we covered good points, bad points, questions and ideas.

<aside>Incidentally, loads of people there knew about Agile methods and many were using them at work. Does this mean that agile is now more-or-less the norm?  Does it mean that companies that encourage people to go to conferences are agile or agile-friendly companies?  Or does it mean that people who care about people (i.e. those that go to a session like this) are more drawn to Agile methods? </aside>

(Yes, I'm wearing trainers to present, for the very first time! Thanks to Cecilia Borg for taking the photo)

((Also, special super-thanks to Stephen Chin who saved my presentation by sneaking in with a flipchart, stand and pens literally seconds before I needed it))

Everyone in the audience came up with really great points about working as a techie.  The thing I found most interesting was that very little of it was gender-specific.

Negatives

  • "Pink it and Shrink it" marketing campaigns, allegedly for women.
  • How do you get into the job?  Entry and career paths unclear
  • Micromanagement
  • The hours
  • Lack of mentoring/role models
  • Booth Babes (they are bad for women, but they are bad for men too - very demeaning to assume that guys as bright and successful as techies are drawn only to boobs)
  • Salary discrepancies
  • Brogrammers stereotype
  • Education pipeline – women doing "computery" subjects decreasing from about 13 years old and onwards (UK numbers)
  • Pressure to be visible when you're a woman/minority
  • You're seen as a woman first and a techie second
  • Time drain to keep current, 90% of what you do is learning new stuff not using skills you already had

Positives

  • Being different makes you stand out
  • The hours
  • The salary
  • Woman's perspective is a positive for the team (Later agreed that diverse teams generally were more interesting to work in)
  • We've seen an increase in the number of senior women
  • Balanced teams are more productive
  • There are lots of jobs in IT, always hiring
  • Flexibility and meritocracy
  • Women Are Exceptional (rare to get in as a girl so you're either really interested, or really good, or both)

Questions

  • I don't understand this, my CIO is a woman?
  • Is there a correlation between gamers and professional programmers?
  • Does the wider availability of technology (e.g. Facebook) lead to a wider appeal (of working in the industry) to people?
  • As parents should we be doing more to encourage our kids into technology?
  • Is the image of techies changing? 

We can replace the word "Woman" with person pretty much everywhere, and it becomes clear that we shouldn't be trying to work out the problems that face women, but instead be working harder to attract more awesome people into the job we love (I asked who in the room really hated the job, and one person half put his hand up.  So as techies, we generally like what we do), and to look after everyone who's here already as well.  So that lead on to the actions we could do to help this.

Actions


  • Look elsewhere for technical talent (e.g. people with craft skills are creative and practical)
  • We should be more actively networking (join your local JUG!)
  • Get them young - go to schools and show kids what we do
  • Challenge stereotypes - we're not geeks who live at home and code in our bedrooms, we're collaborative and creative individuals
  • We need more role models of all flavours
  • Flexible education - it should be cheaper to make "mistakes" - e.g. to switch degrees or to cross-train from other qualifications, we can't be limited by choices we made so young
  • Work experience to give kids/young people a taste of different jobs
  • Encourage / expect children to ask questions, more than just learning the school curriculum
  • Buy kids technology e.g. raspberry pi, arduino
  • Show our faces, we are all role models
  • Be vocal about our passions.  We love this job, let's tell people.

I felt extremely positive at the end of the session, I think guys saw some of the attitudes that affect women, and women saw that guys were not only sympathetic to our "plight", but that they suffer discrimination too.  Basically we're all in this together, and talking gender specifically is sometimes dividing us.

One observation that I loved was that one guy's wife wanted their daughter to do what he does because he loves his job, and she sees hers as a chore.

I also had a number of spin-off conversations later, as always happens when people are dead interested, and a really good point someone raised is that as techies we're frequently the odd one out, the outsider, in a group of "normal" people.  We're actually quite used to it and pretty much embrace it. So if anything we're an industry which will be more tolerant of your outsider-ness (as a woman, as someone who looks different) than more traditional jobs.  It's a thought, and an attitude we should perhaps publish more.

The three things I think we should do as individuals are:

1. Take The Plunge
Women in particularly, but all of you who don't think you can be That Person - start talking at conferences, start writing blogs, start a new user group if you haven't got one, go into schools.  Be that role model.

2. Don't Point Out Her Gender
I know the guys mean well, and women are guilty of this too, but don't highlight to a women at a conference/interview/meetup when you meet her for the first time that she's female.  She knows this. It's almost always said in a positive way ("Wow, it's great that you're here, we don't see many women in these parts"), and I know you mean it to be encouraging.  But it just highlights how different she is, not how awesome it is she's doing the same thing you're doing.

3. What We Do Is Awesome
We're here because we like what we do, we get paid for doing our hobbies.  Not many people can boast of that.  We need to get out there and tell people how much fun it is to be a techie.  Don't let the Hollywood geek stereotype be the only image people have of us.


I had a really good time, and I came out feeling very positive about my job, my industry, and the people who do this.  I'd love to run this session again if I get the opportunity.

EDIT: The slides and audio are available.  The content catalog is a little counter-intuitive to use, hopefully that link will take you to a page with this session title on - click on it and there's "media" on the pop up window.  This session doesn't lend itself well to audio because of the audience participation aspect but I do repeat most of the points and you get a feel for the session.

Monday, October 1, 2012

Tips for Presenters

...or, tips-for-Trisha-because-she-has-the-memory-of-a-goldfish.
  • Do not drink too much coffee beforehand.
  • Do not replace coffee with Diet Coke, it is not better...
  • Do not drink too much coffee and drink diet coke and forget to eat.
  • Check skirt length before prancing around on stage.
  • Check desktop background for public-display-appropriateness.
  • Close down applications that have popup notifications.  Do you really want hundreds of people seeing that tweet...?
  • Plug in your laptop power.  Re-typing your password every time the screen powers down is boring.
  • Remember your Mac-to-VGA dongle thingie.  Bring one even if you don't use a Mac - there might be a cute/friendly/senior/cool speaker who needs one, and you can help them.
  • Bring your slides/laptop.  Not that important, especially if you've put it on dropbox.

JavaOne: User Group Sunday



Well this is exciting!  JavaOne 2011 is the first conference I spoke at, so this the first time I've covered the same conference two years running.  I think.

It's very nice to be back at JavaOne.  Last year it was my first opportunity to meet so many people - the guys at Oracle who work really hard to make sure Java has its own identity; the JUG Leaders and Duchess folk; the JCP EC committee members; and loads of people who live and work in the area who I wouldn't normally get a chance to speak to in person.

This year I'm here with several other London Java Community people, and it's great to be a member of the Alumni, to have the privilege of showing other guys around and introducing people to each other.  It's nice to run into people I met here for the first time last year, some of whom I've had a chance to see at other events this year.

Today, Sunday, is an interesting day.  The focus is on community, so I get to hear what other JUGs are doing, some of their pain points, and learn some of the things they're doing that maybe we should think about.

The day started well, with Jim and Richard de-mystifying the business and technology terminology we're bound to come across at this conference.  8:15am is a really harsh time to have to do your first presentation, but it had a good turnout and was a great way to kick off the conference.

I followed this with a talk about why you would open source your secrets, a short presentation detailing the benefits to your business of opening up parts of your codebase.  It went better than expected, given my voice has all but disappeared due to a stupid cold and plane travel and jet lag (and noisy bars).  I had contingency plans on how to present via typing or drawing on my iPad, but in the end I managed even despite the microphone not being turned on.  Doh.


There were a series of presentations on how to make your JUG successful and how to run Adopt a JSR/OpenJDK programmes in your user group, before Ben and I had to dash off to the public EC meeting.  This was not as well-attended as last year, but it meant that I had a chance to talk to all the EC members, and to drink more free champagne than one really ought to in the afternoon.


Next on the packed schedule was a trip to yet another location (seriously, that's 4 different locations just on Sunday) for the keynotes.  Note: next time I say "it's not far, let's walk" in San Francisco, hit me with sticks.  That's the second time in as many days I've been hit with a vertical distance that was further than the horizontal.  At least this time I wasn't wheeling my luggage up the hill like I was on Friday.

The keynotes were definitely better than last year.  I really enjoyed how the technical keynote put the shiny new stuff into an everyday context - seeing JavaFX running on all the platforms, including embedded, and seeing lambdas used in anger, was really engaging.  In my mind, it's much more likely to get "real" developers using these things.  I particularly enjoyed the interplay between Mark Reinhold and Brian Goetz, it's great to see people like that so passionate about what they're doing, it really humanizes them and their projects.

The last trip of the day was back down the hill to one of the many parties scheduled this week.  Of course, it's not in every party that you get given an award, so this was particularly sweet - the London Java Community has been honoured with a Duke's Choice Award.  This is the first year a community has won a "Dukey", and it's amazing to be part of a group of people who are actively contributing to the language I work with daily, and to be recognised for this.  So yes, I was on stage getting an award again.  It's addictive.

So, a really great kick off to this year's JavaOne, and I'm back at the apartment well before my coach (well, Uber) turns into a pumpkin and resting my voice in time for my Disruptor presentation tomorrow.


Saturday, September 29, 2012

The Strange Loop

Last week (was it only last week?) I was at Strange Loop, presenting a workshop on the Disruptor.

I didn't really have any expectations from the conference, I've never been before and, if I'm honest, hadn't heard of it before.  So everything was a pleasant surprise.

It's a very geeky conference.  I mean that as a compliment, of course.  Lots of very smart people talking about stuff that's waaaay more advanced than you frequently get in the conferences employers would be happy to pay for.  The themes I mostly saw were functional programming and the (insert horribly abused term) Big Data space.

So nothing about Spring and Hibernate or any of their ilk, of course.  Almost nothing about Java actually, as if a language that is actually used by millions of developers is somehow too passé.  But this was extremely liberating - if there's nothing that's going to be applicable to my day job, I can go and see talks on things I'm actually interested in.  That's not to say the day job is not interesting, of course, but removing the constraint meant the only criteria for selecting talks was "Will I learn something I didn't know before?".

My favourite talk was Jeff Hawkins' keynote, Computing Like the Brain.  It was as if he was trying to download several decades of research on neuroscience into our brains in less than 30 minutes.  It was incredible!  Fascinating, and the stuff of science fiction.

The quality of speakers was really good, big names that many would recognise, all talking about their passions.  And it was another friendly conference, where lots of people appeared to be there on their own, and were happy to get chatting to randoms like me.

There were a lot of people too.  I had expected it to be quite a small, intimate conference.  But while it's not JavaOne, there were a lot more people than I expected.

I've never been to St Louis before either.  However, since I voluntarily spent all my time between the hotel and the venue, I think I can safely say I still haven't really been there.  But the venue and the hotel were really beautiful places, as well as being dead conveniently placed.

So I enjoyed Strange Loop.  It was a little strange, and I was out of my comfort zone, but I had an interesting time and met yet more great people.  I'd love to go again next year, if I get the chance (hint hint).

Tuesday, September 25, 2012

Strangeloop Disruptor Workshop Materials

On Sunday I gave my very first workshop on the Disruptor.  The aim was to give people some hands-on coding experience using the syntax.  Because time was limited (you can't get people to build an entire application architecture in 2.5 hours) the example is somewhat contrived, and needs a big leap to make it into a proper application context.  But the workshop should:
  1. Give an overview of the Disruptor
  2. Show how to create a simple one producer, one consumer example.
  3. Show how to wire up a parallel event handler
  4. Show how to how (and why) to create a diamond dependency graph.
  5. Extrapolate beyond these very simple examples to something closer to a real world architecture.
Requirements are:
  1. Basic Java skills
  2. Java 7 update 7
  3. (Optionally) IntelliJ.
The slides (not all that useful, I'll grant you, without me talking) are available, and you can download the code.

If you want to work through the examples yourself, start with com.mechanitis.towerdefense.TowerDefence.  The starting point code for the workshop is in package com.mechanitis.towerdefense.  com.mechanitis.towerdefense1 shows a solution to exercise one, com.mechanitis.towerdefense2 to exercise 2 and so forth.  The final package, com.mechanitis.towerdefense4, has some different towers you can play with to see the effects.  They don't really show anything special about the Disruptor, but they were fun to write and are interesting to play with.






Saturday, September 1, 2012

Upcoming Events

So yeah... in keeping with this year's theme of basically only blogging about the exciting conferences I've been to, I'm going to blog about the exciting conferences I am attending in the future.  I haven't been great at doing that, the disconnect between the time I submit a presentation and the actual announcement means that I often forget I haven't told anyone about what I'm up to.

Firstly, I'm back in the States this month to present my very first workshop - An Introduction to the Disruptor at Strangeloop.  I've been given a mere 6 months to prepare it (note: sarcasm) and it's still a work in progress.  So, if you're coming, feel free to suggest things you want to see covered.  If you are coming, I'd love to hear from you.

Secondly, I'm back in the States again a minute and a half later for several presentations at JavaOne.  I really enjoyed JavaOne last year, it was my first international conference, my first speaking gig, and a great place to meet loads of dead interesting people.  This year I'm being greedy and I'm doing more than one talk:

  • Sun 30th Sept: UGF10467 - Benefits of Open Source 
  • Mon 1st Oct: CON3732 - Concurrent Programming with the Disruptor
  • Wed 3rd Oct: CON5130 - London Java Community: How to Change the World
  • Wed 3rd Oct: CON11338 - The Problem with Women: A Technical Approach

I'm afraid the content catalog totally confounds me, so I can't link to each talk specifically, but you should be able to search on the identifiers.

Then I'm back on home turf, at JAX London, doing the Disruptor talk yet again.  I always enjoy JAX, it has a lot of participation from LJC members, it attracts an international set of speakers and it's right on my doorstep.

Finally, I'd really, really like to go to Devoxx again this year, but that hasn't been confirmed yet.  I'll do everything in my power to be there, but no promises.


Right.  I suppose I had better get back to writing this workshop...

Apologies for the interruption to your service