Well we made it back from Portland after a great weekend at RailsConf. I had mentioned that I wanted to learn a few things and meet a few people, and I'm happy to say I did just that. I think that this year, the meeting people was more important to me than the sessions. That said, I think there are a handful worth mentioning.

Surviving the big rewrite, moving yellowpages.com to rails, John Straw

It was pretty cool to hear how yellowpages.com just decided to rewrite their entire system in rails, and did it with only about 3-4 months of development. Impressive. John Straw attributes the success to a few things:

  • Having a small development team
  • Choosing the right platform
  • Having close communication among team members with diverse viewpoints
  • Freezing development on the existing site in order to prevent having to hit a moving target
  • Updating the beta site frequently to easily communicate progress

The Launch: Dos and Don'ts of Real Life Deploys, Chris Wanstrath

Chris Wanstrath went through the stages of deployment: Alpha, Beta, Optimization, Launch, Panic, and Calm. It was cool to hear him talk about his real-life projects, famspam and the famous github, and what he experienced during deployment. I took away from this talk that Alpha and Beta phases are great tools to get feedback from your users and uncover any bugs. It also allows you to assess what really needs optimization before the real launch. Also, something goes wrong in almost every launch, so expect that there will be downtime.

Using Git to Manage and Deploy Rails Apps, Scott Chacon

OK, all I can say about this one is that this guy talks really fast and knows a TON about git. There is good info about the talk here and you can check out his gitcasts for some more git goodness.

Scaling Rails, Blaine Cook, Bradley Taylor, Ezra Zygmuntowicz, Jim Meyer, Kevin Lawver

There were a couple of quotes from this talk that I thought were insightful. The first was Ezra, who said "the most important thing is getting your application out there and getting the opportunity to have to make it scale." I think that's great because it seems as though a lot of people try to prematurely optimize. Just get it out there, see where the weaknesses are, and then you can spend meaningful hours making it scale. The other quote I liked was from Blaine Cook, of Twitter, who said the biggest mistake developers make is "assuming the production environment is exactly like the development environment." I don't have a lot of experience with real deployments, so this one stuck with me. I hope I remember it when it counts.

ActiveRecord Associations and the Proxy Pattern, Nick Kallen

This was the talk that really made me say, "Wow." Nick Kallen flawlessly coded for the entire session, showing the audience the basics behind ActiveRecord associations. I can't say I've ever thought about what I would do if :has_many didn't exist, and it was really cool to watch him go through the steps... and writing tests first.

