go bold

I’ve been having a ton of fun lately playing with ifttt, a service that lets you easily glue together different web services you use / rely on every day. If you remember Yahoo Pipes (wiki), ifttt is based off the same ideas – but is much easier to approach, think about, and use. There are a couple of other ifttt flow blog posts around, but my favorite blog entries are the ones that show instead of tell – so, here we go:

The favorite use I found for it so far is my Game of Thrones task – I love The Atlantic‘s coverage but really couldn’t care less about their other Entertainment articles, and they don’t have category-specific RSS feeds. This way, I get things delivered straight to my inbox!

And, in the interest of keeping my inbox relevant, I have higher-frequency / immediate-action-required tasks tied to my GTalk, which makes sure that I can react quickly.

(I’ve noticed that more of my tasks are tied around consumption/notification rather than production. The other blog posts I’ve linked to above seem to tend toward duplicating/publishing content elsewhere, which is an interesting difference.)

The site is really nicely designed and is genuinely fun to use. Get on the invite list and start creating – I’m excited to see what other fun uses I find.

Note: Hah, if you look closely, my Rent reminder, the second task from the bottom has never fired. Clearly, the service is still in beta. I still use Resnooze for scheduled email reminders about things, but am looking forward to ifttt stabilizing enough for me to switch!

Today I signed a lease. I signed a lease that I negotiated down (helped in part by the current state of the real estate market), essentially decreasing rent per room in our five-bedroom by $200.

Today I ended a stint with a startup. I ended my time at Aardvark as part of The Mechanical Zoo, and on Tuesday I start my time at Aardvark as part of Google.

And to think I could have been five months into my Master’s thesis, wrapping up the first month of my last semester at MIT.

I laughed out loud to myself today as I was waiting for the bus to take me home from the landlord’s office – I like this life.

Last week at around this time, I had just been told that my four roommates were moving out, and that I either had three weeks to fill four rooms or find a new place for myself. I got the rent down, two roommates stayed (plus the dog and the cat), a friend moved in, and we did the Craigslist dance to fill the last room. So now we’re good, with a little terror, stress, and hopefulness thrown in.

Two months ago at work (plus change), all of us piled into a room like we normally do for our end-of-the-week meeting. We were told that a term sheet had just been signed for us to be acquired by Google. Due diligence was done, HR negotiations occurred, and secrets were held for far too long from far too many people. We start at a different office in three days – and I’ll be bringing my personal little knot of excitement, apprehension, and curiosity.

In looking at life post-college, I was worried it’d be too routine – I thought that without “landmarks” to look forward to (winter break, summer vacation, finals, formals, trips), I might be bored and let time slip by without noticing. Well – now school looks methodical and predictable and the extraordinarily safe option.

What have I learned? That question will, hopefully, be answered thoroughly in the future in frequent intervals, but for now, a brief summary of my favorite learnings of the last several months:

• How to fix a flat on a bicycle (and a little about how the bicycle works to begin with)
• How to pick a health insurance plan to fit my needs
• What an acquisition looks like from the inside, and how many things could go wrong without a strong negotiator on your side
• French men are the most amusing members of a tech startup
• Socializing and quality alone time are most beneficial in a carefully maintained balance
• I still don’t take enough advantage of the opportunities around me! (Talks, meetups, people)
• Everything usually works out in the end

But I know I continue to be extraordinarily lucky. So I’m extraordinarily thankful – and am excited to see what else is in store!

I saw this line recently in the middle of a job posting, and I had a strong reaction – two, actually, in opposite directions. First, one of amusement and being mildly taken aback. Sure, they’re honest, but that’s a bit of an aggressive and unrealistic requirement, isn’t it? I almost wanted to scoff, ‘Who are you to demand to rearrange my priorities?’

But of course, the other side had its say as well – why, after all, shouldn’t these founders (who were looking for their third) hold any new teammates to standards as high as those that they themselves adhere? At least they list their expectations out for everyone to see, and hopefully avoid problems further down the road.

