Skip to main content

Homegrown Wisconsin CSA Weeks 1 and 2

I signed up for the Homegrown Wisconsin CSA program this year. For anyone who doesn't know what that is, Wikipedia and Localharvest do a nice job of explaining it. Basically, you pay money to a nearby farm, or set of farms in this case, and receive a bunch of fresh, healthy, local produce every week. The cost is about on par with buying veggies at the grocery store, but the quality is much higher, it's a lot fresher, and the farmers get a bigger cut. I'm fortunate that one of the pick up sites for this particular program is just down my street, so there is simply no excuse for me not to do this.

One of the most interesting, and occasionally frustrating, things about doing a CSA is the surprise factor. To put it succinctly: you never know what you're gonna get. Nature isn't a mechanical contraption spitting plants out of the ground according to finely tuned inputs and schedules. On the contrary, the quantity, quality, and distribution of the farm's output follows a probabilistic model. Growing is a stochastic process where a million incalculable factors (most notably weather) influence the final result. You generally know which produce will be ready for harvest within a certain window, but the exact yields for a particular week aren't known until hours before pickup.

The biggest surprise for me came a couple years ago, when I received an entire basket (think laundry basket) full of tomatoes sometime in July. I'm not much of a fan of tomatoes to begin with, but this would be a bit much for anyone to eat before they spoiled, which unfortunately did happen to many. So my goal this time is to make sure everything gets eaten, or given away, never wasted. To that end I'll be documenting each week's pickup and holding myself accountable for its full consumption and enjoyment. Nobody will legitimately be able to accuse me of not eating my veggies between now and October!

Week 1: June 17, 2009





Rhubarb, green garlic, white button mushrooms, asparagus, common mint, strawberries, spinach, and a ton of lettuce

The asparagus was excellent (a lot better than the usual from TJ's) and the strawberries were very tasty. The biggest problem was the rhubarb; I'm not much of a baker so I didn't know what to do with it except eat it like celery. Unfortunately I had to throw some out since it went bad in the fridge (I didn't know it needs to be stored in a wet cloth, then cut up and frozen if not used).

Week 2: June 24, 2009





White button mushrooms, spinach, green garlic, peas, strawberries, rhubarb, spinach, common mint, zucchini, more lettuce, and two dozen eggs from chickens eating their natural omnivorous diet (including insects and worms)



Here I present my "A little bit of everything in the box plus a few stray frozen shrimp" stir fry

So far so good; I have no issues downing a metric ton of lettuce per week. But seriously, if you have any ideas for rhubarb that aren't rhubarb pie, then please get in touch with me.

Comments

Popular posts from this blog

Don't Trust the Process

Don't Trust the Process Prelude The first thing I did, after signing the offer letter, was to uninstall the Blind app from my phone. My brain needed a long break from that one. The anonymous commentary from tech employees is valuable, but I don't love the picture it paints of us. Next, I cancelled all the five-hour-long "virtual onsite" interviews I had scheduled for early January and closed my in-progress homework assignments. The feeling of liberation from this was palpable. I had finally landed a new job, one that I was very excited about. More on that later. For now, let's delve into the months of misery leading up to it. As is tradition in my field, allow me to lay out a statement of scope. Not in Scope A solution to these problems. If you're someone who thinks that nobody can present complaints without bundling them with a neatly packaged solution, you should probably turn back now. Any treatment of those coming from less advantage

Reflections on working as an election judge

I don't know how to start with this. There are a number of isolated moments that stand out in my mind. Some are poignant, like the woman who, upon hearing we couldn't find her registration in the computer, shook her head and said, her quiet frustration palpable, "I just won't vote, then." She put her driver's license away and calmly walked out of the room. We had already told her about the Voter Verification Hotline, but she didn't seem all that interested in waiting on hold for what promised to be a very long time. So she left without casting her ballot. I tend to personalize negative outcomes in a way that isn't warranted (my wife can attest to this), so I had to acknowledge, then dismiss, the sinking feeling that the situation was somehow my fault. Some moments were joyful, in that primitive "caveman starts fire" sense, like when our one troublesome ePollbook (the custom laptop builds used to check in voters) finally connected to th

All I Want For Christmas is a Super-Intelligent Public Transit System - Part 1

I was having a friendly debate with another commenter over at Chicagoist, in an article lamenting the latest round of RTA cuts . Upon floating some rough ideas for how Chicago's transit system (or, indeed, any city's transit system) could be made to operate more dynamically, I was rebuked by a solid wall of skepticism. I think my biggest problem--and my problem with most technology--is that I simply don't see the benefit outweighing the expense of implementation coupled with ongoing maintenance. I honestly believe that a simple, fixed route bus system runs about as efficiently as it is possible for a bus system to run. Could it be? That nearly the simplest possible approach to a bus system one can imagine happens to be the most efficient? I find that to be highly unlikely. Many problem domains don't favor simple approaches. Said another way: the universe is complex; deal with it. Take one example from the field of computer science: sorting numbers. Specifically,