Errata

Sep
26
Posted by wubbahed at 9:27 am

My current work focuses on creating software that improves the home cooking experience. Over the past two years, I’ve worked with food writer Michael Ruhlman, and together we’ve started simple and small and released two products. First was Ratio, a digital companion to his book Ratio: The Simple Codes Behind the Craft of Everyday Cooking. The second, released earlier this year, was Bread Baking Basics, an iPad app that lets you design your own bread recipe — choose a flour, shape, pan, and quantity — and a custom bread recipe is automatically created for you.

What sets the Bread app apart from most other cooking apps is that we’ve used technology to re-think the notion of a recipe.

Most recipes are static lists of ingredients and instructions. They can help you make one really yummy dish, but that’s it. If you want to double a recipe, you have to do the math yourself. If you have to make a substitution then you have to find that information elsewhere and incorporate it yourself. And if you’re trying to make dinner from three separate recipes, good luck trying to organize all those steps into one coherent plan of action.

I would never expect a cookbook on my shelf to do any of those things for me. But an iPad? A laptop? A smartphone? Oh, yes. I want it to double quantities and make substitutions based on my dietary needs. I want it to merge three different recipes into one step-by-step plan. I want it to recommend new dishes based on what I like. I want it to plan out my meals for the week using only things on sale and in season. I want every recipe to have a button that says “Buy ingredients from local farms,” and then have it suggest more recipes based on the leftovers. I want it to show me a three course meal that my friends would love and then give me the option to invite them over.

Okay, so Bread Baking Basics doesn’t exactly do all of those things… yet. Those features could be built, but to that I need data. Data about food prices. Data about inventory from local farms. Data about delivery times. Data about food products and their ingredients. Data about expiration dates.

But once that data can be brought into our software, then there’s no longer a need to hack the existing food system. Instead, we will have just created a new one. A new food system that uses data and technology to allow farmers and individuals to buy directly, and will be rooted in products that put the consumer first and make it insanely easy to cook and eat local, sustainable or organic foods.

Accomplishing this will be hard. Very hard. Farm work hard. But not impossible.

Who’s up for it?

This post originally appeared on FoodAndTechConnect.com

Jun
23
Posted by wubbahed at 12:32 pm

They’ve launched the latest version of NYCBigApps, called NYC BigApps Ideas, and this one is beautiful in it’s simplicity — all you have to do is write your idea for an app in 140 characters or less. That’s it! The top 25 ideas will be voted on by a group of judges and some of the winning apps might actually be made.

I’ve got a ton of ideas, but here are a few that I entered. If you like them, it would be awesome if you could vote for them on the site!

Got an idea? Submit it!

Aug
11
Posted by wubbahed at 3:22 pm

I’ve proposed a talk for SXSW Interactive next March called “Stop Talking, Start Making,” and I would love it you could visit the SXSW PanelPicker and vote for my presentation (along with all the other sessions that interest you). SXSW is unique from other conferences in that the popular vote heavily influences their selection, so your voice definitely counts!

“Stop Talking, Start Making” is about the importance of rolling up your sleeves very early in the creative process, and spending 24 hours getting your hands dirty building something. You can’t just sketch something out or put together a few slides in a PowerPoint presentation, you’ve got to build and demonstrate a working product.

In the tech world, this approach isn’t new. For years, it’s happened at BarCamps and hackathons, and the ethos is a central part in many hacker labs, co-working spaces, and publications.

But this presentation isn’t for developers — it’s for creative types, marketers and brand owners. You’ll learn ways you can incorporate the hackathon model into your creative development process—to rethink a brand, quickly build ideas from scratch, and to incorporate new and emerging technologies into an existing brand.

You’ll also learn how the hackathon can be an invaluable tool for evaluating and nurturing internal talent, as well as for recruiting new talent.

Most importantly, it will be fun and entertaining. I promise.

Aug
09
Posted by wubbahed at 1:52 pm

The Challenge: Build and release an app that required less than 12 hours of work.
The Result: NYC Subway Status for Android

I’ve been beating the drum lately on the need to build things very quickly. I’ve found that despite loads of thinking and planning, often you don’t discover most of the real problems with your idea until you’re knee deep in development. Building something in a brief time period is meant to short circuit the process and avoid analysis paralysis.

Working this way, though, can be very stressful. You’re having to cut corners, to make compromises, and to eliminate functionality in order to meet your deadline. However, working like this also forces you to simplify your ideas and focus on the core user experience which can lead to a simpler, more refined final product. Sometimes it’s better to do one feature well than to cram in three or four features.

The result of this latest personal challenge is the NYC Subway Status app for Android. It was built in a few hours and does one thing very well — tells you if the NYC Subway lines are running smoothly, encountering delays, or scheduling maintenance. Here are some screenshots of the app in action.

NYC Subway Status

You can install the app for free just by searching on the Android Market. Alternatively, you can scan in this barcode on your phone.

qrcode

Enjoy!

UPDATE: Version 1.0.3 now released!

Jul
02
Posted by wubbahed at 11:42 am

