Monday, 08 March

Better than adblocking [dria.org]

Just jumping on the adblocking yea/nay blogging train: I don’t block ads. I could but I don’t bother. Most of the time they don’t bother me unless I’m trying to read a long article, at which point I use Readability, which is infinitely better than an adblocker for that situation.

Before Readability
before-readability

After Readability
after-readability

Note: Readability runs fine on Minefield if you use Nightly Tester Tools to force-install. There’s also a bookmarklet version if you don’t want to install an add-on.

Friday, 05 March

Candidate Declaration [JOSHMEANS.COM]

March 5, 2010

To:

Ramshaw Real Estate
Cobblefield Point Residents
Brent Anderson

From:

Josh Means

Re:

Candidate Declaration

Residents of Cobblefield Point:

This letter states my intention to run for a position on the Cobblefield Point Homeowners’ Association Board.

During my first year as a member of the Board we helped correct a significant budget shortage. While some decisions were difficult and did not make everyone happy, all decisions was made with the entire Association in mind.  We have attempted to provide Cobblefield Point residents with a unified direction and strong voice.  The budget shortage we corrected has now turned into a small surplus, with continued oversight of expenditures and careful planning of services, I believe we can further increase the capital reserve of our Association. This will better prepare us for the challenges that lay ahead.

As I stated last year, I am proud of the condo I own and I believe we all stand to benefit from having a complex we can enjoy and be proud to call our home.

I hope that each and every resident understand the sense of responsibility they have and will join the Board with helping to make our community a better place.

Thank you,
Josh Means

cc: http://joshmeans.com/?p=315

Tuesday, 02 March

