Liberia (80%)
Zimbabwe (70%)
East Timor (50%)
Bosnia (40%)
http://www.aneki.com/unemployment.html
Graduates in any of those countries would gladly swap places with you.
102 karma · joined January 10, 2009
Liberia (80%)
Zimbabwe (70%)
East Timor (50%)
Bosnia (40%)
http://www.aneki.com/unemployment.html
Graduates in any of those countries would gladly swap places with you.
Sounds familiar.
I recommend watching it. Good talk. Takeaway point - always err on the side of charging too much :)
for x in 1..10; print x end
1.upto(10).each{|x| print x}
I'm curious - how would you print 1 through 10 in C# 3 by comparison?
Do you mean for the core language? Are you not happy with http://www.ruby-doc.org/ ?
I agree with you about Thought-to-Code and even though I argued in favor of monkey patching earlier, the willingness to use it without discipline has raised a red flag for me and is the biggest sign of this "too cleverness" that you're referring to (at least for me). If Ruby becomes the new Java, maintaining irresponsibly monkey patched legacy systems could be a nightmare for the enterprise developer in the years to come.
Is it more the fact that the community is small or that fewer people share their code than in the Python community? Just wondering.
As for monkey patching, yes, it's ill-advised in general just as global scope and gotos are ill-advised for similar reasons. However, monkey patching is a powerful feature if used responsibly as Chad Fowler has noted ("The Virtues of Monkey Patching"):
http://chadfowler.com/index.cgi/Computing/Programming/Ruby/T...
Now admittedly, not every programmer is as competent or responsible as Chad Fowler or the programming world would be a very different place but the point is there's a right way and a wrong way to do it.
Werner Schuster's article on InfoQ ("Ruby's Open Classes - Or: How Not To Patch Like A Monkey") has more good advice on how to do it the right way:
http://www.infoq.com/articles/ruby-open-classes-monkeypatchi...