not actually Ryan Davis
This is like when you use Google as a spelling corrector. "Oh, you're looking for Ryan Davis? Well, maybe you mean Giles Bowkett!" Or it's like if you search for Target in Google and ads for Wal-Mart show up as well - except Wal-Mart pays for that, and I got this for free. The crazy part is, it might even be fair to say that if Ryan's code was Target, then mine would be Wal-Mart. False modesty aside, it doesn't hurt my …
- Ruby Inside: Google PageRank In Five Lines Of Ruby
- Giles Bowkett: Is That An App In Your Pants Or Are You Just Happy To See Me?
- A Fresh Cup: Double Shot #664
- Giles Bowkett: Another Happy Customer
- ricroberts: Create Your Own Semantic Web-enabled Blog
- MetaSpring Blog: Marketer's Guide to Google Alerts
Well, I'm not quite certain, but I believe ParseTree by Ryan Davis started it
all.
Oh, ParseTree sounds familiar.
It extracts the raw AST that Ruby 1.8 uses internally. It's not very elegant,
so Ryan also wrote UnifiedRuby which cleans it up a bit. RubyParser returns
such a cleanup up Sexp.
And what do people use these cleaned up Sexps for?
There's plenty of projects floating around, here's some I've heard of:
Flog analyzes your …
…hands-down funniest presentation I (or anyone else I spoke with) had ever seen, was co-presented by Ryan Davis and Aaron Patterson. The talk was not about poorly designed or built software, but rather, about software for which the idea or impetus was an "abomination". The talk culminated with a presentation of Phuby on Phails (the ‘ph' is from PHP). Need I say more?
After Hours
Github Meetup
At 9 after the end of the first day of the conference there was …
- Alex Young: Fear and Loathing in JavaScript DSLs
- Scottish Ruby Conference: Call for papers coming soon
- Ruby Best Practices: Fun with Class.new
- Ruby-coloured glasses: Rails underground
- Matthew Bass: Secrets of Nomadic Programming
- Rubycon - All things geared towards web development: Jim Weirich - Test Driven Development meets Design by Contract
Ryan Davis: let's put more words in it
Ryan proposed something totally different: >> words = File.read("/usr/share/dict/words").split; max = words.size => 234936 >> "#{words[rand(max)]}-#{words[rand(max)]}" => "loquat-motorial"
The idea is interesting. You'll need to ensure your dictionary doesn't contain insults, if your user base cares about that :)
Another option Ryan got from Eric is to use the quite unknown bubble-babble …
- Rails Envy » Home: Rails Envy Podcast - Episode #086: 07/08/2009
…average. Teacher Luciano first saw my screencast-talk online, about the translation of Ryan Davis original Hurting Code for Fun and Profit . This "Killing the Average" subject would become the backbone for my next talks. The students from Batatais were really cool, they came to São Paulo to visit Locaweb's facilities and even started their own Rails blog: Batata On Rails .
16/09 - ( PDF ) Now the trip would be to Ribeirão Preto, …
- Litany Against Fear: Professional Ruby Conference Notes
- Rails on the Run - Home: MerbCamp 2008 SanDiego
- Developing with Style: All's Quiet on the Western Front
- Rails on Edge: Been a little while...
- railsexpress.de: Using memcached for Ruby on Rails session storage
- Railscasts: Episode 135: Making a Gem
We've been working a lot of Ryan Davis's ruby_parser project lately. We're actively looking to use that code base as Rubinius' internal parser. This is towards our goal of more Ruby code, but as anyone who's written a parser will tell ya, it can be a real pain.
Ryan has made great progress getting it working and integrating it with Rubinius' Compiler.
Conferences : Wilson Bilkovich was just in Berlin, talking technical about Rubinius at RailsConf Europe…
- Nikos D.: Speed comparison of Ruby 1.8, Ruby 1.9, JRuby and Rubinius using a genetic algorithm
- Programblings: Rubinius for the Layman, Part 1: Rubies All the Way Down
- SD Ruby Podcast: Episode 050: One-man Lightning Talk
- p.latyp.us: Evan Phoenix at acts_as_conference
- starjuice - Home: J2EE Service Wrapper Pattern Candidate
- oldmoe: Ruby Fibers Vs Ruby Threads
After listening to Ryan Davis' inspiring talk, " Hurting Code for Fun & Profit" at GoRuCo today, I wrote this rake task to figure out what code to hurt. It looks though your git log, and takes the 15 .rb files in your Rails' app/ directory and runs them through flog, so you can see which are the most complicated.
RUBY:
namespace :analyze do
namespace :commits do
desc 'Flog the most commonly revised files in the git history'