Stop developing Rails !!!

It is really hard to find the right path. For me that I am coming from
the ASP Classic world it is even harder - because I think in a total
different way.

I think this is probably the most insightful point... Rails is an extraction of ideas and what DHH (and many others) consider to be best practices. So for many of us, it is easy to find the answers, because we already think that way. I've rarely had any problem finding what I need, and IRC usually provides the rest. But just before rails came about, I already was looking for ways to do things this way; rails just did it first and better. :slight_smile:

I even couldnt find the ".blank?" thing and what it does. Its not avail.

IIRC, blank? was added in recent edge rails, so if you are using the stable release, it may not be there. Same caveat if you have bought the beta version of "Agile Programming with Rails". I wonder if some of the forum and wiki pages also suffer from this. People need to be clear what version they are using; due to the incredibly fast pace of development, I suspect a lot of people are using edge rails.

- because the modell behavior is really great but the way is hard. Also
in the Agile Web development book are "MANY" bugs - which doesnt make it
easier.

Again, what version of rails and what version of that book?

I am sitting here since 2 Weeks and coding my first app with rails but
most of the code is from the forum - and some code I dont even know what
it is doing.

On the plus side: Its getting better every day.

As I said before, I think the biggest issue is learning to think in a different way. It's sorta like the transition from being a procedural programmer to a OO programmer.

David Morton
Maia Mailguard http://www.maiamailguard.com
mortonda@dgrmm.net

Hello David,

> I even couldnt find the ".blank?" thing and what it does. Its not
> avail.

IIRC, blank? was added in recent edge rails, so if you are using the
stable release, it may not be there.

#blank? is in ActiveSupport since 1.2.1, so it's in Rails since 0.14.1.

    -- Jean-François.

David Morton wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>
> It is really hard to find the right path. For me that I am coming from
> the ASP Classic world it is even harder - because I think in a total
> different way.
>

I think this is probably the most insightful point... Rails is an
extraction of ideas and what DHH (and many others) consider to be
best practices. So for many of us, it is easy to find the answers,
because we already think that way. I've rarely had any problem
finding what I need, and IRC usually provides the rest. But just
before rails came about, I already was looking for ways to do things
this way; rails just did it first and better. :slight_smile:

> I even couldnt find the ".blank?" thing and what it does. Its not
> avail.

IIRC, blank? was added in recent edge rails, so if you are using the
stable release, it may not be there. Same caveat if you have bought
the beta version of "Agile Programming with Rails". I wonder if
some of the forum and wiki pages also suffer from this. People need
to be clear what version they are using; due to the incredibly fast
pace of development, I suspect a lot of people are using edge rails.

> - because the modell behavior is really great but the way is hard.
> Also
> in the Agile Web development book are "MANY" bugs - which doesnt
> make it
> easier.
>

Again, what version of rails and what version of that book?

> I am sitting here since 2 Weeks and coding my first app with rails but
> most of the code is from the forum - and some code I dont even know
> what
> it is doing.
>
> On the plus side: Its getting better every day.

As I said before, I think the biggest issue is learning to think in a
different way. It's sorta like the transition from being a procedural
programmer to a OO programmer.

David Morton
Maia Mailguard http://www.maiamailguard.com
mortonda@dgrmm.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFT2DBUy30ODPkzl0RAs4iAKDQGbvCcspUGQwBeU4yqStCqlvTbgCfbnLh
OR+ijMbP6lxM/8fA/ajYIvo=
=QERo
-----END PGP SIGNATURE-----

The problems with documentation are not new, in fact some people are
actually trying to do something about it by hiring a professional to
spend some quality time with the docs.

http://blog.caboo.se/pages/documentation_drive

_Kevin

From: David Morton <mortonda@dgrmm.net>

It is really hard to find the right path. For me that I am coming from
the ASP Classic world it is even harder - because I think in a total
different way.

I think this is probably the most insightful point...

I agree - coming from the Java world, it took me a while to understand some
of the philosophy behind ROR. It was almost a month before I realized I
didn't have to download gems before installing. It took me longer to
understand the philosophy behind Java. Although I have dozens of books on
Java, the ones I have on Ruby and Rails are as good as any on Java.

My thanks goes out to the people who have worked on the documentation -
excellent job. While there is always room for improvement, I have found all
the answers I've needed in my 2 months of using ruby and rails every day -
until today, hence my first post to the mailing list.

I look forward to the day I can contribute to both the code and the
documentation. Perhaps I can help with the overviews soon.

Ric Turley

Rdoc does an amazing job of self documenting uncommented code

No other languages core documentation even comes close to facilitating that

here:
http://rubyonrails.org/docs
http://www.ruby-doc.org/core
http://www.ruby-doc.org/stdlib

That said rails has some fragmentation issues in this area.

I usually come across these when looking for examples and tutorials for
plugins and gems.

I guess I could generate the documentation for the plugins myself but im
lazy