Thinking about the Open Web

I’ve been thinking about how to talk to people about what the Open Web is, why it’s so important, and why they should care.

The Open Web as a global public resource

It struck me that the Open Web is analogous to some other fundamentally vital things in our society:

• public libraries
• public schools
• public parks
• public broadcasting
• public roads
• public art
• public museums
• public galleries
• etc.

Many of these things are deemed so vital a part of our everyday lives and societal infrastructure that we support them through our tax dollars. Others are supported by concerned citizens who believe so deeply in their importance that they donate not only their hard-earned money, but also their time, skills, and creativity.

The Web is an increasingly important part of our lives, and it is absolutely essential that it remain free and open and accessible to all. If it doesn’t — if the Web becomes closed, restricted, controlled, and inaccessible to anyone who is disadvantaged or marginalized in some way — our whole, global society will suffer as a result. The Web cannot become something that further delineates the haves from the have-nots. It is already far too important for that, and it is still only in its infancy.

Mozilla exists to support the Open Web

Mozilla is an organization devoted to ensuring that the Web continue to develop as and remain a global public resource — akin to libraries, schools, parks, and roads — and everything we do, every resource at our disposal, is focused towards this end. This is the absolute core of our mission as outlined in the Mozilla Manifesto, and it is the heart of everything we strive towards.

Why Mozilla makes a browser

Making a browser is one of the most important things Mozilla currently does — not as an end unto itself, but rather in support of our larger mission and goals.

The browser is by far the most important tool we use to create and consume the Web. Without an open browser there is no Open Web. This is why we build Firefox, and why we’re pushing hard to get Firefox on to as many devices and desktops as we can. The Open Web is an increasingly crucial part of our lives and our society, and Firefox is one way we’re working to ensure that the Web remain open and available for everyone.

What do you think?

Is this a useful way to think about and talk about the Open Web to people who might not quite get what we’re so excited about? Not everyone is going to grok the analogy in the same way — and this certainly isn’t the only way to talk about it — but I think that most people understand that public works are a good thing, and that ensuring open and equitable access to fundamental resources and infrastructure — which now includes the Open Web — is an essential part of a just and civilised society.

Also, if you have photos posted but don’t use Flickr, please leave a comment here with a link to where you’ve hosted them. Thanks!

So after living in denial for longer than I expected, I finally caved and picked up an iPad (wifi only, 64gb — Rogers, my data provider, can eat [dirt] if they think I’m buying a second iDevice data plan). Anyhow, it’s really quite fantastic except for one notable and surprising thing: the App Store just completely sucks. It’s just awful — impossible to browse for anything, navigation is a joke, etc etc.

If you want to find apps, you basically have to rely on third party review sites. Here are three that I’m finding handy: App Shopper (great, everything), Touch Arcade (ok, just games), and 148 Apps (mediocre, everything).

We got the iPads on Thursday last week and I’ve been spending quite a bit of time trying new apps, games, etc etc. Here’s a quick list of stuff I love so far (all links go directly to iTunes, sorry).

Not Games

• Air Video ($2.99 but worth much, much more)
• Evernote (free)
• Dictionary.com/Thesaurus.com (free)
• Wikipanion (free)
• GoodReader ($0.99)
• Twitteriffic (free)
• Things ($19.99)
• Instapaper Pro ($4.99)
• Kindle (free)
• Stanza (new iPad version, free)
• Epicurious (free)
• Adobe Ideas (free)
• Wordpress (free)

Games

• Dizzypad HD (free + not-free alternate game modes)
• Aurora Feint 3 (free: match-3-w/ rpg elements)
• Word Quest Plus ($4.99: wordsearch)
• Words With Friends HD ($2.99: Scrabble-alike w/ online play)
• Jumbline 2 ($2.99: word scramble game)
• NYT Crosswords (free)
• Amazon: Hidden Expedition ($4.99: hidden object)
• Bomb Master ($1.99: physics puzzler)
• Azkend HD ($4.99: match-3-ish sort of thing – free demo here)
• Orbital HD ($2.99: hard to describe)
• Backgammon NJ HD ($5.99, single-player only, very good)