Other highlights of RailsConf 08 include but are not limited to:

  • My railsconf t-shirt that actually fits!
  • Hanging out with about 30 other women developers at the DevChix meetup. Thanks again to Desi for getting us all together and Obie for picking up the tab. :)
  • The moment when DHH accidentally bumped into me... 'cause he's so dreamy. sigh. (HA you know I'm joking, right? :) )
  • Visiting the monstrosity that is Powell's bookstore. I'll be reading for months!
  • Being pinged in the #railsconf irc channel by someone who reads my blog! Yay for readers!
  • This picture of me clearly looking at my laptop and not paying attention to whoever was speaking, taken by James Duncan Davidson.

All in all it was a great weekend. See you next year in Vegas.

RailsConf is this weekend! I, along with the rest of the Integrum team, will be arriving in Portland tomorrow (Thursday) evening, so find us and say hello! I hope to learn a few things and meet a few people, and I'll be sure to post notes and thoughts here next week sometime. Should be a fun time, hope to see you there!

Did you see this lovely derriere at RailsConf? If you did, you better have already checked out railsresources.org!

Rails Resources was created by Josh, Jade, and Derek (my co-workers at Integrum) and will soon become a place where we all can go to keep up with what's going on in the rails community.

So even if you missed my shameless advertising at RailsConf, go to railsresources.org anyway and subscribe to the RSS feed.

I mentioned before that earlier this month I attended RailsConf in Portland, Oregon. A good time was had by all and amidst the impromptu band performances and drinking parties, I managed to learn a few things. I attended a talk during every session, some of which were very cool and others made me sleepy. Below is the list of talks that I think deserve mentioning.

Clean Code, by Robert Martin

Robert Martin is an exceptional public speaker, and during this talk he made some great points about refactoring and cleaning up bad code. He stressed that the best way to improve bad code is to make a series of small changes and continuously run your tests. My favorite part of this talk was the metaphor that he used to describe how easy it is to write bad code and what happens when you do. He said, "The quickest way to be done with dinner is to just leave the table." If you keep doing this, eventually you just have one big mess. (i couldn't find the slides, but here are the materials from the railsconf site.)

Custom Rails Helpers: Keeping Your Views Dry, Glenn Vanderburg

The emphasis in this talk was on keeping different languages separate from each other. Views are commonly messy because we neglect to refactor javascript, html, and ruby into separate files. Glenn Vanderburg included several tips and tricks for building custom helpers to clean up your view code. (slides)

Practical Design for Developers, David Verba

In this talk, David Verba emphasized the importance of getting to know our users. He talked about the 5 elements of user experience; strategy(what do we want out of our site?), scope(what features will the site include?), structure(how will the pieces of the site fit together?), skeleton(what components will enable people to use the site?), and surface(what will the finished product look like?). As a developer, I enjoyed this easy-to-understand explanation of the elements of design. (slides)

The Mysteries of JavaScript-Fu, Dan Webb

Dan Webb did a great job of entertaining the audience while educating them on "the ancient manuals of javascript-fu." According to Dan, these ancient manuals include working with events, working with dom elements, optimization, and progressive enhancement. He outlined several best practices, such as using script-based event handlers whenever possible, not using "javascript_include_tag :defaults" unless you really need all the defaults, and always providing a non-javascript version of your site. (slides)

Rubber, Meet Road: Getting Designers Running with Rails, Amy Hoy

"Stop, collaborate, and listen." This was Amy Hoy's solution to the big miscommunication problem between designers and developers. She gave a very engaging talk about how designers and developers should interact. Amy said that we should involve our designers early and often, and avoid the "me vs. you" mentality. It all boils down to respecting and having patience with each other, even when we don't understand each other. (slides)

And that concludes my RailsConf recap... Thanks to all the presenters for sharing their knowledge.

Last night I went out for a couple of drinks with the guys from Integrum, and we ended up having quite the discussion about our work environment and our specific personalities. We talked a bit about the difference between men and women in the programming world; a topic that I find particularly interesting seeing as how I am one of few women in this line of work. One of the guys asked me if I thought it was hard to be a woman at Integrum, and I think he was surprised when I said "yes." The truth is, it's not Integrum that makes it hard for me, but the industry itself. Whether we like it or not, it is harder to be a woman developer than it is to be a man. I've actually been very lucky at Integrum, because while it's still hard for me, I give all the guys a lot of credit for allowing me to prove myself. Sometimes, women don't even get that chance. I like to think that I am good at what I do, and I want to be thought of as a good (maybe someday, great) developer and not just a chick who thinks she can code.

While I'm talking about women in development, I'd like to give a little shout out to the devChix, a group of women developers with a mission to create a community for women in development to try and make it easier for them. At RailsConf I got the chance to meet Desi and several other women in the group, and I must say it was nice to chat with other women who know how I feel.

Thanks to all the guys that were there last night voicing their opinions, and to my friend Jenna for helping me sort through my thoughts today. I am proud to be a woman in this field, and I will continue to try and prove that I belong here.

Lindsay Ucci (aka Ooochie!)

Lindsay Ucci

Ruby/Rails developer and wannabe pastry chef. :)

Welcome to ooochie.com! I'm Lindsay Ucci, a web developer workin' my life away at Integrum Technologies, a rails consulting shop in Chandler, Arizona... and having tons of fun doing it.

Design by Dan Ritz, FeedBot by Matt Forsythe, and Powered by Mephisto