Last night I attended the In Code We Trust meetup at Eyebeam, which was an excellent gathering of people talking about what they’re currently doing in the Gov 2.0 space.

One of the speakers was Sarah Kaufman from the MTA, highlighting the hard work they’re doing right now to help bring MTA information and data to the developer community. Check out the MTA data sets currently available including the new GIS information about subway entrances and exits.

Sarah’s talk reminded me of something I’ve been wanting to do for a long time — create a simple calculator to figure out how much money to put on a MetroCard. The MTA vending machines make it easy to put an exact dollar amount on a card, but it doesn’t make it easy to figure out how to add 4 rides or 8 rides to a card. It’s not a hard problem, so I took 30 minutes last night and made a simple web page that figures this out for you. It should work on iPhone and Android, so check it out.

http://bit.ly/mtacalc

http://bit.ly/mtacalc

Finally, I should add that I made this in 30 minutes, so it’s probably got bugs, but who cares? It’s usable. It’s a released product. It’s more important to get something out there and get feedback than to linger in development forever trying to make it “perfect”. Let me know what you think.

Jan
02
Posted by wubbahed at 2:56 am

So a few weeks ago, I went to The Meat Hook to pick up a beef roast for Christmas dinner. Brent helped me pick out a nice 8 lb. roast (which he then layered with fat and tied nicely — something I don’t think I quite fully appreciated until the roast came out of the oven), and then we got down to business. I’ve been following The Meat Hook on Twitter for a while now, and these guys aren’t just dealing with your ordinary bits. They’re cranking out stuff like chorizo-stuffed duck hearts, goose rillettes, lamb belly and bahn mi dogs. That’s right, they took a Vietnamese sandwich and turned it into a sausage. HOT.

Compared to these guys, I’m clearly Mr. Amateur Newbie, so I gave Brent my 10 second charcuterie resume, and asked him to surprise me with whatever he’s got in the meat locker. He came out first with some pig’s skin, rolled it up, wrapped it up and handed it to me. I thought that might be all, but then he went back in the locker and emerged with a pig’s head.

Pig's head from @themeathook Yup, a whole head. They had already taken the cheeks out to make guanciale, but there was still plenty of meat left, so I headed for the checkout with a beef roast in one hand and a pig’s head in the other. It was going to be an interesting weekend.

I’d never cooked a pig’s head before, so I figured I’d play it safe and start with the basics, namely head cheese, which isn’t really cheese at all, more like a meat jelly terrine. I used the recipe in my copy of Fergus Henderson’s The Whole Beast: Nose to Tail Eating. And since it’s not every day that you get a whole pig’s head, I also decided to make the Crispy Pig Ear salad from the book. Both the head cheese and the crispy ears turned out pretty good considering it was my first attempt making them, but what really turned out amazing was the recipe I made with the roll of pig’s skin.

Brent told me how you could slow cook thin ribbons of pig skin in a tomato sauce and after a few hours just before the skin completely falls apart, you end up with the most delicious porky ragu you could ever want. So I gave that a shot, and it turned out awesome. Here’s a pic of the final three dishes, and below is the recipe I hacked together for the ragu.

Pigskin Ragu, crispy pig ears and head cheese.

Pigskin Ragu with handmade pappardelle, alongside Crispy Pig Ears and Head Cheese.

Pigskin Ragu (if the name weirds you out, you can also call it Football Ragu)

Ingredients

  • 1 fennel bulb
  • 2-3 medium sized leeks
  • 1 large can (28 oz.) of whole, peeled tomatoes
  • 1 roll of pigskin (about 1/2 lb.)
  • olive oil
  • salt, pepper and whatever other fresh green italian herbs you have on hand (e.g. parsley, thyme, rosemary)

Directions

Thinly slice the pig’s skin into strips about 1/8″ wide and 1″ long. Saute in a pan with a little olive oil over medium heat for a few minutes just to heat them through and to brown the outside a little. Now open the can of tomatoes and strain off all of the tomato juice into the pan with the pig’s skin. Add a little bit more water if the pigskin isn’t fully covered. Turn the heat down to low and let this simmer for about an hour.

Meanwhile, thinly slice the fennel bulb and leeks. Saute in a stock pot with a little bit of olive oil on medium heat for about 5 minutes until they’ve sweated some. Coarsely chop the canned tomatoes, and then add them to the pot. Turn the heat down to very low and let simmer. You don’t want the pigskin or the tomato mixture to boil, so just keep them low and slow for the next hour.

After an hour of simmering, pour the pigskin/tomato juice mixture into the pot with the leeks, fennel and tomato. Add whatever fresh herbs you want and stir everything together. Continue to simmer for another hour, tasting and seasoning as you like, just be careful that if you simmer the sauce much longer the pig skin will start to completely melt. Personally, I stopped cooking the ragu just before this melting point so that there was still some texture to the finished ragu. But if you don’t like that, just keep simmering and the texture will melt away, but the flavor will remain.

Once the ragu is done, serve with your favorite pasta. In my case, I just threw together some handmade pappardelle using the 3:2 Pasta Dough from the Ratio iPhone App. Delicious.