Quote of the Week [storm trippin']

While watching the Olympics this last weekend we tried the impress upon the kids the values of hard work, competition, team spirit, national pride, and the fun of sport.

G, to the kids: ".. And maybe someday maybe mommy and daddy will be at the Olympics watching you guys compete for a gold medal. Which sport do you think you'll play?"

Naveen, matter-of-factly: "whatever's the easiest"

Sigh, still much progress to be made in the "hard work" department...

Saturday, 27 February

Zdir (Tunisian tomato-chili soup) [dria.org]

Read this article in the Atlantic yesterday and decided to give it a try. The article doesn’t give a precise recipe, so I’ve deciphered it the best I can below (making a minor substitution and leaving out the semolina). I just made it. It’s really damned good.

I really have no idea whether this can be properly called “zdir” since I’ve been unable to locate an actual recipe (or any other information) about it. Either way, it’s crazy tasty with a good solid spicy punch. If you don’t care for spicy food, skip the harissa and chilis. If you do like spicy food, you have to try this.

  • 2-3 dried red chilis (I used 2 Sanaam chilis)
  • 1 oz olive oil
  • 3-4 cloves crushed garlic
  • 1 tsp harissa (this is a lot, I might halve this next time…it’s potent stuff)
  • 2 tsp tomato paste
  • 1 tsp ground caraway
  • 1 tsp ground coriander
  • 1 tin diced tomatoes + juice (28fl oz)
  • 1/4 c water
  • 1 tbsp preserved lemon, chopped
  • 1 tbsp capers, chopped
  • 1 tbsp olives, chopped
  • 1 tbsp sundried tomatoes, chopped
  • 1 tsp dried mint (or to taste)
  1. Soak chilis in a bit of water for 15-20 mins. Chop finely.
  2. Pour olive oil into a pot and heat over med-low, when warm add garlic + let steep for 5 mins or so. Don’t saute the garlic…just let it warm through and flavour the oil.
  3. Turn up the heat a bit and add tomato paste, harissa, and a bit of the tomato juice. Whisk together well and simmer for a few mins.
  4. Add chilis, caraway, and coriander to the paste. Simmer another few mins.
  5. Pour in diced tomatoes with their juices and the extra 1/4 cup of water. Add chopped sundried tomatoes, and mix well. Simmer over low/med-low for 20 mins or so. Add more water if needed.
  6. Optionally, if you have an immersion stick blender, use that now to chop up the tomatoes a bit. If you prefer a chunkier soup, or if you don’t have an immersion blender, just skip this part.
  7. Quickly rinse the chopped preserved lemon, capers, and olives (just to get rid of the excess vinegars/etc). Stir these into the soup. Let sit on low to heat through for another 10-15 mins.
  8. Remove from heat, stir in dried mint, serve.

Friday, 26 February

GrowReviewComment [Coop]

This has been a pet peeve of mine for a while. Assuming you’re not editing the attachment as a comment, Bugzilla gives you a very small window in which to leave a comment when reviewing a patch: the textarea is 5 rows high and only 25 columns wide by default. I’ve found it hard to add coherent commentary in a box that small, and my efforts almost always come out poorly formatted because I just can’t tell how the text is wrapping.

I whipped up a dead-simple greasemonkey script today that increases the size of the comment box when you click on it, and then shrinks it back down again when you click elsewhere.

Spinach & mushroom frittata with goat cheese & sundried tomato [dria.org]

Spinach & mushroom frittata with goat cheese sundried tomato
I’m not going to post the recipe for last night’s dinner because it basically amounts to: make an omelette with fewer eggs and more stuff, the end. The sundried tomatoes were disappointingly tasteless, unfortunately. I need to find a new source. Otherwise, yum! Super easy.

Thursday, 25 February

On 1:1s [dria.org]

coffeecups

Photo by chichacha.

One of the most important parts of my week is my one-on-one (1:1) meeting with Dan, my manager. These meetings generally only last around half an hour, and it’s time extraordinarily well spent. In that half hour we catch up, discuss projects and status, review priorities, troubleshoot blockers, checkpoint against our quarterly goals, and use the time to give each other feedback. It might sound like a pretty dense 30 minutes, and that’s because it is. Our 1:1 meeting is a tightly packed conversation that establishes and reinforces my direction, priorities, and motivation. As a remotie*, I would be lost without it.

The actual meeting is only part of the story, however — while the meeting only lasts for half an hour, I do some prep work the day before. This prep work mostly involves reviewing my projects and goals, writing out what I want to talk about, and sending those notes to Dan so he can review them before we meet. I find this process extremely useful.

Over the months I’ve established a more-or-less standard format for my 1:1 prep notes that includes five fairly straightforward sections:

  • Accomplishments & status
  • Blocked/Waiting on
  • To do over the next week
  • Areas to develop
  • Quarterly goal tracking

Accomplishments & status: This is where I do a quick rundown of my current projects, with one or two sentences covering what I’ve managed to get done in the last week and what the current status looks like.

Blocked/Waiting on: This is where I list the projects I’m stuck on and why, or other things that are blocking progress — either waiting on resources, people, feedback, or whatever else. Having this section is absolutely vital — if I’m blocked on something, we can usually talk it through so I get unstuck, or Dan can figure out what he can do to help.

To do over the next week: By writing out a short list of specific things I plan to work on over the next week, Dan and I can make sure that I’m working on the right things and am prioritizing things properly. This doesn’t take a lot of time to go over, and since we checkpoint on this every week there usually aren’t any changes, but sometimes my task list gets rejigged slightly if other things have come up elsewhere in the organization.

Areas to develop: Usually this is a one or two sentence “big picture” sort of thing. Dan and I talk about longer-term career development once every month or two, discussing what I need to do or develop in order to progress, become more effective, and have more impact. In this part of my prep notes I take a few minutes to review how I think I’m doing in relation to what we discussed and jot down what I believe I need to focus on improving the most.

This section gives Dan a chance to do some career development coaching. While we normally deal with this part of the meeting in a matter of minutes, it’s profoundly useful — this is an incredibly quick and easy way for me to get ongoing lightweight feedback from Dan on a regular basis.

Quarterly goal tracking: We establish a set of goals each quarter, and every week Dan and I review progress on the ones I own and am driving. I find this useful because regularly checkpointing against my goals helps me make sure I’m focusing on the right things. By reviewing these weekly, we can also make ongoing course corrections where needed. Life rarely happens exactly according to plan, and priorities and projects can shift. It’s far better to review and adjust things weekly than to do a single review late in the quarter just to realize that things got off track (at which point the panic sets in).

Video chat: Another thing I should mention is that Dan and I have our meetings using Skype video. We used to just use the phone, but Dan talked me into using video chat and it’s really much, much better. As a remotie, being able to get “face time” like this is way more important than I thought — not only is the communication much higher bandwidth, there’s a psychological impact I can’t really explain. I just feel more connected to the rest of the company, which is both surprising and fantastic. If you’re remote, you should really try using video chat for your 1:1 meetings…I can almost guarantee that it’s more useful than you expect.

And that’s about it. Having developed the habit of prepping for my 1:1 meetings this way, it only takes me about 15-20 minutes to write up my notes to send to Dan, and it makes our meetings incredibly focused and useful. If you’re not sure you’re getting the most out of your 1:1s, you might try something like this — a half hour of prep work on your part for a half hour meeting can have a huge impact.

Do you have particularly awesome 1:1 meetings? What makes them awesome? What tips would you give to people who would like their meetings to be more useful?

  • remotie: noun, a person who works in a different geographic location than his/her manager.

Wednesday, 24 February

Soba noodle salad with grilled tofu [dria.org]

Soba noodle salad & grilled tofu

Dinner this evening, sticking with the “meatless” theme, is a very simple soba noodle salad topped with grilled tofu.

Grilled Tofu

  • 2-3 1/2″ slices of extra firm tofu, drained and pressed
  • 1 tbsp light soy sauce
  • 1 tbsp mirin (sweet sake)
  • 1 tbsp rice vinegar
  • Splash sesame oil
  1. Mix soy, mirin, vinegar, and oil in a shallow bowl. Add tofu slices and marinate for 15-30 mins or so. Note: mirin is optional — it adds a notable hint of sweetness which may or may not be wanted. I’ll probably skip it next time.
  2. Heat a ridged grill pan over med-high heat until hot enough to instantly sizzle water. Grill tofu 3-4 mins per side (it will smoke and should develop good grill marks). That’s it.

Soba noodle salad

  • 2 tbsp olive oil
  • Splash sesame oil
  • 1 tsp light soy sauce
  • 1 tsp rice vinegar
  • 1 tsp lemon juice
  • 1/2 tsp grated fresh ginger
  • 2 oz soba noodles (uncooked)
  • 1/3 c frozen edamame (out of pods)
  • 1/4 c thinly sliced carrot
  • Small handful baby spinach
  1. Whisk together olive oil, sesame oil, soy sauce, vinegar, lemon juice, and ginger. This is a simple lemon/ginger vinaigrette.
  2. Cook soba noodles in boiling water for 4 mins. Before draining, add edamame and let cook for another minute or so, then add carrot slices and baby spinach and let stand for 20-30 seconds. Drain well and rinse with cold water until cool. Drain for 4-5 mins.
  3. Put salad in a shallow pasta bowl, top with grilled tofu slices, and pour over vinaigrette.

Very tasty and very filling. This is what I made for one (me) and I couldn’t finish it.

Tuesday, 23 February

Why I love Readability, with screenshots [dria.org]

Readability is a Firefox add-on that improves the experience of reading long articles in your browser by getting all the extraneous cruft out of the way. I use it every single day and love it to bits.

Here, for example, is a screenshot of what a typical Harvard Business Review article looks like in Firefox (Persona: Save the Bees Plz by monorail cat):

Old Crufty
before-readability

With the Readability add-on installed, all I have to do is hit a quick keyboard shortcut (alt-cmd-R) and the page will reload and be reformatted by Readability. It looks like this:

New Clean
after-readability

It’s just so, so much better. arc90, you have made a great thing. Thanks :)

