Hey guys, I'm sorry I wasn't here earlier in this conversation. We absolutely need tutorials, examples, etc. At the moment, we're pretty thin on a lot of what you're asking for, but let me see if I can answer some of your initial questions:
(1) Best IDE currently available for Merb. This is important since Netbeans > is currently working on Merb support for future. At the moment, pretty much any IDE available with Ruby support will also support Merb. This includes NetBeans, IntelliJ, Aptana, etc. However, no editor except Textmate currently has Merb-specific features. A lot of Ruby developers find Textmate to be a perfect compromise between a raw text editor and a full-fledged IDE; obviously, your mileage may vary. I'd definitely keep an eye on NetBeans :) > (2) Best tutorials and slides to read ( Links are requested ) The videos for all of MerbCamp are available: http://www.merbcamp.com/video. The getting up and running talk is a bit outdated (it actually was outdated even when he gave it), but there are some very good tutorials on the wiki under "How to": http://wiki.merbivore.com/. > (3) Good Beginners projects available on GitHub to start with. One of the best examples I've seen so far is http://github.com/nanodeath/merb_example_google_rss/tree/master, an example app that takes in a Google search and outputs an RSS feed using Haml. > (4) A tutorial on working with Merb and console. Hmmm... I don't know if we have anything like that. What specifically are you looking for? > (5) Some Good Tips and links to visit frequently for learning more. I'd keep an eye on the Merbist (http://merbist.com) and my blog ( http://www.yehudakatz.com). You can also check out http://planet.merbivore.com/, which aggregates the blogs of some of the top merbivores around. And of course, keep an eye on the wiki! Regarding Michael's comments, I'd say his suggestions are more appropriate for people wanting tips on how to become a kick-ass programmer in the abstract. The only way to become legendary is to write an application that scratches your own itch and push the boundaries of your existing skills. I always say, "look for a project that seems out-of-reach impossible, then do that." But you obviously can't get to that point before you get up and running; I hope I've been somewhat helpful on that front. I remember when I first started with Rails, and I wasn't very sympathetic to people who told me to stop whining and buck it up, so I can imagine that you feel the same way. Again, hope that my answers have been helpful :) -- Yehuda On Fri, Nov 21, 2008 at 7:56 AM, Michael Klishin < [EMAIL PROTECTED]> wrote: > > 2008/11/21 Julian Leviston <[EMAIL PROTECTED]>: > > If you want to learn Japanese, you can do courses, and you can ask > > people (in English) how to talk in Japanese, but it's not going to > > help you one WHIT at actually having functional skill in the language. > > > > To learn the language, you have to TRY TO USE IT. > > 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 > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
