How about a fork of exception_notifier to notify via IM using XMPP4R? That way you can get instant notification when your rails app is going weird - better to fix it before anyone notices. I was going to do this the other day and rand out of time.
Guys, I am new to Ruby and was earlier doing programing in .NET for 5 yrs and was in colorado and just recently moved to Boston. I am catching up with Ruby(and RoR) and the question I have is: Will I get any benefit from attending these Tuesdays weekly meetings as I am relatively new or should I wait till I get myself comfortable with these technologies(Ruby and Rails) and then start attending these meetings so that I can contribute in whatever way i can and also learn from you experienced guys. Please go ahead and suggest if you have something else to share/suggest on this case as ultimate motive is to learn and become a good solid rockstar programmer like you guys:)
Thank-you in advance! Mehnaz Singh
David J Berube <djber...@berubeconsulting.com> wrote:
How about a fork of exception_notifier to notify via IM using XMPP4R? That way you can get instant notification when your rails app is going weird - better to fix it before anyone notices. I was going to do this the other day and rand out of time.
I just moved here a month ago myself. I haven't been able to make it to a Hackfest yet, but after being at the recent meeting, I can definitively say that the Boston Ruby Group covers the gamete as far as experience level goes. I'd wager there's a lot to be gained by going, and you'll probably run into at least a few other people at your experience level.
> Guys, > I am new to Ruby and was earlier doing programing in .NET for 5 yrs > and was in colorado and just recently moved to Boston. I am catching > up with Ruby(and RoR) and the question I have is: > Will I get any benefit from attending these Tuesdays weekly meetings > as I am relatively new or should I wait till I get myself > comfortable with these technologies(Ruby and Rails) and then start > attending these meetings so that I can contribute in whatever way i > can and also learn from you experienced guys. > Please go ahead and suggest if you have something else to share/ > suggest on this case as ultimate motive is to learn and become a > good solid rockstar programmer like you guys:)
> Thank-you in advance! > Mehnaz Singh
> David J Berube <djber...@berubeconsulting.com> wrote:
> How about a fork of exception_notifier to notify via IM using XMPP4R? > That way you can get instant notification when your rails app is going > weird - better to fix it before anyone notices. I was going to do this > the other day and rand out of time.
> Guys,
> I am new to Ruby and was earlier doing programing in .NET for 5 yrs and was in colorado and just recently moved to Boston. I am catching up with Ruby(and RoR) and the question I have is:
> Will I get any benefit from attending these Tuesdays weekly meetings as I am relatively new or should I wait till I get myself comfortable with these technologies(Ruby and Rails) and then start attending these meetings so that I can contribute in whatever way i can and also learn from you experienced guys.
> Please go ahead and suggest if you have something else to share/suggest on this case as ultimate motive is to learn and become a good solid rockstar programmer like you guys:)
> All experience levels are welcome and can benefit from the Boston Ruby
> Group meetings and hackfests.
> For tomorrow night, how about something Merb-related to get fired up
> for Ezra's visit next week?
> Dan
> On Apr 14, 11:51 am, mehnaz jaggi <msja...@yahoo.com> wrote:> Guys,
> > I am new to Ruby and was earlier doing programing in .NET for 5 yrs and was in colorado and just recently moved to Boston. I am catching up with Ruby(and RoR) and the question I have is:
> > Will I get any benefit from attending these Tuesdays weekly meetings as I am relatively new or should I wait till I get myself comfortable with these technologies(Ruby and Rails) and then start attending these meetings so that I can contribute in whatever way i can and also learn from you experienced guys.
> > Please go ahead and suggest if you have something else to share/suggest on this case as ultimate motive is to learn and become a good solid rockstar programmer like you guys:)
I'm sure we all have passing familiarity with the 'rails' command to
generate an initial rails app.
After you do enough of them, you tend to fall into some patterns. Like
removing comments from config/environment.rb, adding certain plugins,
and so on.
Wouldn't it be nice if you could setup a template for later reuse?
Turns out the 'rails' command internally is just using a generator,
just like anything you'd do with script/generate.
You can create your own generators in ~/.rails/generators, or they can
come from gems.
So, perhaps we could rewrite 'rails' (or create something new like
newrails) where you could specify the generator to use.
I have a suspicion that most shops that do a lot of rails already
create a sort of template, but it's not readily shared. If it's as
simple as releasing a gem or exposing something that could be checked
out, I think that could lower the bar.
The end result, I think, is that it would help document best practices
for creating new rails apps.
On Apr 14, 11:25 am, Josh <joshua.nich...@gmail.com> wrote:
> I'm sure we all have passing familiarity with the 'rails' command to
> generate an initial rails app.
> After you do enough of them, you tend to fall into some patterns. Like
> removing comments from config/environment.rb, adding certain plugins,
> and so on.
> Wouldn't it be nice if you could setup a template for later reuse?
> Turns out the 'rails' command internally is just using a generator,
> just like anything you'd do with script/generate.
> You can create your own generators in ~/.rails/generators, or they can
> come from gems.
> So, perhaps we could rewrite 'rails' (or create something new like
> newrails) where you could specify the generator to use.
> I have a suspicion that most shops that do a lot of rails already
> create a sort of template, but it's not readily shared. If it's as
> simple as releasing a gem or exposing something that could be checked
> out, I think that could lower the bar.
> The end result, I think, is that it would help document best practices
> for creating new rails apps.
> On Apr 14, 11:25 am, Josh <joshua.nich...@gmail.com> wrote:
> > Hey all,
> > The next Hackfest is Tuesday night (4/15).
> > 7-9pm
> > Food, beverages, wireless provided by thoughtbot.
|