gold medal poker [Talk Without Speaking]

Despite all the amazing activity buzzing around town (oh wait, or is that the sound of helicopters instead?) Suz and I got together with the poker gang and tried to do our part to take the friday night poker championship which has, so far, eluded us. It wasn’t to be however but we all had a great time with Olympic gold being won in front of us, yummy pizza and fun poker.

Took advantage of the intervelometer on the new d300s for some a fun poker video! Enjoy.

Kihei, HI [Life in Kjell]

Dawn around here is loud.

I cheated. I came to Hawaii even though I’m not quite done this thesis. I seriously weighed whether to finish the all-nighter I had started on Sunday and just get something done, but in the end, I think sanity reigned.

I mean, srsly. If I have to spend a day typing on the Lanai, so be it.

So here I sit. Green Lawn. Ocean.

Okay, maybe I’ll go for a snorkel—then thesis.

Monday, 22 February

Vegetable Stew [dria.org]

Sort of made this up as I went. Serves four or so? We have leftovers.

Ingredients

  • 1 tbsp olive oil
  • 2 small onions, diced
  • 3 cloves garlic, minced
  • 1/2 tsp red pepper flakes (optional, but tasty)
  • 1 tsp dried thyme
  • 2 med carrots, sliced into 1/2″ rounds
  • 2 lg stalks celery, sliced
  • 6 small potatoes, quartered
  • 1 md zucchini, sliced
  • 1 c cabbage, sliced
  • 1 19oz tin diced tomatoes, including juice
  • 1/2 c water or vegetable stock
  • 1 14oz tin white kidney beans, drained & rinsed
  • 1 c cooked barley (hulled, not pearled)
  • Salt & pepper to taste

