Thoughts

Stop Talking, Start Making

August 11th, 2010  |  Published in Development, Errata, Mobile, Thoughts, barcampnyc, hackathon, mobilecampnyc, transparency

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.

MTA MetroCard Calculator – 30 minute project

July 2nd, 2010  |  Published in Android, Development, Errata, Mobile, Thoughts, hackathon, transparency

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.

Two simple ways Google can make Android development more designer friendly

April 13th, 2010  |  Published in Android, Development, Errata, Mobile, Thoughts

I’ve been posting some of my more technically-oriented posts and micro-posts over on http://www.techreative.com/. Here’s the most recent one.

Making Android development designer friendly

Tonight.im – Sneak preview for early adopters

March 15th, 2010  |  Published in Thoughts, hackathon

I’m starting to take the wraps off my latest side project, http://tonight.im/, a site based on the notion that:

your check-ins + your weigh-ins = better choices

My office recently started a weight loss contest, and I bought this Withings Wi-Fi enabled scale to track my weight. The information from the scale is very helpful, but that data alone wasn’t helping me lose weight.

My biggest weakness when it comes to dieting is going out with friends, so tonight.im was created to turn that weakness into a strength. By telling me which check-ins (and ultimately which friends) are more healthy than others, it helps keep me on my toes and make healthier choices when I check-in to bars and restaurants.

WHAT THE SITE DOES

  • It tracks your weight using a Withings Scale.
  • It tracks where you eat, drink, go to the gym, and hangout using Foursquare
  • It shows you the correlation between your weight change and your eating, drinking and gym habits.
  • It uses your information along with others’ information to assign a “weight value” to bars, restaurants and gyms.
  • If you want, it can send you a text message to remind of you of this information each time you check-in to a healthy or unhealthy place on Foursquare.

This last bit is key. It’s one thing to have a cool site where you can see where you’ve been, and what impact that has on your weight, but being healthy is all about consistently making the right decision in the moment. That healthy decision could be something small — maybe you order a hamburger instead of a bacon cheeseburger, or a glass of wine instead of a pint of beer. Heck, it might even be justification for an unhealthy decision like you’ve gone to the gym five days in a row, so you know what, you deserve the extra large milkshake. But at least you’re making a more informed decision.

This is an early proof of concept, so I’d love any feedback. Stay tuned for more.

The Pig Head and Football Ragu

January 2nd, 2010  |  Published in Errata, Food, Thoughts

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.

Happy Birthday Bar Code

October 7th, 2009  |  Published in Errata, Mobile, Thoughts

A lot of people find this blog because of my articles on mobile bar codes, so I thought I would mention Google’s spotlight today celebrating the 57th birthday of the bar code. In case you miss Google.com today, here’s a screenshot.

Pretty sweet.

Ovi Store download stats

July 13th, 2009  |  Published in Thoughts

So my simple Morse Code widget has been in the Ovi Store for almost two months now. It’s free, and I didn’t spend too much time developing it, but the Ovi Store finally got their Reporting system back up and running, so I thought I would share some stats on how the app is doing.

  • As of this writing, the widget has been downloaded 10,582 times.
  • The widget has been download from 130 different countries.
  • The top 10 countries that downloaded the widget are UK, USA, India, Australia, France, Finland, Brazil, Singapore, Netherlands and Turkey.
  • These 10 countries only accounted for 62% of downloads.
  • 65% of the downloads are coming from four devices – E71, N95 8GB, N95 and N96.

How is this comparing to other developers out there?

Using Minify to optimize your Nokia WRT widgets

May 3rd, 2009  |  Published in Development, Mobile, Nokia, S60, Thoughts

Recently, I’ve been playing around with Minify. For those who’ve never heard of it, Minify is a simple HTTP content server built as a PHP5 application. It’s placed in a folder on your server, and then either using a querystring or mod_rewrite, it will dynamically merge and minify CSS and JS files as they are served up to a user’s browser. This allows you to develop using multiple CSS or JS files with comments and clear visual formatting, but when they are delivered to your users via a browser, they get minified and optionally merged making your site load and render faster in the user’s browser.

While Minify is meant to run on a webserver, I thought it could also work as a handy offline tool for optimizing Nokia WRT widgets. Since WRT widgets are just zipped folders of Javascript, HTML and CSS, Minify seems like a simple step you could include in the widget packaging process of your workflow before testing and deploying.

I wasn’t sure how much savings Minify would give the average WRT widget, so as a quick test I batch processed the contents of the STEW sample widget from Forum Nokia using Minify running on a local webserver. The resulting files were bundled as a new widget, and here’s a comparison of the two.

  Size of all Files WGZ size
Forum Nokia version 122.4K 83.0K
Minified version 106.3K 78.2K
Difference 13.2% smaller 5.8% smaller

The savings aren’t gigantic, but they’re significant enough that you should seriously consider adding this step before deploying a widget. I’d also be curious to see if anyone has done comparisons about whether or not Minify affects how much memory is consumed at run-time in the browser.

I might do some more work on automating this process or creating a tool that minifies widgets automatically for you, but ideally, I think this should be something automatically built into widget IDEs like Aptana.

How are other developers out there currently optimizing their widgets for release on Ovi Store?

Legislators’ web pages containing earmarks

April 11th, 2009  |  Published in Development, Politics, Thoughts

Over on Taxpayers for Common Sense, they’ve been doing a good job of keeping up with how well House members are complying with new rules about posting earmarks and appropriations to their websites.

The webpage on taxpayer.net gives some insight into their process, but unfortunately, their Excel spreadsheet only uses legislator’s names. This is fine for most individual projects, but if you want to mashup the data across multiple data sources, then ideally you need a common identifier like a GovTrack ID or a BioGuide ID.

Anyway, I took a quick stab at writing an Excel macro which attempted to figure out people’s bioguide IDs. Here’s the results:

Database of FY2010 Earmark Requests (with BioGuide IDs, version 8)

Note that this work was done with version 8 of the Taxpayer.net database, so if they continue to release new versions of their spreadsheet, this representation might be a bit behind.

The Digital Transparency Index

April 9th, 2009  |  Published in Thoughts, hackathon

Now that RepresentedBy has launched, I’ve had a little bit of free time to turn my attention back to my last post about digital transparency.

To help keep the conversation going about digital transparency, I’ve setup a website dedicated to the work around the Digital Transparency Index. The goal of this site is to act as one way of measuring online activity and transparency with legislators, and by providing the data in an open format, allow others to mash it up with their data and observe trends in Congress.

It’s still a work in progress (is anything finished these days?), but check it out and let me know what you think.

http://digitaltransparency.appspot.com

Current Digital Transparency Index for Congress