ooochie - Home

Party On

2011-11-30T14:59:00Z

Hello my dear readers, and many apologies for my serious blog neglect as of late. Some may already know this, but back at the end of June, I decided to make a change. I left my position at Gazelle to pursue an opportunity at a little startup called Punchbowl. Leaving Gazelle was hard to do - but it was the right time for me and I wish them the absolute best. I was actually a customer of Punchbowl before I became an employee, and that's been a fun perspective and an interesting transition for me. I've really enjoyed getting back into a true startup environment, and my new 20 minute commute (as opposed to an hour!) is doing wonders for my psyche.

With the holiday season upon us, you may be interested to know what Punchbowl does. The site offers a comprehensive party planning tool - from getting your friends to help decide on a date, to sending invites and allowing them to choose items from the potluck list. We also recently released our brand-spankin-new free ecards: Digital Greeting Cards with the look and feel of paper cards. There's even a special section for business christmas cards for all you classy professionals. It's all the rage, kids, so go send some good cheer, plan that holiday gathering, and party on!

Things I Learned in Grad School #3

2011-03-23T12:16:00Z

Hmm I wrote this article ages ago, but apparently never posted it (insert apologies for neglecting my blog here). Here's another tasty morsel from my Intellectual Property class:

Non-Compete Clauses

Often when you work as a contractor, or even sometimes as a full-time employee, companies include non-compete clauses or agreements in the paperwork you have to sign. A Non-Compete basically says, "if you leave this company you cannot go to work for one of our competitors." But did you know that it's extremely difficult to enforce a Non-Compete? Courts don't like to enforce them because they put people out of work, thus taking away their livelihood. In order to successfully enforce a Non-Compete, Company A must be able to prove that the employee is giving Company B, their competitor, Company A's trade secrets. Just the desire to avoid competition is not enough to put your ex-employees out of work.

P.S. Just like before, please note that this information applies to United States law. Would love to hear how this works in other parts of the world!

See you at RailsConf!

2010-03-15T14:58:00Z

It's official, I'll be attending RailsConf this year in Baltimore! I didn't get to go last year since I was out of the country, so I'm looking forward to getting back in touch this year. (And being a student certainly pays off... the student discount was a very pleasant surprise!) I also plan on checking out the Ignite RailsConf event which looks like an interesting addition to the program this year. Hope to see you there! :)

Things I Learned in Grad School #2

2009-11-19T13:18:00Z

Recently we had a guest speaker come in to my marketing class to talk about qualitative research interviews. She had some great advice for interviewing customers and getting valuable information out of them. Here are some tips I learned for conducting customer interviews:

Be Prepared, Yet Flexible. Always have a list of questions, but use them as a guide. Let the content of the interview go where the customer takes it.
Show You Care. It should be obvious to your customer that you care about what he or she has to say. Pay attention! If you don't care, why bother?
Don't Interrupt. Never interrupt your customer while they are telling you a story. Instead, make a note of what you wanted to ask about and ask it when the story is done.
Pause. When the customer is done telling you a story, pause for slightly longer than you normally would, just to be sure they don't have anything else to add.
Be Encouraging. Non-verbal communication (i.e. head-nods) and minor vocalizations (i.e. "Mmhmm") show that you are still paying attention and encourage the customer to keep talking. Also, don't be afraid to probe the customer for more information with short extending questions like "Can you offer additional details?" or "What happened next?"
Don't Talk About Yourself. Customer interviews are NOT a two-way conversation - let the customer do the talking. You won't get accurate information by offering up your own insights and opinions.

I used to think that these techniques could only be used for market research at large companies who are developing new physical products, but after this particular class I started to think about how qualitative research applies to software development. Every one of these tips should be applied to our relationships with customers - especially in our initial meetings.

As developers, we often get ahead of ourselves and start planning out a product before we fully understand what our customers want. In my opinion, the first meeting with a customer should be exactly like a qualitative research interview. Allow the customer to talk at length about what they need and what kinds of problems they are trying to solve with the software. Show them you care about what they have to say and hold off on offering up your personal opinions. By structuring our initial meetings this way, we can get a clear, unbiased picture of the situation and create better solutions for our customers.

Ruby on Rails Workshop for Women

2009-10-26T00:02:00Z

This past weekend I volunteered to be a Teacher's Assistant at the Ruby on Rails Workshop for Women at Harvard University in Boston. I have to say that I was really impressed by the whole event. Sarah Allen and Sarah Mei started doing these workshops in the San Francisco Bay Area, and I'm really glad that Sarah Allen made her way to Boston so we could have one too. There was a great turnout; a mixture of women of all skill levels and ages, and yes, there were some men there too. It was really refreshing to be in a room full of so many kinds of women programming Ruby on Rails.

In her intro, Sarah described her hope to one day attend a meetup where she did not "personally double the number of women" in the room. I certainly know what that's like, and I'm so happy I made the choice to donate a Saturday to this event. This workshop felt so different than any Ruby or Rails event I've attended. There was no judgement, no attitude, no "are you really a rails developer?" - there was just a bunch of people who wanted to learn and some other people who wanted to help.

Thanks so much to Liana Leahy and Mary Tolbert for organizing this event, and to Sarah Allen and Andy Gregorowicz for presenting to the group.

You can read more about the workshop in some post-workshop blog posts from Liana, Sarah, and Andy.

Things I Learned in Grad School #1: NDAs & Trade Secrets

2009-10-12T22:01:00Z

So I've been in grad school for about a month now, and it's going really well so far. It's a ton of work, but my classes are super interesting so I can't really complain too much. :) I decided that I should start a new series of articles on this site, henceforth to be known as "Things I Learned in Grad School." As you probably can gather from my oh-so-creative title, I plan on doing a series of short posts with some random but useful things I learn while I'm at school. So let's hit the ground running with a couple of little tidbits I learned in my Intellectual Property class!

NDA's & Trade Secrets

Did you know that it's not always necessary to make your employees or partners sign a Non-Disclosure Agreement (NDA)? Or if you're the employee, did you know that if you haven't signed an NDA you are still obligated to keep your employer's trade secrets private? Though an NDA is the easiest way to prove in court that ideas were supposed to be kept private, it's not the only way to win a case of stolen secrets. Your ideas and trade secrets are automatically protected by trade secret law as long as you make a reasonable effort to keep them secret. There are also some relationships (such as employer/employee) where the law assumes confidentiality. So if you haven't signed an NDA, don't assume you can shout other people's secrets from the rooftops, and make sure you know your rights if someone's shouting yours.

P.S. This information is based on United States laws. I'm not sure how it works in other countries, but if you know please enlighten me in the comments. Cheers!

I'm Back!

2009-07-14T22:15:00Z

Oh hey there... it's been a while, eh? I've been just a teensy bit busy saying goodbye to New Zealand, traveling around Australia, flying back to the US, emptying my storage unit in AZ, packing my life into 2 small vehicles, driving across the country, catching up with fam & friends, and finding a place to live in Boston. But enough with the excuses, I'm back now!

For those that didn't know, I'm going back to school this fall at Northeastern University. I'm super psyched about getting a master's but a little nervous at the same time. It's weird to be doing the school thing again. Anyways, I'm moving to an apartment in Boston in a couple weeks, so I have a new community to infiltrate! If you're in town, let's hang. :)

P.S. I'm also looking for part-time rails work in the city (or I'm willing to work remotely) while I'm in school, so if you know anyone with an opening, I'm all ears!

SonarHQ - Online Polls & Surveys

2009-04-23T07:45:00Z

