Developer Paradox
Wanting to try new languages and frameworks, but only really ever spending time updating packages, frameworks, and tools, leaving little time to write code.
Clever Algorithms
A FREE pdf describing 45 different artificial intelligence algorithms in Ruby. Great read!
From a bit to a few hundred megabytes, from a microsecond to a half an hour of computing confronts us with completely baffling ratio of 109! The programmer is in the unique position that his is the only discipline and profession in which such a gigantic ratio, which totally baffles our imagination, has to be bridged by a single technology. He has to be able to think in terms of conceptual hierarchies that are much deeper than a single mind ever needed to face before.
Source: axisofeval.blogspot.com
Rails Routes
WARNING: Geek Post
In the Rails world, you have these things called resource routes…
http://api.rubyonrails.org/classes/ActionController/Resources.html
You can define how the url gets translated into which controller and action, based on REST principles, thin controllers, and fat data models.
Image, if you will, you see this in your routes file:
This already describes a lot about your application:
- There will be a /users path
- You will have a User model
- The user has a shopping cart, many favorites, a profile, and friends. Each with their own matching model.
Granted, I could have done this too:
But like I said, it describes a lot about the application your building…
Arguably enough to be able to generate: controllers, actions, views, models, and basic functional tests… The only thing it doesn’t describe is the fields you’re collecting about each object.
So my question becomes: If Rails is all about RESTful resources, why don’t we focus on simple generation of an application based on the routes.rb file. Since the HTTP Verb and the Resource URL are important and the routes.rb describes those two, why not start there?
So, from a compliance and risk management perspective, we recommend that you do not store sensitive credit card payment information in our EC2/S3 system because it is not inherently PCI level 1 compliant.
I'm a Ruby developer that loves to play with science, math, and gadgets. Previously, I was part of a startup called drop.io, acquired by Facebook. I live in Fort Worth, TX with my wife, 2 dogs, and baby boy. I'm a foodie, a gamer, and a self proclaimed scientist.
