Start writing an application to scratch some of your own itches (merb
tutorials website, for instance) instead of asking for "best
tutorials" on the mailing list.
You get better not when magic fairies come to give you "best IDE" and
"best tutorials" but when you read code and do actual work.
--
MK
The best way to learn is to try to teach.
I constantly see people moaning about tutorials, blah blah blah. You
have source, Merb is about 6K LOC,
merb is very similar to Rails in many aspects, Merb is a damn *small
web framework in Ruby*,
not an enterprise grade natural language processing system in C++.
If you want to learn it, it's usually more useful to start reading
sources and writing yourself a notes instead of asking people
for tutorials, best IDEs and building yourself a castle in the air.
IDEs and tutorials do not matter for learning at all, pick a simple
test editor and stop wasting your time on mailing lists.
> I am a fresh guy and yet not matured enough
Here you try to make a self-excuse. "I am weak, I am a fresh guy... I
need your help". You don't need any help from others.
Dig into source, write the best Merb tutorial out there, become a way
more skillful than Merb core team members (if you think me or Matt or
Yehuda or Dan are god likes, I have to disappoint you: we are mere
mortals just like you), then
apply your skills to change the world, become rich, famous or whatever
your dream is.
All I see now from you on the mailing list is constant asking for
things others should do for you: whether it is a NetBeans Merb module,
tutorials or something else. Dude, world around you changes when you
step up and write a NetBeans Merb module the world is lacking right
now,
or when you spend a week digging in the source to write a tutorial for
your friends, or when you submit a patch instead of calling Merb
contributors names.
It *is* that easy.
--
MK
I want merb to save me from headaches I had with existing tools in the
Ruby world. I want it to be something Ruby community would not have
otherwise.
I don't care how popular it is, I don't feel for *software engineers*
who cannot figure out how a Ruby web framework of reasonable size
works. Merb is not rocket science, period.
I was honest with you. Now please don't tell me about why Rails is
popular, why something else is popular and how much of an asshole I
am. Use Merb if it fits your needs, make it better, help newbies if
you want to, pitch Merb to whoever you want. Just ignore me. I am an
idealistic asshole who thinks that 6K LOC in Ruby is not that scary
and people could do better scratching their own itches.
--
MK
It does, you did not try (yet).
--
MK
I know everyone is sick of me here, but learning languages is a
perfect example of how people really learn and accomplish something.
Keep in mind learning a programming languages usually 1000 times
easier thing to do compared to natural languages.
I study Italian. I have no idea why, I just like learning languages.
How I do it, you ask? I listen to some radio shows in Italian,
understand nothing,
read a few lessons in a textbook, next day I listen to it again. After
a week I started to understand certain sentences. I feel myself
extremely stupid every time I listen to the program. But I also
understand that if I get all the fancy language coursed you can find
today,
if I start studying with the best teachers I can find in my area, but
then *do not really push hard enough*, I won't learn a thing. So fancy
text books and other fancy things are ignored intentionally.
In contrast, if I continue using one textbook and listen to the same
radio show for months and months, one day I'll be understanding it
all. Key word here is *listen for months and months*, *doing*, this is
what most people do not do. Instead, they build themselves a castle in
the air, trying to imagine how *awesome* they will be if they ask
"senior people" and get all the fancy IDEs/textbooks/etc. They collect
gazillions of books and links they never read, install 20 IDEs they
never use, try to follow "best git workflows" and "best git practices"
where Mercurial with a single branch will do, and so forth.
Don't do it. Don't fool yourself.
So if you ask my heart advice without bitching about newbies, here it
goes. Forget about fancy IDEs, "best tutorials", "best operating
system to develop on". Pick first text editor you can find (on Linux
and Mac I'd recommend Vim since it's there by default, and I am a die
hard Emacs junkie: it does not matter when you learn), imagine what
would be a fun thing to do for you and get lost. Never come back to
any mailing lists until your goal is completed and you are ready to
share your experience with others.
This is how Merb, Mongrel and a lot of other projects started.
--
MK
(1) Best IDE currently available for Merb. This is important since Netbeans is currently working on Merb support for future.
(2) Best tutorials and slides to read ( Links are requested )
(3) Good Beginners projects available on GitHub to start with.
(4) A tutorial on working with Merb and console.
(5) Some Good Tips and links to visit frequently for learning more.
If someone starting with Merb needs a few ideas what to work on,
people often ask me why Merb wiki is not written in Merb.
And though I do not care what it is written in, Collective could be
improved. Grab the source at github [1], see what moinmoin [2] can do,
clone it's Mercurial repository [3]
to see how they organize domain model (no need to read through all of
Python code there, just figure out what their models are), then start
working on Collective.
And of course if some specific question arises ("I try to do a diff
between two versions, how would you do it?"), I am sure people on this
list will be glad help you.
[1] git clone git://github.com/meekish/collective.git
[2] http://moinmoin.wikiwikiweb.de
[3] hg clone http://hg.moinmo.in/moin/1.9 moin-1.9
--
MK
My take, FWIW, is as follows:
* Different resources help folks to learn in different ways.
Reading a book is very different from watching a screencast.
Both are different from reading and/or writing code. I use
ALL of these techniques (rinse, repeat :-) as I progress.
* There is NO substitute for getting your hands into the code.
I know; it's scary. But at some point, you have to jump on
the bicycle, fall off, and try again. Accept your scrapes
and bruises as badges of honor.
* Merb is currently a moving target, though the 1.0 "line in
the sand" will be an enormous help. Expect rapid changes
over (at least) the coming year. Expect Merbists to find
and/or build several new plugins, slices, tools, etc.
I'm pretty comfortable (though not all that happy :-) with Rails,
so my approach has been to compare Merb to Rails. What parts are
different? How does this affect the way I'd do things. Etc.
Finally, I try not to get too upset by either nattering newbies
or gratuitous grumps. I play both roles myself, at times, so
I'd best be tolerant of the behavior in others.
-r
--
http://www.cfcl.com/rdm Rich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http://www.cfcl.com/rdm/weblog +1 650-873-7841
Technical editing and writing, programming, and web development