My last few months have been dedicated to the development of Boost's new online survey tool, SonarHQ. This past week, we released SonarHQ into Beta, and its live for you to use! It's exciting to see it out in the wild... we hope you enjoy it! We'd love to hear your feedback so check it out and let us know what you think. Here's a bit more information about SonarHQ:

What SonarHQ Does

Directly from the SonarHQ homepage:

Fulfill your consultation requirements
Build two-way conversations with your customers
Develop groups for ongoing surveys
Create one-off surveys and questionnaires
Easily create beautiful graphs and reports
Easily administer your feedback and reports
Quickly arrange findings for private or public analysis
Keep your stakeholders well informed.

In my own words:

SonarHQ is, in short, an online polling system. It is especially useful for people who are interested in building a community of members that they can poll about certain topics. SonarHQ was extracted from older code that runs The Couch, a community of New Zealand families. SonarHQ allows you to easily create polls, collect answers, and report on your findings - all on your very own website.

The Tech Specs

SonarHQ is a Ruby on Rails application. It's currently running Rails v2.2 on a SliceHost Ubuntu server. We're using Workling/Starling for background processes and we've rolled our own flash graphs for charting poll results. The app is (mostly) RESTful and we're leveraging that fact in order to create reports for ourselves via ActiveResource. We're using Chartbeat and New Relic to monitor the application and we've got a Tender app set up for support.

So that's about it. Go take a little looksie and then sign up! Play around and be sure to let us know what you think. :)

Burned by Workling & Starling

2009-03-28T03:48:00Z

I'm using the Workling Plugin with Starling on my project at Boost to run processes in the background. Recently, we deployed 2 projects on the same server, and rather than run 2 separate instances of Starling, we just let both apps talk to the same Starling instance. All was well with the world until I noticed that one of my apps was mysteriously creating records in the other app's database. Burn! It appeared that Starling didn't know which app the processes belonged to, so it was always running them on 1 app and never the other one. Eeek!

Thankfully, this was easily remedied by revisiting the options for my workling.yml file in the Workling README:

Workling copies a file called workling.yml into your applications config directory. 
The config file tells Workling on which port Starling is listening. 

Notice that the default production port is 15151. This means you'll need to start 
Starling with -p 15151 on production. 

You can also use this config file to pass configuration options to the memcache 
client which workling uses to connect to starling. use the key 'memcache_options' for this. 

You can also set sleep time for each Worker. See the key 'listeners' for this. 
Put in the modularized Class name as a key. 

    development:
      listens_on: localhost:22122
      sleep_time: 2
      reset_time: 30
      listeners:
        Util:
          sleep_time: 20
      memcache_options:
        namespace: myapp_development
        
    production:
      listens_on: localhost:22122, localhost:221223, localhost:221224
      sleep_time: 2
      reset_time: 30

See that key under memcache_options? Namespace to the rescue! If you set this in your workling.yml file, your Starling instance will never be confused again. Just a quick tip so you don't get burned like I did. Good luck!

Ada Lovelace Day

2009-03-25T00:10:00Z

Today is Ada Lovelace Day - "an international day of blogging to draw attention to women excelling in technology." I only just found out about it, so unfortunately I don't have an article prepared, but I wanted to help by raising a little awareness and inviting you to go read some of the articles that have been published today in honor of women in technology. Here are a few to get started:

Ada Lovelace Day - Finding Ada by Desi McAdam
Ada Lovelace Day heroine: Valerie Aurora by Mackenzie Morgan
Celebrating Ada Lovelace Day by Audrey Eschright
Ada Lovelace Day - Grace Hopper by Brenda Wallace
Ada Lovelace Day by Liz Henry
Ada Lovelace Day: Tribute to Suw Charman-Anderson by Kevin Anderson (Husband of Suw Charman-Anderson, creator of Ada Lovelace Day)

There are several more links to articles on the pledge website. Even if you don't sign the pledge or write a post, today I encourage you to think about all the tech women you know & celebrate them. :)

Webstock Highlights: Day 2

2009-03-09T00:28:00Z

So Day 2 at Webstock was just as fab as Day 1. As promised, I put together a few of my favorites from Day 2.

Derek Featherstone - Madame Butterfly

Derek's talk was about accessibility. It was a great session, and it made me realize that accessibility is not something I really think about, but it definitely should be. One thing he said that I really liked was this: "Just because something is compliant doesn't mean it's easy to use." I think this statement applies to so much more than accessibility. We need to focus on user experience as well as standards compliance. In addition to that, Derek totally wowed me with some of the things he's working on using Ubiquity to improve accessibility.

Joshua Porter - Designing Sign Up Screens & Flows

After hearing this talk, Joshua Porter's book, Designing for the Social Web, went directly onto my wish list. He had so many valuable tips about signup processes, most notably the fact that the form is not the problem with signup - the problem is changing peoples minds about your software. While the form can certainly be an obstacle, the process is much more important. Specifically, I liked the way Josh described the three types of people you should design for: the people who already know they want to sign up, the people who want more information to make sure your product is for them, and the skeptics. It was quite interesting to think about a signup process in this 3-tiered manner.

Bruce Sterling - The Short but Glorious Life of Web 2.0, And What Comes Afterward

I'll let you read the transcript and draw your own conclusions about this one. :)

Damian Conway - Web 2.0.1.

I thought this was a great way to end Webstock. Damian Conway sent us forth with a mission to implement the "Theory of Hippocratic Web Design". He said that we can collectively change our ideals and become people who really care about those we serve. The practices for Damian's theory seem so simple, but often they get overlooked. These things should be part of how we work everyday.

Learn and share good practices
Do your best work
Know your own limitations - don't pretend you're an expert in technologies that you're not.
Work in your client's best interest - don't screw them over!
Be professional

So by now I think I have sufficiently convinced you that Webstock contained heaps (as the kiwis say) of awesomeness. I'm so glad I went and I hope to get the chance to attend future Webstocks. Thanks to all the speakers and all the fun people that took the time to chat with me!

Webstock Highlights: Day 1

2009-02-24T06:34:00Z

Well friends, Webstock is over and it turned out to be totally awesome. It was well-planned, well-executed, and loaded with high-quality content. I had the opportunity to meet/chat with one of the organizers, Mike Brown, and he is not only an all-star conference planner, but a genuinely nice dude. There was so much awesomeness from the speakers that I'm going to split my overview into two posts: one for each day of the conference. My highlights from the presentations on Day 1 are as follows:

Jane McGonigal - Gaming Reality

First of all, Jane is just an incredibly cool person. She's fun to chat with and, quite frankly, cookies make me happy too. :) Her talk made some great points about how games really optimize human experience by appealing directly to the things that humans crave:

having satisfying work to do
being good at something
spending time with people we like
having the chance to be a part of something bigger

One of the points she made toward the end really stuck with me. She said that considering the current state of our world (climate change, sucky economy, etc.), we all need to become "game developers" and apply these things to all of the software we create. We should be thinking about how to structure user experience to make people happier, and how to develop systems that really make people awesome.

Matt Biddulph - Made of Messages

In this talk Matt discussed background processing and said that we should perform only the most basic calculations up front and show the user only what effects their world at that moment. The complex calculations can be put on a queue to be processed later. One of the things Matt mentioned really made me think. What does background processing do to interaction design? Now, I'm no designer, but I've never really thought to mention to the designer that I'm working with that some process is happening in the background and the information may not be available immediately. It seems now like something they should definitely know about in order to not mislead the user or create confusion.

