‹prev | My Chain | next›
I finally decided what my chain should be.
"Don't break the chain", in case you are not already aware, is a motivational tool attributed to Jerry Seinfeld. The concept is that every day you produce something related to your craft. Each day you do this, you put an "X" through the day. After a little while, you have a chain of X's and you begin to be offended at the idea of breaking the chain.
The end result is not the chain. Rather it is the skills acquired and honed by building up that chain.
Jerry's craft is comedy. Mine is software development.
I have decided that my chain is going to be converting my personal site (EEE Cooks) from Rails 2.0 to something running on CouchDB.
Moreover the X's are not going to be on a calendar that only I can see, but they will be on this blog. Every day until I have EEE Cooks running on CouchDB in production, I will blog about my latest experience in the effort.
The point is not to make EEE Cooks better than it already is. The point is an excuse to practice my craft. And to become a better blogger while I'm at it.
skip to main |
skip to sidebar
About Me
- Chris Strom
- Baltimore
- Reformed perl hacker, willing rubyist. Big into chains.
Blog Archive
-
▼
2009
(245)
-
►
October
(17)
- "Newbie" Feedback
- Smoke 'em If You Got 'em
- A Slight Rewrite
- Regression Testing
- 404 in Sinatra
- Deploying ImageScience to Debian
- Rack::ThumbNailer
- Rack Middleware: Driven Almost to Completion
- Can't Stub Rack
- Two More Examples to Drive Rack Middleware
- Describing Rack with BDD
- Rack Image Science: A Spike
- Unsuccessful Image Science
- Two More Features Deployed
- Cucumber Driven Development with CouchDB
- Inside Out Ingredients
- Ingredients, in Batches
-
►
September
(30)
- Outside-In Ingredients
- The Ingredient Index Feature
- Prototyping CouchDB Views (Take 2)
- A Poor Man's CMS on CouchDB
- CouchDB is not a CMS
- Rack Caching: No Longer Just a Proof of Concept
- Full Stack ETag Support
- Rack::Cache
- Minor Details, The End?
- No Hard Breaks
- Ingredients, with Style
- Pretty Floats
- Minor Details, Part 1
- Deploying the Latest
- Alternative Seeds, Seeds for Replacements
- Last Feature Complete
- The Last Helper
- Alternate Preparations Helper
- Prototyping Alternatives
- Holy Crap
- Excluding couchdb-lucene Documents (or trying to)
- Enjoying Cucumber
- Recipe Update Grits
- Pizza Dough is Tough to Get Right
- Learning the New Feature
- Outdated Recipes
- Always Check Boundary Conditions, You Dumb Ass
- A Stylin' Mini-Calendar
- Slow, Slow, Slow... Done!
- Links Between Mini-Months
-
▼
March
(35)
- Accessing Sinatra Helper Methods in View Specs
- Implementing Recipe Details, Part 2
- Finishing Working Inside the Recipe Details, Movin...
- Inside with View Specs
- RSpec with Sinatra & HAML
- Oragnization for RSpec, HAML, and Sinatra
- RSpec with Sinatra & CouchDB
- Implementing Recipe Details, Part 1
- Proper Cucumber Sinatra Driving
- First Steps Toward Implementation
- Recipe Search Feature
- VPS Notes
- Full Text Indexing of CouchDB with Lucene
- Yak Shaving is the new Dependency Hell
- Benchmarking
- Complete Recipe Upload to CouchDB
- Recipe.to_json
- Running Old Code
- Backing Up PostgreSQL
- First Draft: Recipe Feature "Story"
- Cucumber, Merb and CouchDB - Win (Finally)
- Cucumber, Merb and CouchDB - Getting Closer
- Merb + CouchDB Does Work After All
- Merb It Is, Then
- Bleeding Edge Rails
- Spike Edge
- Cleaning up the Spike
- Test CouchDB Database with Cucumber and Sinatra
- Finishing the Cucumber and Sinatra Spike
- Spike Cucumber and Sinatra
- Spike Sinatra and CouchDB
- First Draft: Meal Feature Story
- Source Code Management
- Technical Requirements
- My Chain
-
►
October
(17)
5 comments:
We are watching. Do not disappoint. :)
Sounds cool. What do you mean by "something"?
Jeff, thanks. Nothing like making a big, bold proclamation in a public place to give you motivation. If you ever think of doing something like this, late at night, right before you go to bed is great. Don't save as draft otherwise you'll likely never follow through :)
pjb3, "produce something" means to document a step that I have taken that day to move toward my goal: could be as big as deployed beta code, could be as little as wrote a spec. "something running on CouchDB" means that I am not making a decision on the framework yet (though it'll be a ruby framework).
Finally came up with a chain of my own (since I see you've been doing very well with yours): http://forthright.plainlystated.com/2009/05/blog-post.html
Post a Comment