Skip to main content

Comment: Are you an Internet Producer or Consumer?

Most people who use the Net nowadays really fall into one of two categories.

1) Internet Consumers - This is most of us. We may occasionally paste some video into Facebook, but we normally use the Net to swap emails, read the news and occasionally look at pictures of other naked people.
2) Internet Producers - Leaving aside the techies for a moment (the people who "build" the Internet), these are the people who are obsessed with getting their points across, their opinions discussed, their crappy music demo listened to, and posting naked pictures of themselves online for the Consumers to look at (oh yeah, let's not forget those budding young stars trying to get their 3 minutes of YouTube fame).

Ok, so most of us probably fall somewhere in the middle. We blog, we may occasionally post something to YouTube, and maybe we daydream about being naked online before we realize what a bad career move that is...

For about 10 years now I have been making a living as one of these people who "build" the Internet. Were it not for this wonderful piece (pieces) of technology I would still be living in my parents' basement, but lo and behold, I now have a lucrative career. But you know what? There's not one of us "techies" who doesn't dream about either making history or having a blog so popular you only need to work on it 3 hours a day.

For a long time now, I have been pretty much a consumer outside of my professional life. I would post questions on bulletins when I had a technical question and lo and behold, someone would answer it. Tonight I decided to try and give back to the tech community, but every time I saw a question I knew the answer to, someone had beaten me to answering it.

So instead I decided to write this little article to keep you all amused.

It's my way of giving back to the community...

I must remember to post this on Reddit.com so I will get a few page views.

;)

Comments

Ringo Mercedes said…
While I do occasionally post to my blog, I am more of a consumer really...
Anonymous said…
dCf8sODLTz Holy Casino WMDt2wasXh Taj Mahal Casino RtWDQI97vB Laughlin nTedcEiNXk Casino 3d DcMvBQaj6 Hotel Casino t4Ox2Fl8C Casino Photo Zcq21rzJiy Red Rock Casino ahu07TDWd Tunica Casinos

Popular posts from this blog

Freezing Gems

What is a gem and why would you want to freeze it?

In Ruby, there are times when you want to access pieces of functionality that other people of written (3rd party libraries) and you normally have 2 options. You can install a plug in or install a gem. Normally the method you use is determined by which ever is made available by the author.

Gems are installed on the host machine and are pretty handy when you want to run things in the command line or else across lots of projects, but their downside is that if you use a gem in a Rails project there is no automatic publishing mechanism when you deploy your site. You will need to log onto the remote host machine and install the gem manually.

Plugins are specific to Rails and are similar to gems in that they are also 3rd party libraries. However they are associated with your Rails project as opposed to your machine so they will get posted to the server on a regular deploy.

Freezing a gem is the process of transforming a gem into a plug in. Essen…

Comparing Rails' Active Record Pattern with Phoenix/Elixir/Ecto

Rails has a very well established Active Record pattern for dealing with the database. You have an Active Record model which maps to the database table, the schema of the model comes directly from the database schema and you place your model specific methods on the Active Record model. This file is also where you set your model relationships (e.g. has_many, has_one, belongs_to). Your instance of the model has all the methods built in.

In Ecto/Phoenix it's a little different. First of all, the database schema doesn't automatically map to the "model". In fact we don't really have models (as Elixir is a functional paradigm). What happens in one file in Rails, happens in essentially two (or more). You have a schema file (where you have to list out all the attributes and relationships). Using the schema file, your "instance" is essentially a data structure (with no methods on it). If you want to transform the data on your struct, you would use a context modu…

Unit/Functional Testing RubyAMF

One of my current projects is using RubyAMF to communicate with Flash (http://rubyforge.org/projects/rubyamf/). On the whole this is really nice because it allows you to transfer Ruby objects directly to ActionScript ones (as opposed to translating the object into XML, sending the XML and then recreating the object in ActionScript).
However, Rails does not provide a built in transport mechanism for AMF, so we cannot run functional testing directly on the data call (as we could for an XML or HTML transport layer). This is a show stopper for a lot of people (Rails w/o Unit testing = a big mess of trouble when something goes wrong).
We can though serve both the HTML and the AMF formats depending on the request format. This means that we can test the object instantiation logic and make sure there are no errors in the controllers (though we cannot check the actual format of the data being served). In the controller, instead of rendering AMF alone, do the following respond_to do |format|