Heather Champ - Shepherding Passionate Communities

Heather Champ, of Flickr, gave an insightful talk about 7 lessons she learned while managing the passionate flickr community. She had a lot of good stuff to say, but there were two that I liked best. First, Heather said that feedback has a lifecycle. The feedback you get in the first 48 hours is usually full of gut reactions to change, whereas over a 2 week period you get more thoughtful feedback. The second one I liked was this: Own your failure. If you screw up, tell your users you screwed up without making excuses. Then turn it into something fun.

Michael Lopp - Being Geek

This was a really fun talk and affirmed my suspicion that I am a total nerd/geek. But definitely not a dork. :) He talked about the cliches of being geek and what they mean about our personalities. Nerds are supposedly good with computers, obsessive, and awkward. But in actuality we just love puzzles, don't want you touching our stuff, and are always trying to figure out how people fit into our system. :)

The rest of the speakers from Day 1 were just as good: Nat Torkington, Cameron Adams, Derek Powazek, Adrian Holovaty , and the ever-hilarious Ze Frank. For the sake of keeping this less than a zillion words, I won't summarize them all, but I was truly impressed with the quality of the speakers as well as their content.

Stay tuned for thoughts on Day 2.

Fun Times in Wellington

2009-01-22T05:13:00Z

I realized that I haven't written yet about some of the events I've been to in Wellington, so I thought I'd give y'all an idea of what I've been doing for the past 3 months. I've been trying to infiltrate the nerd community here and meet as many people as I can, so here's a few of the events I've attended and what I thought of them.

WellRailed (November)

WellRailed is the Ruby on Rails group in Wellington. I've been subscribed to the mailing list for a while now, and it was cool to meet some of the people that I see writing on the list all the time. I liked the style of the meeting and I thought it was productive. It started with drinks, pizza, and socializing, and then moved into two short talks by Paul Flewelling (i18n in Rails 2) and Will Bryant (submitting a patch to Rails on github). I'm looking forward to attending more of these meetings before I leave NZ.

Tweet-Up (November)

This one is pretty self-explanatory. I thought this was a great event for meeting people, and following new people on twitter helps me keep up with what's going on in Wellington.

Women in Technology (December)

I happened to stumble across the Women in Technology website one day and was quite intrigued. I emailed and asked if I could attend one of their meetings just to see what it was about. When I got there, I quickly realized that their idea of 'technology' was not quite the same as mine - i.e. it was not a room full of programmers, but women who use any type of technology in the workplace. I did, however, really enjoy the presentation. A woman from Auckland talked to us about how to properly give a presentation. It's really amazing to learn from someone while they demonstrate just how much they know about their subject. She was an excellent presenter.

Girl Geeks (December)

Last year Erica and I attended a Girl Geek Dinner Event in San Francisco, so when I saw that Wellington had a Girl Geek Community I was pretty excited. I went to their Girl Geek Drinks event and there was a great turnout! It was so nice to meet a bunch of girl geeks in Wellington. I hope to be able to attend more of these events while I'm here.

Webstock (February)

Next month I'll be attending Webstock! I am really looking forward it, and will surely post here about my Webstock experience. Hope to see you there!

P.S. In other news, Dan and I had a lovely holiday traveling around NZ's South Island. You can check out the photos on my flickr.

My 6th Photo

2008-12-15T20:14:00Z

So I have been tagged in "The 6th Meme" by this clown. I have been instructed to post the 6th photo on the 6th page of my flickr stream, so here it is:

This photo was taken on the last day of my Fiji trip, in the Garden of the Sleeping Giant, just outside Nadi. This pond with all the lily pads was my favorite part of the garden.

I hereby tag the following people to post their 6th photo and pass it on:

Ready, set, go!

Validating Uniqueness with Acts As Paranoid

2008-11-26T00:07:00Z

I've recently been using Rick Olson's plugin, acts_as_paranoid, to mark records as deleted rather than actually destroying them. When I had my model acting very paranoid, I found myself wanting to ignore the 'deleted' records when validating newly created records. For instance, I have an Account model:

class Account < ActiveRecord::Base

acts_as_paranoid

#Validations
validates_uniqueness_of :subdomain
end

As it stands, when I create a new account object with a subdomain of "foo" and try to save it, it will be invalid even if the existing record with the "foo" subdomain has been marked as deleted. I needed to treat the deleted records as if they no longer existed. To remedy this problem, I overwrote validates_uniqueness_of inside acts_as_paranoid to take an option to exclude deleted records.

So after updating the plugin, I can pass the :without_deleted => true option to validates_uniqueness_of and the record will be valid if no other active records have the same subdomain. Here's the whopping 1/2 line change to the model:

class Account < ActiveRecord::Base

acts_as_paranoid

#Validations
validates_uniqueness_of :subdomain, :without_deleted => true
end

And that's it! Pretty simple change, but I found it useful. I don't know if this is something anyone else needs to do, but feel free to grab my version of acts_as_paranoid from my github repository if it helps.

Saying Kia Ora to Wellington and Boost

2008-10-19T02:08:00Z

I wrote recently about leaving Integrum, but I failed to mention that I was also leaving the country... :)

I decided a few months back that I wanted to live and work abroad for a few months, and after some searching around, I chose New Zealand. It's weird that it has finally arrived, but I am happy to say that I've just moved in to a flat in Wellington. I've never been to the South Pacific before, so I'm excited about the opportunity to see this part of the world. So far Wellington has been amazing! The city is so pretty and I love being close to the water. Our flatmates are super nice and have been very helpful in getting us settled in.

Tomorrow I start my new job at Boost New Media in downtown Wellington. I met the team on Friday, and they seem like such a fun bunch! I definitely want to check out the local rails scene and meet lots of people, so please get in touch if you are in the area. Oh, and if you need design stuff done, Dan is available and looking for contract work. :)

See you around Wellington!

Saying Goodbye to Integrum

2008-09-25T17:34:00Z

1 year, 10 months, and 21 days ago, I walked in to the Integrum offices for my first day of work. I had no prior professional experience and I was scared out of my mind. I have recently decided to leave Integrum to pursue other opportunities (which I will write about soon), so tomorrow is my last day at Integrum. I thought it appropriate to publicly say goodbye, and more importantly, thanks, to all who influenced my time there.

I was so surprised when I received the email from Jade originally offering me a job. With my lack of experience, I never expected it, and I will always be grateful for the opportunity I was given. To Jade - It was a leap of faith to hire me and believe in me, and I can only hope I've made it a worthwhile choice.

Through all the changes I've seen the company go through, the best part about working at Integrum has always been it's people. I could not have asked for better coworkers - you guys are such intelligent people with incredible ideas and potential to do big things. I owe each and every one of you a huge thank you for making me the software developer I am today, not to mention the person I am today.

I'm not good at goodbyes, but what I'm really trying to say is: Thanks and I <3><3>

Edward Tufte

2008-08-25T04:31:00Z

This past week I had the opportunity to attend Edward Tufte's one-day course in San Diego, CA. The course was on presenting data and information, and it turned out to be really interesting stuff. I took some notes, which certainly do not do it justice, but I thought I'd post them here anyway.

Some tips on presenting information in charts:

Annotate lines in charts (bring character to the linking lines) - give them meaning, otherwise they are all the same and don't really mean anything.
The nouns should also be annotated - the detail is what gives the credibility and character.
"Clutter and confusion are not attributes of detail - they are failures in design." Replace the "chart-chunk" with information.
Keep in mind that the audience has to understand your story and decide whether they believe you or not - it depends on the quality of your presentation and sources.
"You should have an open mind about alternatives, but not an empty head" - Your information is accurate at least until better evidence or alternative explanations come along.

