On recipe sharing and media piracy

This is something that’s been on my mind for a while now.

Anyone that I know who has ever spent time creating a recipe in the kitchen or that has a treasured family recipe that has been passed down for generations is always extremely willing to pass it on so that others may enjoy the dish. It takes a certain amount of skill and talent to develop a good recipe as well as many hours spent perfecting it.

This is not to say that these chefs and bakers should never receive monetary reimbursement for their hard work, however those who choose to make a living through cooking are able to in other ways – such as building a restaurant around their own recipes or even selling a book with a large collection of their recipes. Just because they like to share a recipe for free here or there does not mean they do not value their work. Instead I believe the willingness to share causes others to look into the chef in question and support them more.

This is in direct conflict with what we see today in the digital media industry. Certainly the culture of sharing recipes has been around much longer, but today we see a push in the opposite direction. Artists are urged to not share their work to get their name well known but instead sign content deals with large corporations to market the work and make profit of their own.

There are artists and film directors out there that try to succeed through this method of sharing instead attempting to make a living off of live shows and movie viewings. I feel that this is frowned upon because of the industry we have built around the selling of content.

So, what do you think? Are cooks everywhere missing out? Should there be corporations built around marketing and selling recipes or should modern day artists rethink the accepted way to gain success?

This article has been in response to articles like one published on The Guardian’s website this past March. Even though I was directing this article towards artists, it could also apply to content producers who have this same business model.

Thoughts from a new Android developer

I’ve been interested in Android development for some time now. However, I never actually got around to setting up the development environment – until now. Before I give my impressions on the documentation that covers how to do all of this, I’d like to clarify that I’m not new to the development world at all – I’ve had a good few years experience – mostly with C++ and PHP and a few programming courses by now as well. I have not, however, had any experience with Java up until now. These are my immediate thoughts about developing on Android after spending some time (only a few hours so far, maybe 5 or 6) getting familiar with the SDK.

So far, I’ve been very pleased with how well the documentation is written. I followed the setup guide at the Android Developers website. My first step was to download and install Eclipse for my platform. I’m running Mac OS, and that’s the platform that my Android development experience has been on thus far. After getting Eclipse set up I then proceded to follow the instructions to get the latest (2.2 as of this writing) Android SDK and setup the SDK tools.

I also took the time to setup a virtual Android device (AVD) and test it for a few minutes (not as fast as my HTC Incredible!) Even though I did this here, the next guide walks you through the steps. I found them quite self explanatory and took the liberty to do it on my own.

Once finished setting up my development environment I dove right into the Hello, Android demo application. This tutorial shows how a very minimalistic is built and what components it needs. As with the previous tutorial, this one was written very well with a good mix of beginner tips and intermediate developer centric portions. There were few, if any, portions of the guide that left me lost or feeling unsure of what to do next. In addition, I felt comfortable exploring SDK documentation immediately after completing the Hello, Android program and started messing with other Views and Actions available from the SDK.

Whenever I got stuck or wasn’t exactly sure of how to do something (keep in mind that at this point I’ve only been using the SDK and Java for an hour or two now) the excellent Hello, Views tutorials helped set me on the right path.

After only reading those three tutorials and a few documentation pages I felt ready to begin work on my own application. What I have so far is an application that has two layers of tabbed menus with scrollable lists in each section. That’s all I can show you for now – more on that in a later post.

Overall, I’m extremely impressed with how easy it is to develop Android applications so far. It really is quite easy to go from not knowing a thing about Android programming to being ready to build your own application all within a single afternoon or maybe a couple of nights. I’m super excited to continue working on my application and hope that this article helps to alleviate any fears that others may have about getting started with Android development.

Hello, World!

I’m starting this blog to record my thoughts on various topics.

As I am a Computer Science student and have been doing lots of web and mobile development as of late, many of my posts will focus on my experiences with web development, Android development, and the occasional news item as I see fit. However, I am not claiming this is a tech or development blog and as such I may also write about other topics.

Runner. Developer. Student.