Ok, that’s it for now. What iPad apps have you tried that you like and would recommend?

Updated to add Air Video.

Ingredients

• 2 racks baby back pork ribs, cut in half
• 9-12 cloves garlic, smashed and rough-chopped
• 3 large onions, sliced
• 6 sprigs fresh thyme
• 6 sprigs fresh oregano
• 10-12 dried chilis
• 2-3 tbsp black peppercorns
• Water
• BBQ sauce of your choice (Mad Dog Original, here)

Method
Heat oven to 300 (275 if you have more time, 325 if you have less).

Scatter half the onions, garlic, thyme, oregano, peppercorns, and chilis on the bottom of a roasting pan. Place ribs in pan, overlapping slightly. Fill pan with water until ribs are 2/3rds submerged. Scatter the rest of the onions, garlic, thyme, oregano, peppercorns, and chilis over the top of the ribs (it doesn’t have to be tidy). Cover roasting pan tightly with 2-3 layers of tinfoil (or cover, if your pan has a cover…mine doesn’t).

Put ribs in the oven for around 3 hours. They will be fully cooked and fork-tender when they’re done.

Remove ribs from pan, leaving behind basically all the other stuff. Let cool a bit, then slather with BBQ sauce and grill to caramelize. Do a few coats of the sauce and take your time, it’s worth it. You’re worth it.

Serve with Bourbon baked beans, Fennel-cabbage coleslaw, and beer. Then watch some hockey.

1. Copy/paste these rules and questions into a blog post, answer the questions, then tag some other people (however many you like) and encourage them to do the same.
2. Include a link to the original post.
3. You don’t have to be tagged to take part — if you see this post and want to play, just dive on in. Simple!

How (and when) did you originally get involved with an open source project? Which projects have you contributed to?

I first got involved with open source-related stuff in 1999 when I started Linuxchix (still going) and the Open Source Writers Group (long since dead). In addition to those, I’ve contributed to the PA-RISC/Linux project (about forty million years ago), and the Mozilla project, plus little fiddly-bits here and there.

Why did you choose to contribute to an open source project?

Because I could. I had been using Linux for a few years at that point and I loved it — I loved the community and the openness and everything else about it. When I realized that I had the skills and ability to make real and useful contributions, I got involved. Linux and the open source community had given me a lot, and I wanted to give back however I could.

If you were to pick one or two people who have had a major influence on your involvement with open source, who would those people be? Why?

Chris Beard: Some 10 or 11 years ago, I read about Chris and the Puffin Group (a small Linux consulting company) on Slashdot and sent Chris (a complete stranger) an email asking for a job. He hired me. This is a pretty short story for what has ended up being a decade-long friendship. I have an enormous amount of respect for Chris and the work he does — easily one of the most visionary and driven people I’ve had the privilege of working with.

Mike Shaver: Some 10 or 11 years ago, I met shaver the day before his wedding to which he immediately invited me (a complete stranger). I declined, and I regret that decision to this day because Mike has turned out to be one of my best friends. I’m going to stop now because I’ll just get teary-eyed, and it would take more than a few hours to talk about how his friendship has (actually, and for reals) changed my life.

Both Chris and Mike are why I’m part of Mozilla now, and I believe I still owe them both a beer or two for that.

How have you personally benefited from being involved with open source projects?

Getting involved with open source turned into a career for me. Mozilla, in particular, has been spectacular because this project encourages people to push beyond themselves and to reach for and learn new things all the time. I’ve learned more and done more in the past five years of being involved with Mozilla than I would have been able to do in any traditional organization, had I been able to wedge a foot in the door.