Using a "Super Graphic:"

High resolution displays are genuinely interactive - Use a high resolution display, like an aerial photograph, to open your presentation.
PowerPoint presenters usually control and manipulate the cognitive actions of the audience - they have a monopoly over the display of information. You should give handouts and let people use their own cognitive style.

The principles of analytical design:

Show comparisons
Show causality, explanation
Show multivariate data
Integration of information - "Never segregate information by its mode of production."
Documentation - give links/credibility. Show people where the information came from. ("This is what 6pt font is for - it should be small but it should be there.")

At the end of the course, Tufte gave a few simple tips for giving a presentation:

You can make the big gains in improving your presentation by getting better content. Improve relevance and integrity of content.
Rehearsal improves performance. Rehearse to a friend or watch a video of your performance.
Show up early to your own presentation.
In your introduction, never apologize.
Finish early. People will be delighted.

Tufte stresses that humans can process much more information than is usually presented to them. All of his methods for presenting data strive to increase the "information throughput." Tufte also said, "No matter how beautiful your interface is, it would be better if there were less of it." We should be trying to maximize the time that the audience spends reasoning with content, and minimizing the time they spend figuring out the design.

I'm really looking forward to reading Tufte's four books now that I've seen him speak. He was engaging and had a lot of great points, and I would recommend going to see him if he comes to a place near you.

P.S. Matt's notes are also online, in all their handwritten glory.

Books, Books, and More Books

2008-07-30T14:53:00Z

I've recently gotten back into reading, and have been trying to read at least a little bit every day. I always feel a sense of accomplishment after I finish a book, since I get so much more out of them than most other things these days. I really enjoy books based on true stories, inspirational books, and sometimes technical books. I mostly read books that have been recommended to me, so I thought I'd post my reading list here for you all to peruse. If you have any recommendations, please leave a comment!

Recently Read

Mere Christianity by C.S. Lewis
Into the Wild by Jon Krakauer
Escape by Carolyn Jessop

Currently Reading

The Art of Possibility by Rosamund Stone Zander and Ben Zander
Implementation Patterns by Kent Beck

In the Queue

The Art of Happiness by the Dalai Lama
The Screwtape Letters by C.S. Lewis
The Culture Code by Clotaire Rapaille
The Exceptional Presenter by Timothy J. Koegel

What are you reading?

RailsConf '08 Recap

2008-06-03T15:31:00Z

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 2008, Here I Come

2008-05-29T03:26:00Z

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!

Bowl for Kids Sake 2008

2008-05-06T02:16:00Z

At the beginning of the year, the Integrum team compiled a list of company goals for 2008. One of our goals was to participate in a charity event in order to give back to the community. On June 7th, the Integrum team will be participating in Big Brothers Big Sisters annual Bowl for Kids Sake event.

If you'd like to help us reach our goal, please visit my page or our team page to donate online. Every little bit counts, and we really appreciate your support!

Mid-twenties

2008-04-26T23:47:00Z

Last week I celebrated my twenty-fourth birthday, and my crossover into my 'mid-twenties.' Ahhhh I'm such an old fart! :) It got me to thinking about whether or not I'm happy with what I've done in the last 24 years, and I must say that overall, I'm pretty proud of myself.

I wanted to say thanks to everyone who celebrated my birthday with me and made it amazing. I must say I felt more appreciated than I have in a long time. The day was full of lovely birthday treats, just look at this stuff!!

Thanks to Heidmo&Aeree, Gist, Dan, Mom, Steph and Jenna for all the goodies, and everyone else for all the birthday wishes!!

Here's to the 25th year!

CSS Naked Day '08

2008-04-09T15:06:00Z

I’ve removed my stylesheet today to participate in CSS Naked Day. Here is the official description of this event:

The idea behind this event is to promote Web Standards. Plain and simple. This includes proper use of (x)html, semantic markup, a good hierarchy structure, and of course, a good ‘ol play on words. It’s time to show off your <body>.

So go get naked, everybody’s doin’ it!

Agile Estimating and Planning

2008-04-07T04:38:00Z

I've been working on reading Agile Estimating and Planning by Mike Cohn, so I figured I would post my notes here as a follow up to my notes on Extreme Programming Explained. The book starts by introducing the purpose of planning, and why traditional methods of planning fail. Right from the beginning (even the title), it stresses that the estimating and planning process itself must be agile. Planning should reveal what should be done and when, and estimating should reveal how big a project really is.

The Purpose of Planning

Planning is an attempt to answer "What should we build?" through consideration of features, resources, and schedules.
Planning supports better decision-making, establishes trust, and helps set appropriate expectations.
"The most critical risk facing most projects is the risk of developing the wrong product." - Planning can help reduce the risk of uncertainty and take the guess-work out of developing without a plan.
"The knowledge and insight we gain from planning persists log after one plan is torn up and a revised one put in it's place." - We should be eager to change the plan; it means that we have either learned something or have come up with a better idea.
Don't try to plan an entire project at the beginning. Agile planning should be spread evenly across the project's duration.

The reason I picked up this book was to read about release and iteration planning, so those are the parts I will highlight here. I have never personally be involved in a release planning meeting, and we talk a lot at Integrum about how we need to be better about release planning. We've also tested out a handful of iteration planning techniques, so I was really interested in what this book had to say.

Release Planning

Release planning produces a high-level plan that involves about 3-6 months worth of work. It helps the product owner and the team decide how long it will be before they have a releasable product. It sets expectations about the time-frame for a project - what will be done, and when? The author says, "without the concept of a release, teams move endlessly from one iteration to the next." I can attest, it is disheartening to developers to work and work without a release in sight. The steps of release planning are as follows:

Determine criteria that will make the project a success or failure. (Based on the company's goals)
Estimate the user stories.
Choose the length of your iterations.
Estimate velocity. (Planning Poker)
Have the product owner prioritize the user stories according to what is most valuable to the success of the product.
Select stories to be completed for the current release and set a date.
Revisit the release plan after every iteration.

Iteration Planning

Iteration planning provides a short-term, detailed view of the work for one iteration within a project's release. It helps lead the team into a discussion about product design and set expectations for the customer about what features will be completed in the current iteration. The result of an iteration planning session should be a spreadsheet or index cards stating the stories, as well as tasks that go with each story. The book outlines two types of iteration planning; Velocity-driven and Commitment-driven.

Velocity-driven planning involves determining the target velocity based on an average of past iterations, then choosing the top prioritized stories that will fit within that velocity.

Commitment-driven planning involves choosing the top prioritized story from the backlog, writing tasks for that story, and then asking the team if they can commit to delivering that entire story in the current iteration. This process is repeated until the team can no longer add stories to the iteration.

The team at Integrum has tried both these methods of iteration planning. We recently switched back to velocity-driven planning, since the general feeling was that commitment-driven planning created too much overhead. Mike Cohn recommends commitment-driven planning because he feels it is more accurate than relying on story points and "yesterday's weather." What do you think?

Tips for Iteration Planning

Don't allocate tasks to certain pairs/individuals during iteration planning. It takes away from the "all in it together" attitude.
Organize stories and tasks so it is easy to tell what task goes with what story.
Don't get too far into a discussion about design. All you need at the time of iteration planning is guesses about the work to be completed.

These are just the highlights I took from Agile Estimating and Planning by Mike Cohn. For more information, go read it yourself! Please comment with thoughts or experiences on release/iteration planning. Thanks!

My Six-word Memoir

2008-03-25T03:07:00Z

I mentioned before that I was still working on my six-word memoir. It's really hard to convey your life in only six words. After much thought, I came up with something that I think suits me pretty well. I can't explain it, because then it would be a 100-word memoir, so use your imagination. :)