Method

  1. Heat olive oil in a large pot over med-high heat. Add onions, garlic, and red pepper flakes and saute for a couple of minutes. Add carrots, celery, and sliced cabbage, and saute for a few more minutes. Toss in potatoes, saute for a little longer.
  2. Pour in diced tomatoes and juices, and add water. Heat to just boiling, then turn down to med-low and simmer for 30 mins or so (until everything is cooked through).
  3. Add drained and rinsed kidney beans and cooked barley, stir and leave on low for another 10-15 mins to heat everything through.
  4. Salt & pepper to taste. Optionally serve with freshly grated parmagiana cheese (it’s yummy).

Grocery run [dria.org]

Tylenol Cold & Flu meds got me on my feet long enough to get to the grocery store (Rob’s away, else he would have gone). Figured I’d pick up enough food for the better part of 2 weeks. Unsurprisingly, it’s cheaper to eat like this. Froze the bacon we already had on hand, which was hard. Oh bacon, I’m gonna miss you the most.

Here’s a list of what I bought because I’m bored and cranked on cold meds.

Fruit

  • Bananas (7)
  • Clementines (2 lbs)
  • Flat of cubed melons + pineapple (on sale)
  • Blueberries, 1 pint

Fresh vegetables

  • Baby spinach (1 lb)
  • Celery (1 bunch)
  • Carrots (organic, 2lb)
  • Leeks (3)
  • Anise (1)
  • Zucchini (3 small)
  • Ginger
  • Garlic (5)
  • Cabbage (1 large)
  • Butternut squash (1 med)
  • Spaghetti squash (1 med)
  • Potatoes (3 lb, small)
  • Eggplant (1 large)

Dairy (and whatnot)

  • Goat cheese (plain)
  • Feta cheese
  • Butter (cultured, 2lb)
  • Milk (2%)
  • Yogurt (1 ltr, plain, 6% mf)
  • Tofu (extra-firm, 2 blocks)
  • Eggs (2 doz)

Everything else

  • Tortillas (whole grain, flax)
  • Bread (whole grain, flax)
  • Crispy flatbread (honey & flax)
  • President’s Choice “Ancient Grains” cereal (2 boxes)
  • Sundried tomatoes (3oz, dry)
  • White kidney beans (3 tins)
  • Red kidney beans (3 tins)
  • Black beans (3 tins)
  • Chickpeas (3 tins)
  • Vegetable stock (Campbell’s organic, 3 tetrapaks)
  • Short grain organic brown rice (best rice ever)

Already on hand…

  • Basically everything else including onions, sweet potatoes, various rices, barley (hulled & pearl), quinoa, dried beans, a plethora of dried herbs & spices, various oils & vinegars, a somewhat alarming array of hotsauces, a big ol’ chunk of 2 year old cheddar, parmigiana cheese, peanut butter, tahini, olives, dried mushrooms, egg noodles, rice noodles, pasta, tomato soup, etc etc etc.

This is gonna be awesome.

Sunday, 21 February

An experiment in meatlessness [dria.org]

vegetables
Picture by karimian.

I’ve decided that I’m going to try an experiment in going without meat for the next two weeks. I say “without meat” rather than “vegetarian” because there are shades of grey in the world of vegetarianism, and I fully intend to cook with animal products such as eggs, milk, cheese, and butter. Just no beef, pork, fish, chicken, shrimp, etc.

The reason for this is simple. We’ve been working on eating less meat on average for the past couple of years, but we still eat more than we should. To eat less, we need to expand our repertoire of recipes for meatless mains. We have the cookbooks, we just need to use them and try more new things.

