I'm Officially Employed

It took a while, but the visa issues have been taken care of and I’m happy to say that I’m working at Square. It’s been crazy busy and pretty exciting. I’ve enjoyed being able to work with a bunch of really smart people and Chris again (who is really smart as well).

I’ve been working on a real blog post as well, so that will show up soon. I’m off to bed after a long day.

March 17, 2010

Comments

More Projects

The February Lady Sweater is done and looks like this:

February Lady Sweater

See how it goes nicely with my living room wall?

I’m happy with it overall. The button holes I made were way too big, so I ended up sewing part of them closed. I think I would have made the yoke a little longer if I were to do it over again.

In an effort to use up a bunch of stashed Cascade 220, I’m attempting to knit owls. I’m knitting a size large in hopes of getting an extra small. So far, it’s a little on the big side, but I think it will fit. Otherwise, Sophy gets it in exchange for all the nice things she’s given me. :)

Half Done Owls

A sleeve and body in a pile on the floor

I started knitting a Robin’s Egg Blue hat today for a friend’s neighbor who was just diagnosed with cancer. It’s my first hat, so I’m excited to see how it works out. The hat needs to be done by the end of February, so owls is on hold until it is finished.

Unrelated to knitting, I’ve found a new job! Pretty much the best job ever. I haven’t started yet because there’s still some visa related issues that need to be settled, but I’m looking forward to working on some cool stuff, learning how to be a morning person again, doing Ruby professionally again (even though it’s been a short hiatus) and giving the Erlang book I borrowed back.

I wonder how many programmers besides me use a new job as an excuse to buy cute dresses?

January 31, 2010

Comments

Christmas

My Christmas present

The best puppet ever

I found it through mr x stitch and then it showed up a couple days before Christmas. I was impatient and opened it right away.

I have the week between Christmas and New Year’s day off. I have a list of things I want to do, but so far I’ve only been knitting. The February Lady Sweater is close to completion. I have one more sleeve to go. It’s been mostly painless knitting this. I left out the eyelet increases in the yoke which kept it from being too big. I can do gull lace in my sleep now.

February Lady Sweater

It's turning out okay

Jeremy also gave me a camera, so now the blog will have more pictures!

December 29, 2009

Comments

inject vs. each_with_object

I tweeted about this a while back, but I thought I’d write about how I ran into problems with inject and how each_with_object made it all better.

So I was originally using inject to create a hash of video game data from an array of div elements I was parsing with hpricot like so:

div_elements.inject({}) do |hash, div_element|
  game_name = div_element.at("//p/a").inner_text
  last_played_online_time = div_element.at("//p/strong").inner_text
  hash[game_name] = last_played_online_time
  hash
end

But sometimes, a user had never played a game online, so the text in the strong element I was checking for the time would contain something like “not played” in this case. I thought I could easily solve this by doing:

div_elements.inject({}) do |hash, div_element|
  game_name = div_element.at("//p/a").inner_text
  last_played_online_time = div_element.at("//p/strong").inner_text
  next if last_played_online_time =~ /not played/i
  hash[game_name] = last_played_online_time
  hash
end

But this was bad. Next would return nil, setting the accumulator to nil and causing bad errors on the next pass through the block. each_with_object did not have this problem. Changing things to use it looked like:

div_elements.each_with_object({}) do |div_element, hash|
  game_name = div_element.at("//p/a").inner_text
  last_played_online_time = div_element.at("//p/strong").inner_text
  next if last_played_online_time =~ /not played/i
  hash[game_name] = last_played_online_time
end

So not that different! But better. I didn’t have to worry about returning the accumulator, making things a little simpler.

December 23, 2009

Comments

Being a Girl Programmer

I’ve been ask a couple of times recently what it’s like being a female developer, and it’s one of those questions that I’m probably going to be asked as long as I code. I feel like earlier in my career it was a drawback. I’m pretty shy and I’ve lacked confidence in a lot of areas of life, and I think the combination of these two things and my gender made me seem less smart to some of my coworkers in the past. A couple of years ago, when I was working on my first Rails project, I had a coworker tell me (while drunk at an after work dinner) how he had assumed that I had no skills whatsoever and how surprised he was at how good some code I had written was. Besides that, I’ve had more cases of people assuming that I was more junior than I really am. I don’t think that my gender was the only reason for that, but I think that it’s been part of the problem.

As I’ve gotten older, I’ve realized that I can overcome people’s assumptions or keep them from making them in the first place by both being able to talk about things I know and writing good code. I’m still learning how to express myself better and I feel like I’ve failed a couple times to explain something as well as I wanted, but I’ll get better the more I do it. I don’t think I’ll ever be loud and highly opinionated, but I think that’s a good thing.

Also, I’ve been confused with every other female developer/qa/intern/admin that I’ve ever worked with. Maybe t-shirts with names on them would help with this?

December 13, 2009

Comments