"Well that was fun. What now?"

What's yours?

My first SXSW

2008-03-20T14:40:00Z

Last week I had the privilege of attending my first SXSW. Overall I'd say it was a good experience, though I wish I was more of an go-chat-it-up-with-anyone kinda girl. I tend to stick with the people I know, and SXSW is definitely a place I'd have liked to branch out.

Unfortunately, due to a family matter I had to attend to in CT, I didn't arrive in Austin until Sunday, and the rest of the team was already in the SXSW groove. I quickly dropped my bags at the Integrum house and hustled over to the convention center. I was there just in time to pick up my badge and grab a seat in the 3:30pm session. I made it to two sessions on Sunday, and here's my synopsis of them.

Tools for Enchantment: 20 Ways to Woo Users, by Kathy Sierra

There are several other people who have posted notes on this talk, so I won't be too redundant. I think she made a lot of good points, but in general, the gist was that you should not be worried about whether or not you kick ass. You should be worried about how to make your users feel like they kick ass. It makes almost too much sense; if your app makes people feel like rock stars, they are sure to keep coming back.

LOLWUT? Why Do I Keep Coming Back to This Website?, by Ben Huh and Eric Nakagawa

There isn't too much to say about this session other than that these guys are hilarious. When Eric Nakagawa leaned into the microphone to begin the session and said, "Oh Hai," I knew it was going to be good. They basically just summed up their journey since the beginning of icanhascheezeburger. I was dissappointed, however, that I didn't get my hands on one of the cheeseburgers they provided for the audience. Shucks. kthxbye.

Sunday night I went geekbowling with some integremlins, and then hit the hay so I could squeeze in a full day of sessions on Monday.

The Art of Self-Branding, by Lea Alcantara

I was expecting to get a little more out of this session. Lea Alcantara used two companies as examples for a talk about self-branding. Then when asked for examples of individuals who have branded themselves well, she said, "Madonna." With no disrespect to The Immaculate Collection, I thought this was an irrelevant answer considering the audience. She did give some useful information though, including her 5 aspects of a successful brand:

Relevance: Do you make sense?
Creative Design: Does your look match?
Message Communication: Do you talk the talk?
Understanding Customer: Do you know who you're talking to?
Consistency: Can we expect the same quality in everything you say/touch/do?

She also said, "Talent is not enough, perception is almost everything." Which I wish weren't true, but I totally agree with.

I don't have much to say about the rest of the sessions I went to on Monday, except that I am still trying to write my six-word memoir. Maybe I'll post it here when I come up with it. :)