Two weeks gives me a chance to try around 10-15 new recipes. More if I get inspired and energetic, but probably not because I’ve got a cold and “inspired” is just about the last thing I feel right now. I’ll probably start with some sort of vegetarian stew or chili and go from there. If I remember, I’ll take pictures and blog it all.

If there are particular meatless recipes you think I should try, leave a comment!

Best music of ‘09 [n3wblog]

Yeah, I’m late, but I might as well type up this list before we’re much further into 2010. It seemed like kind of a dull year for music. I did a lot of back-filling which should make for an even more compelling Best of the Oughts if I can ever get around to writing that. There was a lot of music that I liked in the last ten years.

So, here we have it:

  • Atlas Sound, Logos
  • Bat for Lashes, Two Suns
  • Crocodiles, Summer of Hate
  • Fever Ray
  • Grizzly Bear, Veckatimist
  • Handsome Furs, Face Control
  • Metric, Fantasies
  • The Raveonettes, In and Out of Control
  • Silversun Pickups, Swoon
  • Yeah Yeah Yeahs, It’s Blitz!

I actually had a hard time coming up with 10. If I were being honest, I’d probably drop Metric and Silversun Pickups out of this list. “Fantasies” didn’t have any stand-out killer tracks on it, though it was probably a more consistent album than any of their previous ones. “Swoon” was similar, lacking anything truly earth-shattering, though “The Royal We” and “Panic Switch” are solid tracks.

Notable albums that didn’t make the cut: The xx, xx. That album was pretty over-hyped and gets tired fast. Tegan & Sara’s “Sainthood” (despite a couple of excellent tracks), and the already boring Phoenix’ “Wolfgang Amadeus Phoenix”. If you’re gonna sell your songs to car manufacturers, at least wait a few months for me to get tired of your music first. Still catchy though.

It occurs to me that I’m spending more time talking about the music I liked less than the albums I listed above. If I had to buy just three of them, I’d probably pick Atlas Sound, Bat for Lashes and Grizzly Bear. But I couldn’t buy just three because then I wouldn’t have Handsome Furs’ excellent minimal electro-rocker “Face Control”. And Fever Ray is truly strange and excellent.

Did I miss any? Leave me a note if you think I’m missing out on anything 2009 had to offer. Happy listening.

Currently listening to All We Want, Baby, Is Everything by Handsome Furs from the album Face Control

Saturday, 20 February

