The Ruby Reflector

bq. " Hmm... but will MySQL scale to 1,000,000 records?"

Looking back on these internal conversations I find them funny; programmers always tend to think big. However, these are real concerns that developers and teams think about. While planning I would constantly consult the blogosphere for help, and to see what others were doing. Kirk Haines of Engine Yard wrote a great series of NoSQL posts highlighting and comparing different key-value stores and explaining …

• Topics: Redis, MySQL, user.id, NoSQL, Ruby on Rails
• paperplanes: When To Redis
• GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS: Redis: Data Cheeseburgers
• Jake Scruggs: Rails Conf 2010 Day 2
• Scout ~ The Blog: Three reasons for Resque (and a Scout Plugin)
• Running & Coding: LOOP CHAT!
• a work on process: Weekend Links

Hmm...that is not what we expected, right? We expected that when we clone the first options hash and modify the clone that it would not modify the original. The issue is that some things in Ruby do not get cloned when stored in other objects and one of those things is hashes. To do this right, we need to define initialize_copy for the options hash and tell it to fully clone the source hash when cloning the options hash like so: class OptionsHash def initialize_copy(other) super @ source…

• Topics: Mongo, MongoMapper, Ah, Ruby, Hmm.

Hmm. Interesting. Is there a down side? How do I do this?

People say that remote research is inexpensive, it's great for cross-country teams, and you get a lot of data without leaving your office. But wait, what are the downsides? How is something like this setup?

In a 25 minute interactive discussion Nate will share:

When we should & shouldn't go remote

How to create tasks for participants

How to find participants

How to handle problem participants

Best ways to gather …

• Topics: Nate, 12:00-1:00pm, RSVP, List, n.
• Developing with Style: Cake Nibbles #3
• Signal vs. Noise: QUOTE: Nate Kaiser recently said on Twitter, "If I
• MetaSpring Blog: The Panel Agrees: SEO & SEM Are Growing
• The Queue Blog: Link dump for May 25th

…accurate image would be someone who stares quietly into space for a few minutes and then says " Hmm. I think I've seen something like this before."

Learn to Let Go: How Success Killed Duke Nukem

It's a dilemma all artists confront, of course. When do you stop creating and send your work out to face the public? Plenty of Hollywood directors have delayed for months, dithering in the editing room. But in videogames, the problem is particularly acute, because …

• Topics: Ruby on Rails, JavaScript, Mongo, MySQL, GitHub
• alexjsharp.com - Home: Continuous Integration Installation Gotchas
• Too-biased - Home: Clarity in log files.
• Litany Against Fear: Load Rails conditionally with Rack
• Tom Ward: A rails template for gem bundler
• High Scalability: Hot Holiday Scalability Links for 2009
• A Fresh Cup: Double Shot #562

Hmm.... what to do for the next two hours?? #

RT @ conikeec: BREAKING NEWS: Comcast Buys NBC http://www.businessinsider.com/comcast-buying-nbc-is-done-2009-12 #

I, apparently, have 16 Google Wave invitations. Who needs one? #

I also, apparently, have google voice invites. Any takers? #

I still have plenty of google wave invites if anybody wants one. #

http://tweetphoto.com/5707075 I wonder if these are any good? …

• Topics: RT, Ruby on Rails, Brazil, Senate, Dylan

…unexpectedly error: failed to push some refs to ' <repo here> ' < / repo > Hmm. This has always worked for me before, what gives?

When I took a look at my remote branches: 20 : 35 : 33 > git branch - r origin / master I noticed that there's no HEAD pointer. I'm actually not certain of how that came about, but let's add it:

git symbolic - ref refs / remotes / origin / HEAD refs / remotes / origin / master Now this looks a little better: 20 : …

• Topics: Hmm.
• Nikos D.: Tiny (but maybe important) Rubinius tidbits
• Viget Extend : The Development Lab: Using ruby-debug to Find Those Hard-To-Reach Places (bugs)
• Pathfinder Development: A Pair of Kings Beats A Single Ace: Pair Programming, Agile Rails, and You

…ASC" end

Calling: Order.by_delivery.by_creation

Would produce: SELECT * FROM "orders" ORDER BY delivery_date DESC

Hmm...

In the end, the issue was a bug in Rails itself, but this process allowed me to gain a better understanding of how the tools and libraries I use interact with one another. Try giving ruby-debug a whirl in your next project.

Here is a link to the Rails Lighthouse ticket describing this bug.

• Topics: Ruby on Rails, Hmm., mysql, Web Developer, Ahh
• Andrzej on Software: A Guide to Deploying Rails Applications
• amazing development: Chumby goes i18n - soon available outside US?
• Mental Paging Space: Call Center Voice Recording
• i am ruinous: "Downturn" spelled backwards is "Opportunity"
• Alexey Kovyrin's Blog: Loops plugin for rails and merb released
• I was just thinkin'...: Rails Bugmash August 2009: Before, During & After

Hmm... A lot of challenges, not much guidance. Which matches my feelings. When put in the right context, pairing is fantastic. But the context can be elusive, even for people with the best of intentions and talent.

Would this have been a better blog post if I had paired with a co-worker?

Pathfinder is a software development firm. Hire us to build complex software that's easy to use.

A Pair of Kings Beats A Single Ace: Pair Programming, Agile Rails, and You

• Topics: XP, Mike Gunderloy, Hashrocket, Pair Programming, TDD
• Pathfinder Development: Pair Programming in the New York Times
• Pathfinder Development: Pair Programming: Lone Programmer Shoots Back
• Litany Against Fear: Defraggle Rock
• Internaut Design - Home: Scrum is Everywhere
• Programblings: Mat mini
• Giles Bowkett: One Reason Pair Programming Is Not For The Elite