Monday night I attended the Facebook party with Chris and Matt, but no sign of Zuckerberg. :(

Tuesday morning I skipped out on some sessions to visit the office of Red Fly Studios, since Erica has a friend (Kris) that works there. The office was super nice, and they even let us play around with a game they are working on! Thanks to the guys at Red Fly Studios for giving us a peek into the game industry. After lunch, a couple of sessions were worth mentioning:

Creative Collaboration: Building Web Apps Together, by Paul Hammond, Simon Willison, George Oates, Matt Biddulph, and Dave Shea

I really enjoyed this panel. It was so interesting to hear people (developers and designers) from different types of companies talk about collaboration. What I got out of this panel:

Technical Wife/Design Husband - it should be a partnership.
Decisions should be made together and with reason.
White-boarding sessions, including designers and developers should happen early in a project and often.

Taking Over the World: the Flickr Way, by Simon Batistoni

This was a really interesting talk for me, since I've been working with internationalizing a project for quite some time now. Many of the things Simon learned while internationalizing flickr, we at Integrum have also learned on a client project of ours. It was almost refreshing to hear that someone else has gone through the same pains of internationalizing an app. I won't go through all the details of what to do, but he said his presentation would be posted here. (Not there yet, but hopefully soon.)

And then, after eating dinner and making brief appearance at the Digg party, my SXSW experience came to a close. Overall, I had fun and I learned a few things. Phew! This was longer than I thought it'd be, thanks for sticking it out. Cheers. :)

ooochie.com, now even hotter than my macbook air!

2008-03-16T22:39:00Z

Feast your eyes on the brand spankin' new version of ooochie.com! I'm so so so excited for the new look of my site, I mean, just check out my awesome feed robot! Many many thanks go to Dan Ritzenthaler of Forty Agency for ooochie.com's amazing new look! Let me know what you think. :)

Macbook Air, so hot right now

2008-03-13T20:26:00Z

Yesterday was a very exciting day in my life - When I arrived home from SXSW (which I will get my stuff together and write about very soon), my very own Macbook Air was waiting for me! It is oh-so-pretty and I'm already in love with it. Check out the unwrapping here.

Yay!

Fun Times in San Francisco

2008-02-05T05:29:00Z

Last Thursday, Erica and I headed out to San Francisco to attend the first annual Bay Area Girl Geek Dinner. We ended up having a really great weekend meeting people and listening to panelists at the dinner, as well as visiting with the team at Pivotal Labs the following day.

According to the Women 2.0 post (who sponsored the Girl Geek Dinner) over 600 people showed up at Google's Mountain View campus to network and listen to the panelists (Yes, Google really does have heated toilet seats!). I think its wonderful that so many attended, Phoenix would surely have a much smaller turnout. The topic of the evening was "building credibility and reputation in technology and business." While I really enjoyed listening to the panelists, it wasn't quite what I was expecting. I thought there would be more specific advice about how to promote yourself as a woman in the tech world, and I found most of the advice pretty general (i.e. Believe in yourself, don't let people tell you you don't belong in tech, don't be afraid to disagree, etc.). Aside from that, I found the event truly inspirational. All four women on the panel -- Leah Culver (Co-Founder and Lead Developer, Pownce), Sumaya Kazi (Entrepreneur and Social Media Manager, Sun Microsystems), Irene Au (Director of User Experience, Google), and Rashmi Sinha (CEO, SlideShare) -- have done very well for themselves, and it was great to hear them talk about the steps they've taken to get where they are. Some of the things I took away were the following:

Contribute to open source projects. (Leah Culver)
Write articles that show your personality.(Sumaya Kazi)
Don't forget to network. (Irene Au)
You have to have a thick skin. Decide what parts of yourself you want to put out there, try not to post personal things. (Rashmi Sinha)

In addition to the panel, the Girl Geek Event was really about networking. Erica and I had the chance privilege of meeting Arena Reed, a designer at Pivotal Labs. Integrum and Pivotal are both agile shops, so it was interesting to chat with Arena about process - something we've been talking about a lot lately at Integrum. Arena was nice enough to invite us to the Pivotal office Friday morning to see how they operate and talk with some of the other employees. It was very reassuring to see a shop working so well with agile, and I'm optimistic that Integrum will find what works best for us soon enough. Thanks everyone at Pivotal for being so welcoming!

It turned out to be a great couple of days in San Francisco, thanks again to Angie Chang of Women 2.0 and Pivotal Labs for making it an enjoyable and productive trip!

Skydiving!

2008-01-29T14:56:00Z

A great rails guru once told me, "If you didn't blog it, it didn't happen." So I figured I better blog about this one... I went skydiving! It was awesome and I would recommend it to anyone who hasn't been. Here is part of the video they took of me jumping out an airplane at 13000ft!

Girl Geeks

2008-01-22T02:17:00Z

Just an FYI, the Integrum girls (myself and Erica) will be attending the first Bay Area Girl Geek Dinner on January 31. I think it will be a great opportunity to meet people and hear some interesting speakers. (I'm also pretty excited to see the Google Campus in Mountain View!) Unfortunately, registration is already closed, but if you're attending find us and say hello! When we get back I'll be sure to post my thoughts/notes on the event. Hope to see you there!

Happy Anniversary to me

2007-12-04T14:54:00Z

I can't really believe I'm saying this, but as of today I have been working at Integrum for one whole year. It's true what they say you know, time really does fly when you're having fun! Last year around this time, I was starting to have serious doubts about my choice of degree, thinking that I might not ever find a job in my field that did not involve a cubicle or a serious lack of human interaction. But then, a craigslist ad and an interview later, I was starting my first day at Integrum.

I had some serious anxiety about going in there that day. But now, a year later, I can say it was one of the best decisions I've ever made. I have had the opportunity to work with and learn from some extremely talented people, and have had tons of fun doing it.

So anyway, a big thanks to the Integrum gang for just being awesome. :)

Facebook Developer's Garage - Phoenix

2007-11-15T17:55:00Z

Last night I attended the Facebook Developer's Garage at the Tempe Center for the Arts. I was surprised at the turnout, but disappointed to see that only a fraction of those in attendance were developers. I got to hear Dave Morin from Facebook speak about "harnessing the power of the social graph" by using the Facebook platform. Erica took some good notes, which she has already posted on her blog.

Back in July I launched my first Facebook app, which provides users with a profile box that displays their myspace photo and links their friends to their myspace profile, and I'm proud to say it has over 2700 users! (You can install my app here.) Curtis, Matt, and I are currently working on another application for Facebook that we hope to unveil sometime in the very near future. Stay tuned!

Extreme Programming: Part 3

2007-10-27T01:36:00Z

OK my dear readers, I give you the final part of my series on Extreme Programming. Thanks for being patient (except - cough - Gist - coughcough) while I finished reading!

Parts 1 and 2 discussed the values and principles of XP. Now we are ready to talk about the practices: specific ways to apply XP to your software development. The author says the following about the practices:

"The practices in this chapter aren't the whole story of XP. They provide a foundation of respect, communication, and feedback that fosters simplicity and courage. The team members can use their increasing confidence and competence to build relationships inside and outside the team."

Without further ado, the primary practices of XP are:

Sit Together

Develop in an open space.
Communicate with all your senses.
Physical proximity enhances communication.

Whole Team

People need a sense of belonging to the team.
Large teams lose trust, and trust is necessary for collaboration, so try to keep teams small.

Informative Workspace

An outsider should be able to tell how the project is going within 15 seconds of being exposed to the workspace.
Water and snacks provide comfort in the workspace and encourage positive interactions.
Cleanliness and order of the workspace clears minds and helps people focus.
Use big, visible charts.

Energized Work

Work only as long as you are productive.
"Software development is a game if insight, and insight comes to the prepared, rested, relaxed mind."
If you're sick, rest!

Pair Programming

Pair programming is two people working at one machine.
"Pair programming is a dialog between two people simultaneously programming and trying to program better."
Allows people to keep each other on task, clarify ideas, and hold each other accountable to other practices.
Rotate pairs frequently. Switch pairs at natural breaks in development.
Personal space must be respected!
Pay attention to hygiene and health.
Avoid relationships within the team.

Stories

As soon as a story is written, try to estimate the necessary development effort.
Early estimation gives business people and tech people the chance to interact and create value.
Estimating early gets everyone thinking early.
Put stories on index cards on the wall.
"You can't make a good decision based on image alone." - Providing estimates allows customer to make an informed decision.

Weekly Cycle

Plan work a week at a time.
Have a weekly meeting to review progress, have the customer pick a weeks worth of stories to implement, and task out stories.
Goal: deployable software at the end of the week.
Work on gradually reducing planning time.

Quarterly Cycle

Plan work a quarter at a time.
Have a weekly meeting once per quarter to reflect on progress, plan themes, identify bottlenecks, and pick a quarter's worth of stories to implement.
Focus on the big picture: Talking about "themes" as opposed to stories helps people see how the details of what they are doing fit into the bigger picture.

Slack

Always include some minor tasks that can be dropped if you get behind.
Meeting your commitments is important in building relationships.
"Clear, honest communication relieves tension and improves credibility.

Ten-Minute Build

Automatically build the whole system and run all tests in ten minutes.
"A build that takes longer than ten minutes will be used much less often, missing the opportunity for feedback."
An automated build can be a stress-reliever at crunch-time.

Continuous Integration

Integrate changes every couple of hours.
Pairs should integrate(build and run tests) after every pairing session.
"Continuous integration should be complete enough that the eventual first deployment of the system is no big deal."

Test-First Programming

Write a failing test before changing any code.
Helps avoid writing unnecessary code.
Tests should be easy to write. If they aren't, you may have a design problem.
Passing tests let your teammates trust that you've written working code.
Get into a coding rhythm: Test, code, refactor. Test, code, refactor. etc.

Incremental Design

"Strive to make the design of the system an excellent fit for the needs of the system that day."
Eliminates duplication.
XP teams are confident in their ability to adapt the design, which allows them to satisfy the human need for immediate success and economic need to put off investment.
"The most effective time to design is in the light of experience."

There you have it, a brief (and hopefully helpful) overview of the values, principles, and practices of Extreme Programming. As I mentioned in Part 1, I am glad to have found a work environment that follows XP. It creates a feeling of community and a productive working environment. For more info, go read the book yourself! Enjoy. :)

Extreme Programming: Part 2

2007-10-10T19:47:00Z

Now that we've gone over the values that drive XP (Part 1), we're ready to talk about the principles that guide XP. Beck defines principles as "a set of domain-specific guidelines for finding practices in harmony with XP's values." We need principles because they act as a bridge over the gap between values and practices. "Values don't provide concrete advice about what to do in software development." Principles help make it easier to derive practices from the values outlined in part 1. The principles that guide XP are the following:

Humanity

People need basic safety, a sense of accomplishment and belonging to a group, the opportunity to grow, and the opportunity to understand and be understood.
People need free time. Time away from work allows for more energy to bring back to the team.
Private life details confuse team communication. Keep private matters private.

Economics

Make sure what you are doing has business value and serves business needs.
Earn money sooner and spend money later.
Try to enhance "option value": options for future use of your product.

Mutual Benefit

Every activity should benefit all people involved. If it costs one person, relationships will begin to break down.
Automated tests help you write better code now and act as documentation for future programmers, therefore benefiting all parties.

Self Similarity

Try copying a good solution into a different context.
Write a test that fails, then make it work.

Improvement

"Perfect" is a verb, not an adjective!
XP is excellence in software development through improvement.
Do the best that you can now with the intention of doing it better tomorrow.

Diversity

Teams where everyone is alike are not effective: a variety of skills and perspectives is necessary for success.
Diversity leads to 'conflict' (i.e. more than one solution). All ideas should be valued and respected.

Reflection

Think about how and why you are working.
Learn from your mistakes and the mistakes of your team members.
Reflection comes after action.

Flow

Deliver a steady flow of valuble software.
Deploy small increments of value frequently.

Opportunity

See problems as an opportunity for change!

Redundancy

Difficult problems should be solved in several ways in order to prevent disaster. (i.e. Defects are addressed in XP by continuous integration, pair programming, customer involvement, etc. All these things are done to solve the same problem: bugs.)

Failure

"Failure is not a waste if it imparts knowledge."
When you don't know what to do, try something. Risk failure.

Quality

Increases in quality lead to increases in productivity and effectiveness.
People need to do work that they are proud of.

Baby Steps

Momentous change all at once is dangerous.
Take many small steps rapidly.(i.e. Test driven development, continuous integration.)

Accepted Responsibility

Responsibility cannot be assigned, you have to accept it.
If you are responsible for implementing story, you are also responsible for designing and testing that story.

As Beck puts it, "The principles give you a better idea of what the practice is intended to accomplish." Now that you understand the principles, you already know the goals of XP. The practices, which I will outline in part 3, are the things you can do to accomplish these goals.

Part 3 coming soon!

Extreme Programming: Part 1

2007-10-03T15:45:00Z

Even programmers can be whole people in the real world. XP is an opportunity to test yourself, to be yourself, to realize that maybe you've been fine all along and just hanging with the wrong crowd.

This quote comes from the Note to Programmers at the beginning of Extreme Programming Explained, by Kent Beck and Cynthia Andres. I consider myself very lucky to have found a workplace that follows XP. While I was in school I didn't know what I wanted to do with my degree because the stereotypical lonely programming life did not appeal to me. Had I known there was such a thing as XP, I would have been much more optimistic about pursuing a career as a programmer. I've recently been reading through Extreme Programming Explained and have taken notes in an attempt to absorb as much of it as possible. I thought I would post them here for those who haven't gotten the chance to read it. Here's a very brief overview of the overview. :)

