Archive for September, 2009

Presentation for Code Camp ‘09

  • September 29th, 2009
  • Posted in Talks

This year at Code Camp, I will be presenting the topic “When to Build and When to Buy”, which will explore the trade-offs associated with either buying software as a service or building an internal tool to meet your business’ needs.  This is especially important for cash strapped startups that are trying to keep their [ READ MORE ]

Timeline: Mint.com – Spring 2007

2007 began slowly, but started to pick up as the year progressed.  Originally, Aaron Patzer wanted to launch Mint.com before tax time, because he envisioned that at the start of the year users are very keen on making New Years resolutions, especially those that deal with finances, ultimately leading up to tax time.  Although Mint [ READ MORE ]

Timeline: Mint.com – 2006

2006 was a year of firsts for Mint.com aka myMint.com.  It was the year Mint Software Inc. was officially incorporated, it received its seed round of funding, and formed the initial members of the Mint family.  And it was the year I officially joined Mint as “#2″. January 2006 – Aaron starts meeting with people who [ READ MORE ]

Timeline: Mint.com – 2005

I was the second engineer, third employee at Mint.com, and lone femgineer.  Mint.com is  in the midst of being acquired by long time rival Intuit.  This was my first startup, and the past three years have been a very unique and fulfilling experience.  In the following posts I will chronicle the major events in the [ READ MORE ]

A Femgineer’s Adventures in Italia: Part I – Trip Planning

  • September 13th, 2009
  • Posted in Travel

I spent the last two weeks traveling to Italy, and when I got back there was a fervor amongst my friends and co-workers to know more about my trip, see pictures, and even start a travel blog!  I’ve decided to do a series of posts to satisfy every one’s curiosity Over three years ago [ READ MORE ]

The Importance of Readability

When I first started coding I believed it was good enough to get stuff working, and then move on to solving the next problem.  I’d spend a little time designing, but most of my time implementing and testing.  My primary concerns were correctness followed by efficiency.  I didn’t see the point in re-factoring code until [ READ MORE ]