Dump or Slurp YAML Reference Data (and Fixtures) | Ruby on Rails for Newbies

Sometimes you need to save data and use it again when you deploy a server or continue a project on a different machine.I wrote a plugin for ActiveRecord that lets you do this easily.

Just make sure that the first thing you try is “User.dump_to_file”. I used the “User.to_fixture” first, then I tried the “User.load_from_file”. And I got a nice users fixture file (which wiped out my existing fixture file without asking), and then…

This article is entertaining… and frightening in it’s own way.

Hacknot – The A to Z of Programmer Predilictions

Sometimes I fancy that I have met them all. There will be no new developers for me to work with in future – only the reanimated ghosts of projects past. The same quirks and foibles that I’ve endured in the past will haunt me the rest of my days.

I recognized all too many of these characters. You will, too. It is sad, however, that there was only one female in the entire bunch. Really. I know that there are a lot more male programmers, but < 4% female? Come on. Get real.

For years, I’ve been diligently erasing all traces of pre- and post-fix naming conventions from the source code under my control. I’ve always hated it. The argument I most commonly make for this is that, IMO, it makes the code less readable. Now, in a happy coincidence, I have been reminded about this topic, when I have actual proof to point at to back it up.

Now, “readable” is a very subjective term. Some people would insist that the prefix “m_” provides additional semantic meaning to the field, telling you that you are dealing with a class field instead of a parameter or local variable. In Java, so does “this.”. Others would add tags like “str” to the beginnings of every String field name. Again, yes, it adds semantic meaning, but any decent IDE will provide the same information in several different forms (tooltips, find definition, etc) without the extra baggage.

So, what about this proof? Consider the following:

Aoccdrnig to rsaerech, it dseon’t mttear in waht odrer the ltteers in a wrod are, the olny iroptmant tihng is taht the fsirt and lsat lteetr be at the rghit pclae. The rset can be a taottl mses and you can sitll raed it wouthit any perbolms.

Now, I hope you see where I am going. The real problem with all these pre- and post-fix notations is that they screw up that first/last letter recognition that seems to be hard-wired into readers of the English language, mostly because of some redundancy features of English. (See the links at the bottom of this post for more information about this.) So, there you have it. Proof that readability in your code is diminished by the use of pre- and post-fix naming conventions.

So let’s all get out there and start improving the readability of our code. JBuilder has some nice Rename Refactorings to help. ;-)

References Comments from a researcher at Cambridge A letter purportedly from the original researcher of the topic

And thanks to Anders for the inspiration from his new CafePress shop.