The BYU Ruby Users Group will be holding its February meeting
on Wednesday the 8th at 7PM. We're meeting in room 120 of the
Talmage Math & Computer Building (TMCB) -- see
http://map.byu.edu/Map.html for a map of campus if you need it.

Eric Hodel is making a trip in from Seattle to talk about all
kinds of deep Ruby things. He is a former presenter at RubyConf
(RubyConf 2003 "Working in the Garden: Web Apps with Borges" and
2005 "Reimplementing Ruby"), and has his hands in a number of
exciting Ruby (and Rails) projects: ZenTest, Ruby2C, ruby-growl,
ParseTree, Borges, and the Rails Log Analyzer. He currently
works for the Robot Co-op, helping build 43 Things.

Eric was recently mentioned in Bruce Eckel's blog
(http://www.artima.com/weblogs/viewpost.jsp?thread=146091). Bruce
said that Eric has "done some very immersive work with the language.
[He] live[s] and breathe[s] this stuff, which is exactly what I
needed to get some actual insights into Ruby."

This should be an awesome meeting for those who want to get a better
handle on Ruby, whether you're a long time hacker, or just looking
into the language.

----------------Special Thanks--------------------------
We'd like to thank Sleep Inn of Provo, who've graciously sponsored
this meeting, and are providing accomodations for Eric on the night of
the meeting.



--
thanks,
-pate
-------------------------
_______________________________________________
UTOSC mailing list
[EMAIL PROTECTED]
http://plug.org/mailman/listinfo/utosc


-- 
Topher Fischer
System Administrator - TMCB 1140
GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19  EFF5 2FC3 BE99 D123 6674
[EMAIL PROTECTED]

Attachment: signature.asc
Description: OpenPGP digital signature

--------------------
BYU Unix Users Group 
http://uug.byu.edu/ 

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to