I’m torn – what is the right way to handle your pet project? I came into this summer wanting a ‘real startup experience,’ one with late nights and young techies bonding over their mutual misery labor. I complained about most people in my office heading home by 7, despite the smaller and otherwise generally ‘startup-y’ feel. But then, faced with an opportunity to interview with a company that would expect more of me – expect me to make it the primary (only) focus in my life. And I don’t know, after all, if that’s what I want anymore.

I do want to care a lot about my work, be heavily emotionally and professionally invested in my product, and I wouldn’t mind it if everyone stuck around until 9 or 10 most nights… but I also appreciate having good friends outside of the company, and coming home to a roommate who cares more about my personal and emotional health than necessarily the health of my professional career.

In any case, I think this is going to be something I’ll be revisiting over and over again in the coming years, and something that will be heavily dependent on my professional focus. We’ll see what happens… and I’ll leave with a quote from a serial entrepreneur’s thoughts* on “Rules for Web Startups”:

#10: Be Balanced

What is a startup without bleary-eyed, junk-food-fueled, balls-to-the-wall days and sleepless, caffeine-fueled, relationship-stressing nights? Answer?: A lot more enjoyable place to work. Yes, high levels of commitment are crucial. And yes, crunch times come and sometimes require an inordinate, painful, apologies-to-the-SO amount of work. But it can’t be all the time. Nature requires balance for health—as do the bodies and minds who work for you and, without which, your company will be worthless. There is no better way to maintain balance and lower your stress that I’ve found than David Allen’s GTD process. Learn it. Live it. Make it a part of your company, and you’ll have a secret weapon.

* I actually hate the term ‘serial entrepreneur.’ But I suppose Evan Williams has done pretty damn well for himself, and while I want to resent him for trashing this style of working, some part of me supposes he can’t be entirely wrong about everything.

I’ve been trying to be on my own case this summer. Last summer I was in San Francisco, I was very comfortable – I took the last shuttle home (at 7pm!) every day, couldn’t do work at home (no VPN access for interns!), so did a lot of relaxing, watching Alias, and cooking.

I’d had the goal of going out and “doing the SF tech thing,” which to me at the time meant going to tech meetups and talks and meeting all sorts of cool people, and learning all sorts of cool things. Clearly, it didn’t happen.

So this year I’m trying something different. I’ve been much more proactive about getting out and talking to people – an interesting union of MIT friends in and out of the startup world, acquaintances with interesting backgrounds and experiences, and now and then the occasional stranger whose blog I find fascinating. (I hate the term networking. I prefer “being-enriched-by-the-wisdom-of”.)

While the first category of dinner partners definitely keeps me from feeling like I’m becoming a hermit, it’s the second two categories that are really pushing this summer and myself forward. I walk out of each of these dinners excited about everything I can and want to do, and even more convinced of the importance of constant self-improvement.

So. In the interest of committing myself to a number of things to achieve this goal, here goes the list:

• Blog at least once a week. I’m going to set an alarm on my iCal and commit to posting something interesting I learned, or thought, or accomplished.
• Read 1 ‘improvement’ book for every fun book. I’m in the middle of reading the LOTR series (for the first time!), and once I finish The Two Towers, until I finish a programming- or startup- or productivity-related book, I won’t let myself read Return of the King. Sniff.
• Keep working a few nights a week on my side project (more later) – I feel like I need at least one or two non-school- or work-related projects under my belt before I can respect myself as a hacker. Or, as a lower standard, any sort of programmer.
• Along that line of thought – be more disciplined about said project! Don’t just sit down and start coding. Plan out the project a little more (what do I want it to do? How should it behave?) and use version control / repo management tools as well.

(Side note: am still probably far too awkward to be going around meeting people and making these first impressions. Need to work on that, too – for now, just sadface)

(Last note: tonight’s conversation was described as “covering a lot of ground, both philosophically and academically.” Last week’s was described as “spontaneously deep conversation with strangers.” Good nights, both. :))

I was at the SF MoMA this past weekend – and if you’ve ever been, you’ll (hopefully) know that in their standing collection is a set of art from a number of particularly interesting artists, one of whom (Duchamp) is known best for a work photographed here. This is Fountain:

It’s a urinal. It’s a run-of-the-mill, yes-he-really-did, urinal. Made into art (and thus deserving of a spot inside the MoMA) simply by declaring it as such.

Of course, some amount of reputation was required to pull that off, and some other, more traditionally respectable work had to be done to acquire said reputation, but in the end – he’s able to pull something someone else technically “made,” and enhance it for his own purposes.

In the software world, there are those who seem to find it unthinkable to use off-the-shelf products to help with the engineering process in-house. While this attitude has certainly led to plenty of innovation (thank you for Cassandra, BigTable, etc), these special cases seem to really only be the extreme of the “there’s nothing out there just for us” attitude. And, I suppose, to play devil’s advocate, in their situation, off-the-shelf tools probably aren’t quite right for their incredibly unique case. (Or maybe they just had too many engineers and not enough game-changing projects?)

In any case. One of the things I’m getting used to at Aardvark – and starting to really appreciate the wisdom of – is utilizing existing and established solutions when necessary. We need bug/ticket tracking? There’re tons of solutions out there – done! Better log analysis? Found, installed, done. System and cluster monitoring? Perhaps not entirely ideal, but good enough – done. It lets the team know what we need to know, and gets us free to focus on what we really need to get done – the core product and infrastructure.

I joined a conversation this past weekend with a couple of people just starting to get their startup off the ground, and they were embroiled in a CouchDB vs MySQL debate – are relational databases really outdated, or are document-based databases just overhyped? Which is the better to start with for their startup? My answer – whichever makes your actual job easier. There are lots of cool toys out there, but there’s a careful risk vs. reward tradeoff you have to make – and when you’re focused on startups, can you really afford an awkward risk down the line with your data or architecture?

I suppose this is a long, elaborate rephrasing of “Worse is Better.” Take shortcuts and the quick, easy, established route to change the world, first – then figure out how to make it happen better.

I need a brain recorder. Not a notepad, or a voice-recognizing to-do list, or an iPhone app I can access anywhere, but a straight-up biodevice that hooks up to my brain and, when I realize I’m thinking a semi-coherent and somewhat interesting thought that needs a little more munching on, jots it down somewhere for me.

This summer, I’ve been exposed to more down time than I’ve ever been used to – part of it has been due to the necessary delays that come along with the joys of public transportation, some of it is from the copious amounts of walking I’ve been doing (to the grocery store, to and from work, to BART), and some of it is late at night after I get home. (Digression: that down time I’m not OK with – email me to hang out if you’re free!) And in this down time (actually, often when I should be focusing on other things), little thought bubbles pop up around my head:

I wonder what the weather is like in Boston, and (when it’s cold and windy here in SF) how much I actually appreciate seasons on the East Coast,

I wonder why there are so many people scattering so many elementary grammar and spelling mistakes in their emails (“Lot’s”? Come on.),

I wonder about companies and focus and HR people and women (more blog posts along the way),

I wonder about relationships and priorities and what other people are doing this summer.

So somehow, in my mind and for this blog, I’ve been queuing up quite the list of things to think about and blog about. I haven’t, however, found the impetus or time (because I’m thinking up too many other thoughts? :)) to actually do so. So here’s a promise – there are interesting things to come.

In tech and the startup world, there are tons of options – new startups spring up every day with “the next big thing” – or “the ____ killer,” or “____ for [insert platform here],” or “____ meets ____, AGGREGATED!!”

So when something really cool comes around – it seems to make sense to want to jump on board and share in their (or your expectation of their) success. But when you know little about the actual team you’d be working on, and conventional wisdom seems to put “the people” at the top of the list when considering school / workplaces / environments in general, how do things play out?

I like to think that good people want exciting projects. A good developer wants stimulating work, and once put in an environment with that stimulus taken away (either by a boring project or, for example, being bought out by a company which stifles the exciting parts), they’ll find a new place to play out their cool ideas.

So I think instead of worrying whether product.good > people.good or people.good > product.good… I’ll stick with product.good implies people.good (with the converse unfortunately not always being true, without good management / vision / etc). Here’s to the future.