Women Engineers Show New Confidence About the C Word

I've been spending quite a few evenings of late at the Girl Geek Dinners, the Women in Technology events and various women leaders in technology things. The generation gap between the older girl geeks who fought for equal treatment and the girl geeks coming through now who thankfully don't have to see or do the things we oldies saw or did back in the day is fascinating to me, and worth a post in its own right, but today I'm excited about something else: the 'C' word.

Until relatively recently, the women engineers that I've worked with have been very careful about mentioning their children (the 'c' word in question, in case any of you thought it might abbreviate something else). As a general rule, I've seen secretaries and PAs put pictures of their children on their desks, chat openly about their children's development, take time out to look after them as a right. But female engineers. Photos were rare, talking about kids restricted only to close friends, time off always accompanied by embarassment. And never, and I mean *never*, did anyone have that conversation about relative priorities, about the real work-life balance. And even considering it in front of the men? Noooo.

But this week I've seen a senior woman engineer do just that: tell everyone that her priorities shifted for a while when her kids were young. And she did this in front of her (male) boss. And nothing exploded. This past year, I've seen several women presenters list their children amongst their significant achievements (and we are talking some very senior women indeed), and professional women out and proud of their side-by-side roles as both professionals and mothers. And this is so wonderfully refreshing. I never became a mother myself, but I am proud that we have grown up so much as a profession that women don't have to choose between images any more. I couldn't be part of this particular movement myself, but to those women who did have the courage to say "I'm a mother too", I salute you.

Meanwhile, on a slightly less historical note, I've found and signed up with an interesting volunteer effort - IT 4 Communities. It's a place that puts geek and charities that need geek skills together, and as such it's much to be encouraged.

The Internet doesn't know everything any more...

...not that it ever did, but for a long time there were lots of people like me around the world, spending time getting as much information into the Internet as possible (with the added aim of making as much of it accessible as possible as well). But now there are gaps. There always have been gaps, but where they existed and were important to someone or anyone, they were filled with information by enthusiasts of model trains, language quirks (big nod to Tylor Jones and his June29 language site), research papers (citeseer) and a whole host of things that most people didn't know existed til then. But that doesn't happen so often anymore. I was an early adopter of the Internet (see under Geek Code) but I think I blinked, and in the time that I was blinking, the Internet went from being an inderground collective dedicated to freedom of information and became a series of newsletters, with editors and rules and regulations. I think I've been aware of this change happening, but it really hit home last week. I tried to look up my road race times over the last few years. I run - slowly but steadily - and I needed proof of that for a race entry. And so I looked myself up, in the comfortable expectation of finding at least 10 years of staggering round courses all over the country at just under 10kph. And nothing. Or nearly nothing. I've run some very big races: the Great South, Great North, London; and some very small races: little local things that one man and his dog turned out to watch (and the dog was more interested in the local rabbits). And I thought, naively, that the times and field for each of these races would still be held somewhere on the 'net, easily accessible for me to check whether I came in at 6704th or 6705th. Nope. Not there. Now back in the day, runners were an enthusiastic bunch: you ran, the results got posted and stayed on the net for you to look at later. Not any more.

I did find a couple of little local results back from -ahem- 1999, which was nicely parish-magazine. But I was quite shocked at the lack of big-race data. F'instance: the Great X series. One year's data only. Now given how much it costs to store data for a 10000 person race (name and time) compared to even a small video... heck, let's do the thought experiment on that one here... a race field of 10000 people: give them 30 digits each for their name and two digits for the time they finish in: I make that 320,000 bytes. Now compare that with a single 480*640 pixel digital camera image: 307,200 bytes in black-and-white, and three times that for colour (each pixel in a typical colour image has one byte each for red, green, blue). So if storage isn't the issue, what is? Is it access costs? Publication rights? If the race organisers put up the results for each year, they must actively remove the old ones every year, and I'm puzzled about why. I mean, it's bad enough with people selling rights to view public information without that information being completely removed as well. What's going on, folks?

SQL, the -erm- sequel

And so to SQL. I've found a lovely little site called SqlZoo to brush off my sql rust with: it's very enthusiastic children's television meets quite gentle learning. I like. Thank you chaps.

Blog tracking

Well, I did try Google Analytics, but didn't really get on with it. So now it's time to play with IceRocket's tracker; link courtesy of a visibly shrinking (courtesy of the diet) Gemma. It will be interesting to see what happens, and whether I really do have an audience of 1.

c sharp

Okay, time to learn c#. So far, all I know about it is that it's a C++ nd Java-like hybrid that's nanny-like in its control of variable use (in fortran, implicit none was a good idea; removing the ability to shadow global variables with local ones seems to be very market-specific, i.e. if you have to hack in this language, it's going to be even messier than usual).

Anyway, onwards: onto a tutorial or two, then back to TopCoder to test out my new skills...

Teeny weeny 'puter things

Gad but I have a cool job sometimes. Right now, it's playing with teeny-tiny components, some of which I want to remember here (just in case I feel like building some strange bots of my own). So... cool little gumstix computer, C328RS camera, and a cute little 5dof imu. Not that this is fun or anything, but... well, it's fun okay. Although the soldering-related screaming and sticking-plaster bonanza are bound to start soon...

First python

Okay, so I didn't break into Google (not in the conventional sense anyways. There was this misunderstanding with an oversimple instruction and an unlocked door, but we'll gloss over that...), but I did get the building-stuff bug back again, which can only (as long as you don't have to share any space with me when I'm coding at 3am) be good.

So. Today. My first Python program. Had bought the book and skimmed the language ready for the above, and was just having a snuffle round the big G's website when I fell over their coding pages. And the Google App Engine. It's a cute little beastie (so far), but we'll see how I do when I get past the 'Wahey! Hello World!' stage. And I really need to sort my path out asap; it's not good typing in the whole thing every time...

Things to remember include: http://localhost:8080/