Tết in Thailand [storm trippin']

peach blossom
Chúc Mừng Năm Mới to everyone! Happy belated Lunar New Year and may the year of the metal tiger be a happily memorable year for you.

This year we took off to Thailand for the Tet holiday. We decided to try a vacation in Pattaya this year. As a beach vacation goes, it was not as good as our previous beach vacations in Phuket or Bali, but, hey we still had fun. Pattaya's advantage is that it is only a 1.5 hour drive from Bangkok on the toll highway. And if you're an old white man looking for younger Thai women, or older white man looking for younger Thai men, and looking for a party town, then Pattaya is a good place to check out.

We stayed a few days at the Rabbit Resort and a few days at the Birds & Bees resort, both very family-friendly resorts. The Rabbit Resort is a very good value for the money and has a better breakfast than the Birds & Bees in my opinion. The Birds & Bees resort is more expensive than the Rabbit, but overall scored higher than Rabbit for us. The B&B; Resort is entertaining in many ways: the kid's pool has slides & water sprinklers, a vegetable garden and fruit tree farm to explore, Mozart-listening hens laying eggs, rabbits hopping around the grounds, fish to feed, bicycle stations that power water sprinklers & speakers looping through various national anthems, and of course the mannequins plastered in condoms and contraceptive pills. And profits go to support Population and Community Development Association a non-governmental charitable organization.

We did make it away from the beach and pool to take an elephant ride. Here again the Pattaya experience did not measure up to previous elephant rides in Phuket and Luang Prabang. Riding along the fringe of suburbia is not as enjoyable as riding through jungle. And the elephant ride business did not have any displays or briefing on where the elephants came from, or the current state of elephants in Thailand or what the future may hold for the beasts.

A few days in the sun and warmth of Thailand watching the kids enjoy the beach and pool, then back to the relative chill and cloud of Hanoi. We arrived back mid-week and Hanoi was still very much in the quiet of Tet, such a contrast to the pre-Tet chaos and mayhem when everyone shopped, shopped and shopped. We had such a pleasant time walking along the quiet streets, not having to avoid swerving motorbikes or listen to incessant honking or shake our heads as headstrong impatient drivers knotted themselves into another traffic lockup. A few short days of quiet and now the city has returned to its bustle and vigour.

Vacation over.

Tuesday, 16 February

Best Games Ever [pintday.org]

Jamie and David got screwed.

Let me admit, I’m not exactly a huge figure skating fan (far, far from it), but once again, the crowd says “perfect.” The commentators say “perfect,” and the judges say “I liked the fallin’ down Russians instead.”

Call me a worthless idealist, but the Olympic picture I’ve always carried around in my head is one of athletic prowess. Slice the field up into a bunch of events, and whoever is the best in any given one gets a shiny medal. Sure, this depends on somebody’s definition of best, but that can’t be too hard to come up with, can it? We’re talking athleticism. It’s quantitative. First one over the line wins.

Yeah. I’m funny.

The Olympics, of course, have little to do with athletic prowess. Perhaps when everyone still competed naked things were different, but now it’s an entertainment product, just like all the other pro sports that I used to like. (Come to think of it, competing naked is a pretty appealing marketing plan. I’m sure one of the new cable channels will latch onto that one in the near future.)

An entertainment product has to have crowd appeal, and though first one across the line works for me, it’s obviously not enough for his royal-majesty-highness-right-honorable-big-studmuffin IOC Chair, or whatever he’s making people call him these days. Crowd appeal requires judged events, it is said, so judged events we get.

Consider the ski jump, of all things. If ever there was an opportunity for an event to be based on good-old quantitative results, I would have figured the ski jump was it. Ski down hill. Jump off cliff. Measure distance at impact zone. Clean up bloody mess if required.

Of course, it isn’t quantitative. That’s not entertaining enough.

In the K-90, you have style points. The style points, it would seem, are based on comparing your form with the ideal ski jumping form. The ideal form, of course, is the form which—in theory—would cause the ski jumper to jump the farthest. If this was true, then the person with the best style should fly the farthest, and win the event.

But, as I watched the K-90 gold medalist miss the silver medalist’s mark by four metres, the irony began to beat its way into my head. When my grade 10 gym teacher told me that there were no points for second place, he wasn’t being entirely truthful. There are, and they’re called style points.

And when the Russians won the figure skating gold, well, I just had to laugh. Apparently all five people in the world who thought it was a better performance were on that judging panel. Way to go, folks. You’ve brought some real class to the sport.

The only thing funnier is going to be when his-royal-whatchamacallit IOC Chair declares these games, the judging-scandal-wrought, bribe-the-hosting-panel games, the “best games ever.” Best by who’s measure?

I bet it’s the figure skating judges that decide.

Saturday, 13 February

generational [Talk Without Speaking]

Dad, Loch Fyne, Scotland, 1959

Where does something like a lifelong love of photography come from? Perhaps the answer to that question isn’t that hard to uncover. While visiting one of my father’s best friends in Scotland, he gave me scanned copies of many of his pictures from when my father was growing up. The one above was the one that fascinated me the most.

My father sat down with his father and journaled the story of his life and there is a deep sadness that I never got the chance to do the same. And so these little glimpses into Dad’s life are…well…inexplicably valuable.

I have no recollection of my Dad getting the Pentax 35m camera that took so many hundreds of pictures of me while I grew up. When I bought Dad his first, and only, digital camera for his 65th birthday, I genuinely didn’t know how well it would be received. But to say that he loved it is, I think, an understatement. I would walk into his den and he would have digital pics of his paintings opened up in Photoshop, zoomed in to 1600x magnification, marvelling at how the paint colours were blending together.

Me, Espiritu Santo, Mexico, 2009

Fast forward to today. I look down at the seemingly ever growing collection of camera battery chargers on the floor as we ready ourselves to head out for another day of Olympic shooting. I flick through years of photographs with small clicks of my fingers; a glorious bombardment of sights, memories, sounds and emotions. 6 weddings and a funeral. Powerful stuff.

I couldn’t explain to you why the drive to capture life’s moments compels me while others are content to simply move on through. It’s so easy to share our life experiences with each other now…it seems easier by the moment actually.

Ultimately, this is a passion, one that I have inherited from my father it seems. And that brings its own power with it as well. Dad said ’seize the day’ and so we should. Do what you love. Love what you do. Let’s start.

www.feelingphotography.com

Friday, 12 February

links for 2010-02-12 [dria.org]

Kiss the Future goodbye [Coop]

Flaming tire tracksLet it never be said that we don’t listen.

In response to the comments on my previous entry about Tackling the Release Engineering:Future queue and a number of conversations I’ve had out-of-band over the past few months, the release engineering team has decided to do away with the Future component. We will be merging all of the bugs therein back into the regular Release Engineering component.

Aside from the simplicity inherent in having fewer components to worry about, there were three main reasons we chose to do this:

  1. No other group in the company/community has an explicit “Future” component where they can hibernate bugs.
  2. People outside the RelEng team find the Future component opaque, and despite reassurances to the contrary, they often just assume bugs in the Future component won’t be fixed.
  3. Moving bugs between the regular Release Engineering component and the Future component makes it very hard to extract meaningful statistics about how our bugs change over time (new bug rate, fix rate, etc.). This makes it hard to change our processes based on data.

What does this mean for you? Nothing, hopefully. I’m planning to move all the bugs out of the Future component on the morning (EST) of Monday, February 15th. People in North America will be on holiday, so this should be a relatively low-traffic time to make this change. My apologies in advance for the RelEng mail bomb you’ll be getting on Tuesday morning. :/

We will still continue to triage bugs using our three bucket approach, only the location of the third bucket will have changed. Our three buckets of bugs correspond to the following:

  1. Untriaged: – state: NEW, assigned to: nobody, priority: none (–)
  2. Triaged, assigned – state: NEW (we’re not working on it yet) or ASSIGNED (we’re working on it), assigned to: a specific release engineer, priority: P1-3
  3. Triaged, unassigned (was Future) – state: NEW, assigned to: nobody, priority: P3-5

In the interest of further simplification, the RelEng team will eschew the Severity field as we move forward, although we won’t change any information already contained in that field if it exists. Instead, we’ll start using the Priority field more diligently. All bugs that have been triaged will have a Priority associated with them from here on out.

For reference, the various Priority levels mean the following to us:

P1: blocker, all other work on hold until this is fixed
P2: being actively worked on
P3: acknowledged as an issue, but not being actively worked on
P4: (future) goals that are either blocked on other work, or that simply have not been started yet
P5: enhancement

There was some concern within the RelEng team that developers might assume that bugs moved out of the Future component were now being worked on. I have faith that people will correctly interpret the implications of their bug still being assigned to nobody@mozilla.org as an indication that, no, their bug is still on the shelf.

Please note that this does not change the triage work that still needs to happen on these once-and-Future bugs, as described in the previous post. We’ve already made some good headway on triage this week, though. The number of “Future” bugs is now down to 304 from a high of 343. Kudos to the people who made that happen. Let’s keep up that great work.

Thursday, 11 February

links for 2010-02-11 [dria.org]

  • This is really cool. Read the paragraph of explanation below the video for context.

Wednesday, 10 February

links for 2010-02-10 [dria.org]

Non-fic – Greater Than Yourself: The Ultimate Lesson of True Leadership [dria.org]

gtyI stumbled across an article called “Your Greater-Than-Yourself Project” by Steve Farber, and it was interesting enough that I bought the book.

The premise is fairly simple: You can help make the world a better place by finding and mentoring someone who you feel has amazing potential and help make them as successful as possible (ideally, of course, to be “greater than yourself”).


The greatest, most successful and well-respected leaders that I’ve encountered in my two decades of consulting, advising, writing, and speaking are not just helpful: they’ve come to understand that the true measure of their greatness as leaders is their ability to develop leaders who go on to surpass them — who rise to a level greater than themselves in skill, influence and ability.
– Steve Farber

The article outlines six pieces of advice to help you get started, which are expanded upon (in a roundabout way) in the book. It’s a fantastic premise, but I’d be curious to see how it works in action. The book doesn’t really get into a whole lot more detail — it’s written as a parable which makes for a quick read but glosses over the nitty-gritty. Worth reading, either way.

Monday, 08 February

Tackling the Release Engineering:Future queue [Coop]

Bart falls down a well.The Release Engineering:Future bugzilla component alternately inspires feelings of sadness, loathing, and contempt…and that’s just within the RelEng team!

I’m certain most developers first response to having their bug moved to the Future queue is, “Oh, look, my bug has fallen down a well.” Historically speaking, that may not be far from the truth.

What goes in Future?

Great Scott!!Why does the Future component make people get punchy? For a long time, the Future component has lacked a decent description, so developers don’t know what it means when their bugs are moved there. Many have started hording their gigawatts in anticipation.

Bugzilla currently has the following small description of the Release Engineering:Future component:

“For longer term projects that have been agreed should be done, but have no immediate plans to so. These are not be part of the regular recurring triage. Advanced planning and placeholder goals for next quarter also go here.”

Despite the grammatical errors, this description is mostly accurate, but what does it actually mean:

  • Triaged bugs with no immediate owners go here.
  • Sadly, most enhancement bugs end up here unless they will make the core release process better, more streamlined, etc. quickly.
  • Bugs that are blocked on longer term projects in other groups go here until there is something for RelEng to do.
  • Advanced planning and placeholder goals for next quarter (or later) also go here. That’s pretty self-explanatory.

Remember: this description is for the Future component ONLY. The RelEng team continues to pick up and work on bugs that need to get done on a daily basis.

I’m thinking about how to improve this description, and will get the description updated in Bugzilla once I have achieved some rough consensus. In the meantime, I’ve posted this description of the Future component in the wiki as an ongoing reference.

The (Ever-Increasing) Numbers

At the time of writing, the Release Engineering:Future component has 343 bugs in it. This number has grown steadily over the past year despite having more release engineers on staff, and having made a great many improvements to our release automation and our continuous integration infrastructure.

Our turnaround time for bugs in the Future component is also not stellar. At our urging, the Mozilla Metrics team recently started setting up a dashboard to give us various statistics on our Bugzilla usage. Bugs don’t get fixed in the Future queue, so it’s hard to make truly accurate assessments here, but there are a lot of aging bugs in there. According to the numbers, fully 50% of the bugs in the Future component are older than 1 month and more than 25% are older than 6 months. How this compares to other teams or areas, I can’t say, but it certainly makes me empathize with developers who feel their Future-ed bugs have gone walkabout.

Crocodile DundeeIf it makes you feel better in a sadistic way, the majority of bugs filed by RelEng team members go directly into the Future queue. We’re not overly happy about it either. :(

I have a way? Is that better than a plan?

Crew of Serenity on ProspectThings are getting done, though. For example, over the past month, the number of non-Future, release engineering bugs that are actively being worked on has gone from a low water mark of 130 up to over 200 today. For comparison, over the same period, the total number of bugs in the Future queue has slowly crept up from a low of 302 to 323. Mozilla is growing along so many axes that sometimes it feels like keeping the increase in the number of Future bugs to a linear relationship rather than exponential one is an accomplishment in itself.

So how do we stop the increase and start wrestling the Future component back under control?

The first step is triage. Starting this Thursday, February 11th, the RelEng team is going to have bi-weekly triage meetings to specifically prune down the Future queue.

As part of the triage, we’re going to be touching every bug and updating the whiteboard field with searchable tags. Our goal here is to make it easy to find classes of bugs in the Future queue so that duplicates and overlap can be easily eliminated, and fixes can be batched as much as possible.

We’ll be keeping a list of the tags we’re using in the wiki in case you want to follow along.

There are some classes of bugs that we won’t be able to eliminate (e.g. future goals), but hopefully within a few months, we’ll have the Future queue back under control.

It won’t be a quick fix, but it’s one we’re committed to.

Feeds

FeedRSSLast fetchedNext fetched after
a crick in the net XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
A Tale Never Loses in the Telling XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
bluheeler XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
Coop XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
dria.org XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
JOSHMEANS.COM XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
Karen XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
kev XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
Life in Kjell XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
n3wblog XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
nareg XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
pintday.org XML 21:30, Tuesday, 09 March 21:30, Wednesday, 10 March
storm trippin' XML 14:00, Wednesday, 10 March 22:00, Wednesday, 10 March
Talk Without Speaking XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
this is february XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March
zjlw XML 14:30, Wednesday, 10 March 17:30, Wednesday, 10 March