What is XP?

Giving up old habits for new ones that work.
Appreciating yourself for total effort today.
Striving to do better tomorrow.
Evaluating yourself through contributions to team goals.
Getting your needs met through software development.

Paradigm for XP

"Stay aware. Adapt. Change."
"Make frequent, small corrections."
"You don't have to wait a long time to find out if you were going the wrong way."

After the basic overview of XP, the author gets into talking about values, principles, and practices. For now, I will only cover values, which are the first to be explained.

We all have personal values that shape our everyday lives; they are the roots of the things we like and dislike, and are "the large-scale criteria we use to judge what we see, think, and do." XP incorporates five core values that that focus on what is important to the team. They are outlined below.

Communication

Helps solve problems.
Motion without communication is not progress.
Creates a sense of team and cooperation.

Simplicity

Ask yourself, "What is the simplest thing that will work?"
Eliminate wasted complexity.

Feedback

Change is inevitable, and change creates the need for feedback.
Be satisfied with improvement rather than expecting instant perfection.
Shorten the feedback loop; it will allow you to adapt sooner.

Courage

Definition: Effective action in the face of fear.
If you know what the problem is, do something! If you don't know, ask!
Doing something without regard for consequence is not effective teamwork.
We must have the courage to adhere to the other values.

Respect

XP won't work if the team members don't care about the project and each other.
Everyone is important!

Next stop: principles that guide XP and practices to use in order to live XP. Stay tuned.

O'Reilly's Women in Tech

2007-09-18T03:56:00Z

Ahh, everyone's favorite topic: Women in Technology. O'reilly has recently been putting out essays on this subject, and I found them to be a decent read. Frankly, I'm a little sick of hearing/talking about women in tech, but I'll give you the run down of my thoughts since it seems to be such a popular issue.

So the conclusion I've reached for myself is that it's time to quit analyzing the situation to death and to just get moving and start trying different things- sort of an open-ended experiment. My first goal is to be more visible, so I can set an example and inspire someone else, just as Mrs. Roberts did for me.from Inspiration: Pass It On by Gabrielle Roth

Good point. I totally agree that this has become an over-analyzed issue. Let's stop talking about it and do something! Women currently involved in technology can use their own experiences to encourage the younger generations by becoming role models.

We need to change the geek stereotype and start showcasing that geek girls are the hip and cool people in society.from Be a Part of Influencing the Future by Nelly Yusupova

Is she serious? Certainly the issue does not revolve around whether or not being a geek is "hip" or "cool." Sure, I'm all for educating young women about the tech field, but let's stay away from labels like these. Show them all they can do with a degree in computer science and get them interested that way. I don't think making it a popularity contest is going to get us anywhere.

I truly believe that personal responsibility is one of the biggest goals towards which we should all strive. I believe that you only really grow up when you voluntarily take full responsibility for your own actions and outcomes, good and bad- and kvetching about women in technology is the antithesis of personal responsibility. No matter how you slice it, the arguments of something must be done; help must be given; someone must change!; or women fail because of something men do all feature the underlying assumption that someone else has power over you or insert-allegedly-marginalized- group-here. After all, a person must have power over you to grant you special treatment or quash your efforts.from I Don't Like Articles about Women in Technology by Amy Hoy

Amy makes a great point. Yet while I agree that taking personal responsibility is truly something to strive for, I think she's going a little overboard. Sometimes there really are factors that we cannot personally control. I can't control it if I attend a job interview don't get hired because some prick doesn't think women belong in tech. Sure, I can fight the urge to complain and get on with my life, but the fact is, that situation is beyond my control. There are clear barriers women face, yet I agree that we should re-evaluate where we place our efforts. (i.e. A little less talk and a lot more action.)

So far the essays have been a good read, and I believe there are more coming. Some were more interesting than others, but I always like to hear what other people have to say. These are just some quotes jumped out at me as I read through. Let me know what you think, too.

The Way I See It #280

2007-09-05T05:31:00Z

I find it ironic that the best advice I've received lately came from the side of a starbucks cup. As I was thoroughly enjoying my cinnamon dolce latte this morning, I absentmindedly skimmed the "The Way I See It" on the side of the cup. It seemed mildly interesting so I read it again and was surprised at how much sense it made. This is what it said:

"You can learn a lot more from listening than you can from talking. Find someone with whom you don't agree in the slightest and ask them to explain themselves at length. Then take a seat, shut your mouth, and don't argue back. It's physically impossible to listen with your mouth open."
-- John Moe

I think we would all be a little better off if we could make an effort to listen to others. Too often we pass judgment too early in a conversation or butt in before the other person is finished speaking. It's time we all learned to recognize when to talk and when to shut up and listen. Ahhh if only it were that easy!

Flickr

2007-08-13T01:43:00Z

Check me out with my shiny new flickr badge!(see sidebar) I created a flickr account to see what all the fuss was about, and while playing around with it I succeeded in uploading some fantastically random photos. I will continue to poke around and upload some fun pictures, so enjoy!

Nerd alert!

2007-07-27T05:58:00Z

Well, my friends, I have officially graduated to a new level of nerdiness (or so I've been told).... I wrote a facebook application! It may not be pretty, complex, or anywhere near perfect-- but I wrote it all myself, and I already have 164 users since submitting it last night!

It's a simple app that, when given the user's myspace url, steals the photo off the myspace page and places it in the user's facebook profile. The picture serves as a link to the user's myspace page.

So, nerd-factor aside, I think it's pretty darn cool. If you have a facebook and a myspace account, go check out my fantastic application. You can find it at http://apps.facebook.com/myspace_fb.

Maybe if I feel ambitious I will post about developing a facebook app, but for now I will just link you to those who have already done so. Liverail has a nice tutorial that helped me out a bunch, and the follow-up is here.

Happy Facebooking!

Best Rake Task Ever

2007-07-16T13:15:00Z

Courtesy of Jade. :)