Not only has it become a career, being involved with open source has (as I foreshadowed before) lead to some of my deepest and most lasting friendships. It turns out that open source projects are a fantastic way to meet like-minded (but oh-so-entertainingly diverse) people. I know, talk to, and work with incredibly brilliant and passionate people all over the world, every day. I wouldn’t trade this for anything.

What advice and/or encouragement would you give to someone who is considering getting involved with an open source project?

Do it! Get involved. Persevere. Step up. Be brave. It can be awfully intimidating and overwhelming when you first start out, but don’t give up. Find some niche where you can make a contribution, then just get started. It could be the best thing you’ve ever done.

• Chris Beard
• Mike Shaver
• David Humphrey
• Lukas Blakk
• Mike Morgan

The rules:

1. Copy/paste these rules and questions into a blog post, answer the questions, then tag some other people (however many you like) and encourage them to do the same.
2. Include a link to the original post.
3. You don’t have to be tagged to take part — if you see this post and want to play, just dive on in. Simple!

The questions:

1. How (and when) did you originally get involved with an open source project? Which projects have you contributed to?
2. Why did you choose to contribute to an open source project?
3. If you were to pick one or two people who have had a major influence on your involvement with open source, who would those people be? Why?
4. How have you personally benefited from being involved with open source projects?
5. What advice and/or encouragement would you give to someone who is considering getting involved with an open source project?

That’s it! I’ll post my own responses soon :)

It might sound sort of silly or contrived, but it turns out that a simple note of appreciation really can have a huge impact. Since I’ve started using Rypple to send out kudos, I’ve received a few notes from folks telling me that I’ve basically made their day. It’s a little thing, and doesn’t really take more than a couple of minutes out of your day, but it can really make a difference. We don’t often get genuine, heartfelt, positive feedback, so it’s really incredibly energizing when we do.

Everyone with a Rypple account (which is anyone, since everyone can sign up) can log in and send kudos to anyone with an email address. It’s totally wide open and anyone can do it — so if you have a few minutes sometime today, think of someone who’s done something awesome, head over to Rypple, and send them a kudos. The more you do it, the more fun it becomes.

So, in addition to getting new content produced to help people, I’m going to start collecting existing materials together and figuring out how to make those easier to find and use.

I’ve created a new page on wiki.mo called Learning Mozilla, listing on it some of the useful things I already know about. Now I need your help: if you know of other resources that would be useful for someone who wants to learn more about Mozilla, please take a few moments to add it to the page or leave a note (with a URL) in the comments here.

Anything and everything is great — I’ll dig for more content as I can, and I’ll take it upon myself keep the page cleaned up and organized, so don’t worry too much about where to list things or how to format stuff. Just add the links and we’ll sort out the rest as we go.

On the other hand, positive feedback is absolutely energizing. Those moments where someone goes out of their way to say “thanks” or “awesome job” or “you rock” really does make it all worthwhile. Feeling appreciated — knowing that someone genuinely cares about and values the work you do — can often make the difference between something being a burden or a joy. For me, receiving positive feedback is the most powerful motivator out there — more so than money, fame, or anything else.

Rypple (which we use at Mozilla) recently built a new feedback mechanism into their service called “kudos” that you can use to send someone a quick “thanks”, “you’re awesome”, or “you rock” sort of message. The message you send is visible to everyone in the organization, so serves as a public note of appreciation. Other people can comment on the kudos as well, so there’s a way to quickly add a “+1″ or otherwise pile on the love. You can read more about the Rypple kudos feature (and an ongoing contest they’ve launched to promote it) over at WorkplaceHero.com.

The Rypple kudos system really is fantastic. We don’t often go out of our way to publicly acknowledge the awesome things our coworkers do, but Rypple has given us a fun, fast, simple, lightweight, and unintimidating way to do so. If you haven’t checked it out yet, you should — take a minute to send a kudos and make someone’s day :)

So far, people have suggested the following:

• Lifecycle of a Bug – introduction to the stages involved in fixing a bug from start to end
• Building Firefox – introduction to getting the Firefox source code and compiling it, while going over the basics of hg
• Test Frameworks – introduction to the different test frameworks we use, and how to write a basic test in each of them
• Drinking from the Firehose – how to stay on top of the news, difference between “stream of development and ideas” and “announcments”, how to understand things like what the next milestone is
• Bugzilla for Developers: Getting your patch into the product – how to nom for review; how to determine if you need to nom for approval, blocking, etc.; writing tests; checkin wrangling; watching the tree.
• Gaining Traction – how to publish that wicked cool idea you have; how to rally people around it to see if there’s interest; moving from idea to implementation
• How to navigate the code using MXR/DXR
• How to use and contribute to MDC
• Writing your first automated test
• How to do your own screencasts/videos
• Mozilla Developer Tools & Workflow
• How to optimize edit/compile/test loops
• Presentation tips & tricks

What other screencasts or video introductions do you think would be useful for learning Mozilla and getting involved with the project and community?

Ingredients

• 5 tbsp extra virgin olive oil
• 1 1/2 tbsp white wine vinegar
• 1 1/2 tbsp fresh lemon juice
• 1 clove garlic, finely minced or grated (a microplane grater is a wonder here)
• 1 tsp grated lemon zest (see above re: microplane grater)
• 1/2 tsp fresh ground black pepper
• 1/2 tsp honey (or brown sugar, mirin, etc…something sweet)
• Dash salt

Directions are simple: put everything into a bowl, bottle, or jar and whisk or shake to combine.

The fennel & celery salad is insanely simple:

• 2 bulbs of fresh fennel (aka: anise), sliced as thinly as you can manage
• Roughly the same amount of thinly sliced celery
• An ounce or so of parmagiana cheese strips (make these by using a vegetable peeler on a hunk of the cheese — long, thin strips)

Toss these with the vinaigrette. Ta dah.

Ingredients

• 4 c chicken stock or water
• 1/2 c milk
• 1 c polenta (corn meal)
• 1/2 c ricotta cheese
• 2 oz shredded parmagiana cheese
• 3 tbsp butter

Directions

1. Bring chicken stock to a low boil in a medium sauce pan.
2. When boiling, whisk in the polenta, pouring it into the stock a little at a time and whisking well — do this slowly to avoid lumps. Note: it will thicken quickly…do not be alarmed.
3. Once the polenta is all stirred into the chicken stock, turn down to low (pretty much as low as your burner will go), and cover. Whisk vigorously every 10 mins.
4. After 20 mins, whisk in the milk. Continue to cook on low, stirring every 10 mins for another 20 mins.
5. At this point, grab a spoon and taste the polenta. Depending on how coarsely ground your cornmeal is, it could be done now, or you might need to keep cooking it. If it’s grainy, keep cooking. It should be soft and creamy.
6. Stir in the ricotta cheese, then, once that’s well blended, stir in the parmagiana cheese. After that’s all incorporated, stir in the butter.
7. That’s it. Fantastic as a bed for braised meat, sliced steak, mushroom ragu, etc etc etc. Keeps well, and solidifies (like jello!) when cool so it can be sliced and fried or grilled. Yum!

Before 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.

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.

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.

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.

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

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

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

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).

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.

• Soba noodle salad with edamame and tofu
• Chickpea & spinach curry (Channa Masala)
• Double oatmeal cookies with cranberries and walnuts
• Leek + potato soup
• Wild rice and quinoa salad
• Black bean and sweet potato soup
• How to make a yummy vinaigrette
• Basic arrabiata sauce
• Tzatziki sauce
• Blue cheese, walnut, and apple salad
• Sweet potato and chickpea curry
• Spinach-Hummus recipe
• Easy asparagus soup
• Sunday veggie soup
• Pasta with savoy cabbage
• White Bean Soup
• Pasta with Baked Tomato Sauce
• Wicked Bean Salad
• Nutty Brown Rice

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!

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.