I understand your motivation, but I think it is showing something that
I would rate as ugly ruby code to the world. If you really want a
string, you could have used to_str.
Please don't feel offended.
No worries. I have thick skin.
I'm not even maintaining a library and
have until now never managed to really develop something test first,
let alone write an article and get it published. I feel that ugly
maybe is a bit too strong a word, but I can't find anything more
subtle.
Inelegant? It's a valid point, but as James Britt points out in a
new (related) thread, it's an fine line between trying to make a
point and striving for elegant code. I'll tell you what, I'd be happy
to take on reviewers for upcoming articles. Contact me offline
if you have an interest in helping refine code or prose.
···
On 5/24/05, Brian Schröder <ruby.brian@gmail.com> wrote:
On 24/05/05, pat eyler <pat.eyler@gmail.com> wrote:
I think it is important to show good ruby style in articles, and
ducktyping is one part of good style.
--
thanks,
-pate
-------------------------
We are often unable to tell people what they need to know, because
they want to know something else, and would therefore only
misunderstand what we said
- the Raven (George MacDonald, Lilith)
My own experience in writing abut Ruby, especially in the common case
where the audience is largely unfamiliar with Ruby, is that practices
and procedures tend to get a bit skewed for reason of discourse.
Code is often not as compact is a it might otherwise be because that
tends to require more background explanation. It's also hard to create
good demo cases, to find the balance between a compelling problem and a
7-page discussion limit.
Has anybody collected tips and guidelines for writing about Ruby? It
would be good to see more Ruby articles in high profile places (i.e.
sites outside the Ruby community circle, or in widely-circulated
magazines such as Linux Journal), but I wonder if people with good ideas
and useful knowledge hold off because they don't know where to start or
how to construct a well-organized, (reasonably) self-contained article.
I'm also very interested in this, as (I think) are several other people. I
don't want to bore the rest of the list though. Would there be any interest
starting a list for Ruby related 'riting where we could collect tips and
guidelines, pass along leads/prospects, etc.?
···
On 5/24/05, James Britt <james_b@neurogami.com> wrote:
James Britt
--
thanks,
-pate
-------------------------
We are often unable to tell people what they need to know, because
they want to know something else, and would therefore only
misunderstand what we said
- the Raven (George MacDonald, Lilith)
I'm also very interested in this, as (I think) are several other people. I don't want to bore the rest of the list though. Would there be any interest
starting a list for Ruby related 'riting where we could collect tips and guidelines, pass along leads/prospects, etc.?
is'nt this the maybe this is something that should go into the "Why Ruby" stuff[1]?
On 5/24/05, James Britt <james_b@neurogami.com> wrote:
Has anybody collected tips and guidelines for writing about Ruby? It
would be good to see more Ruby articles in high profile places (i.e.
sites outside the Ruby community circle, or in widely-circulated
magazines such as Linux Journal), but I wonder if people with good ideas
and useful knowledge hold off because they don't know where to start or
how to construct a well-organized, (reasonably) self-contained article.
I'm also very interested in this, as (I think) are several other people. I don't want to bore the rest of the list though. Would there be any interest
starting a list for Ruby related 'riting where we could collect tips and guidelines, pass along leads/prospects, etc.?