Just for the sake of writing...

2007-07-13T05:31:00Z

As Matt Gist so kindly reminded me yesterday, it's time for a new post. And since I have no interesting work-related stuff to write about at the moment, I'm going to give a little rant on life in general. Disclaimer: The following are things that are currently frustrating me and are extremely random. They really have nothing to do with anything.

Rant #1: Harry Potter and the Order of the Phoenix Movie was not cool.
I am a huge Harry Potter fan(I don't care if you think it's nerdy!), and I know that a movie will never live up to the fantasticness (yes, I just made up a new word) of the books. That said: what were they thinking? I got all excited for the movie and was very disappointed in the final product. It was jumpy, inaccurate, inconsistent with the previous movies, and was probably confusing for anyone who hadn't read the book. It had such potential. What a let-down.

Rant #2: Migraine Headaches are stupid.
I have been a migraine sufferer since I was 18 months old, so it goes without saying that I am sick of them by now. When I was a kid, they blamed the headaches on a problem with my jaw called TMJ. After lots of dental work, I seemed to grow out of the headaches and went several years without a single migraine. But two years ago, I started to get them again sporadically and now they occur all too often. Migraines have started to interfere with my life again, and I'm not going down without a fight.

Rant #3: Arizona is a very hot state.
Actually, this is less of a rant the the previous two. It's true, Arizona is flippin' hot, but I think I'm adjusting quite well. Air conditioning is amazing, and I really appreciate the 12% humidity as opposed to 81% back home in CT. That said, I wouldn't mind if we turned down the heat a little... 95 sounds ok with me.

Like I said, this has nothing to do with anything, so feel free to ignore it completely. Actually, I'm surprised you're still reading. Cheers. :)

Thoughts

2007-06-15T14:10:00Z

A very interesting article was posted a few days ago on the devChix website about women in tech communities. I think it is a worthwhile read for anyone in a tech environment, male or female. Here is the direct link to the article, so go read it before you continue on to my thoughts.

Gloria makes some great points in this article, but I think that her points are somewhat clouded by her tone. I can see how male readers may feel attacked because the article is so one-sided and focuses on what men are doing wrong and how to accommodate women in tech communities, rather than how we can all work together to make everyone feel welcomed.

I am very new to the professional tech world, so I do not have as much experience with the online communities that Gloria talks so much about in the article. She has given a great description of patterns she has noticed in women-only and mixed-gender communities. Most of the problems she describes come down to a difference in how men and women communicate amongst themselves and with each other. Of course, this is a problem in all professional environments, not just technical. (Hell, communication between men and women is a problem in everyday life.) Both genders have natural tendencies, and it is difficult to break through the stereotypes. We should all take a moment to think about our natural tendencies and how they affect the people we interact with. Maybe even just taking a moment to think about it will help us move a step in the right direction.

I particularly enjoyed the "For the men who care: Tips for communicating with women in Tech environments, online and Face-to-Face" section of the article. Yet while I agree with almost all of what she said here, the problem is again the tone. I think it makes women sound like we expect tech men to be creeps. In my opinion, the first three points in this section are unspoken laws that need to be brought up every now and then to remind everyone what a professional environment should be like. (And I totally agree with number four, so invite me out for beers!) Yet I also think that this section is incomplete. I don't think all the tips for interacting with women should be about sex and not trying to jump into their pants. I think number five should be this: We all know men and women communicate differently, but that doesn't mean you have to change your whole style to speak to someone of the opposite gender. Just realize that your words can be interpreted differently than you might mean them, so think before you speak. If you think you might offend someone, rephrase. If we all treat each other with a little more respect, we might get somewhere.

In the end, it all boils down to communication and respect. We all need to learn to respectfully communicate with each other as humans, and not specifically as men or women. It is sad to me that there is a section in the article entitled "To make an online community more women-friendly, try these suggestions." Shouldn't we just be trying to make the community more friendly in general?

Thank you to Gloria for a very interesting article. I think it has and will continue to get people thinking and talking about how they can better interact with each other on a regular basis.

Rake

2007-06-14T01:12:00Z

Just recently, I learned how to write my own rake tasks. My co-worker, Matt Heidemann, was nice enough to walk me through it after work one day. Everyone who is reading this probably already knows how to do this, but I figured I'd write about it anyway just for fun. My first rake task was very simple and just used system calls to tar and gzip a folder in my /vendor directory. Here's what I did to write it. (Note: the names of my folders and tasks have been changed to protect the innocent.)

First I created the rake file in my /lib/tasks directory, let's call it mytasks.rake. The first thing I want to do is describe what my rake task is going to do. Do this by adding desc before the task. Next, define the task with task :task_name and a block containing what the task will do.

Wow, that was easy. Now this task can be run by calling rake folder_zip at the command line. Sweet.

A couple things to note:
In order to access your models in a rake task, just add "=> :environment" after the task name; like this:

You can add a namespace block around your tasks if they fit into one category. So then you can call your tasks like this: rake folder:zip, rake folder:someothertask, etc.

So that was pretty darn exciting for me, since rake tasks used to be a such a mystery. There is a nice rake tutorial here that gives a much better explanation than my simple overview.

Runt Tech-Talk

2007-06-01T15:45:00Z

At Integrum, we do "tech-talks" every Tuesday and Thursday. A member of the team gives a short presentation about something technical so as to share his or her knowledge with everyone else. I personally enjoy these talks because it gives me an extra opportunity to learn cool stuff from my oh-so-brilliant co-workers.

This past Tuesday, it was my turn to present during tech-talk time. I never know what to talk about, so when Josh suggested that I talk about Runt, I ran with it. Last week I was introduced Runt while trying to incorporate recurring events into a project. Runt is a gem that implements recurring event patterns as described in a paper by Martin Fowler. It allows you to easily define a temporal expression, which represents a set of dates and/or times that an event will occur.

The basic idea is to define a temporal expression using one or many of Runt's temporal expression classes and then use the include? method to ask the expression if it includes a particular date. In the example below, I created a temporal expression for an event that happens every week on Thursday.

I definitely recommend taking a look at Runt if you need to work with recurring events. Below are the slides from my presentation, and here is the rubyforge site for Runt.

RailsConf favorites

2007-05-30T05:37:00Z

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.

Bar Chit-Chat

2007-05-27T02:22:00Z

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.

RailsConf

2007-05-25T14:27:00Z

So I figure that I might as well jump right into the blogging thing while its hot. Last weekend I had the opportunity to attend RailsConf in Portland, Oregon, with several of the guys from Integrum. (Special thanks to the boss-man, Jade Meskill, for giving me the chance to come along). I'm really glad I went, mostly because it gave me such perspective into the phenomenon that is rails. I was introduced to ruby/rails back in December when I started at Integrum. I had no experience actually using either one, so I jumped right into learning as much as I could as fast as I could. I have really enjoyed working with rails the last 6 months, but I never realized that there was such community and passion behind it. I am proud to be a part of that kind of community. At RailsConf I attended several interesting talks, and I will try and post about some of them when I get the chance to sort through my notes. To get a play-by-play of Integrum's RailsConf Experience, visit Derek's blog.

my first blog!

2007-05-25T02:09:00Z

Well, it finally happened. I gave in and here it is.... my very own blog! I hope to use this space to give the world a small glimpse into my life as a young female ruby on rails developer at Integrum Technologies. I've only been using ruby/rails since December '06, so bear with me as I'm still learning all the ins and outs. I hope to post as often as I can with useful information... and maybe some random thoughts about life. Enjoy! :)