Matz comments: Otaku, Cedric’s weblog: Flaws in Ruby
Finally, I am not against “method overloading”, but it very easily leads to optional static typing in the language, which changes the language
very drastically, since you need to specify “type” to overload
arguments. Without well-thought design, it can “destroy” the language
and its culture. I have not yet got that well-thought design of
method overloading
Typography - Hypnerotomachia Poliphili
Scholars find that the greatest artistic merit of the book is neither in typography or woodcuts separately, but in the overall composition of text and image into a harmonious whole, which allows the eye to slip back and forth from textual description and corresponding visual representation with the greatest of ease – a rarity even today
Actually, the best way to do this is to put test root in your load path.$LOAD_PATH << File.dirname(__FILE__) + ‘/../’ require ‘lib/variables’The problem with Keith’s solution is that you’ll end up requiring the same file from different tests via different paths. The semantics of require is that it won’t load a library if it has already been loaded, but if you are loading the same file but using a different path in your require statement, require will think it is a different library and load it again.
I am wondering if a better thing would be to unshift the path so it’s first in the stack like this:
$LOAD_PATH.unshift(File.dirname(__FILE__) + '/../')require ‘lib/variables’
Would it be a bit better? Would it cause problems if you are use other require for ‘test/unit’ etc…? Ideas?
from Brian Marick - Everyday Scripting with Ruby
What I tell people on my consulting trips is that every week you spend
at your job should make you worth at least a little more money. Make
a habit of asking yourself whether that has been true of the past week.
Some fraction of scripters fall into the opposite trap: they get so enthralled
with scripting that they build elaborate, gorgeous (to them, at least)
frameworks far in excess of what their job demands. The trick in scripting
is to push yourself beyond the minimum while still regularly producing
results that justify your salary. To do that, you have to grow
your scripts bit by bit, satisfying one real and immediate need after
another, while still keeping the code clean. This book won’t surgically
implant that skill in your skull, but it’s given you some of the tools you
need.(emphasis mine)
This Open Source stuff is free. But it’s free like a puppy. It takes years of care and feeding. You don’t get to criticise a free puppy that you bring in to your home.
Merging conflicts by hand can be quite intimidating the first time you attempt it, but with a little practice, it can become as easy as falling off a bike.