[Boulder-Denver Ruby Group] Ruby spots on the Front Range?

[Bothari]

Let's make a deal.

I've gotten a couple responses already, and one request for a summary
of what I find.

Just to make it interesting, I'll be glad to summarize the responses
and post them (names redacted) to anyone that sends me info on
Thursday.

If you don't have anything to contribute, just send me a note saying
you don't know the answer to my question, but you work at <company
name> and do java/ruby/whatever and it rock/sucks because <why>.  That
way you're on the list and I have more info, but I won't post those
messages without your permission.  I still won't post your name,
because it could be your cow-worker trying to get you fired.  ;-)

Unless I win the Powerball I'll send it out Thursday.  I'm asking a
similar question in Houston, and if I get anything worth having there
I'll include it, too.

Thanks,
Joe

On 5/21/07, Bothari <bothari at gmail.com> wrote:
> Greetings, Group!
>
> My name is Joe Fair, and I am a former resident of the Front Range.
> I've developed lots of Java, but I'm trying to move to Ruby full-time.
>  I was wondering how the market is in Denver?  Are there any full-time
> people hiring, or contracting spots that require a local person?  Are
> there any places to persue or avoid?
>
> I'm in the middle of Oklahoma now, so the only option is full
> telecommute gigs.  I'm open to that, but I'm looking for a good reason
> to move back to Colorado.  :-)  I can develop in Java, too, but I want
> to start doing more Ruby this year.
>
> I attended the Rails Studio in Denver last year, and there seemed to
> be several companies open to the idea.  Does anybody know if those
> seeds took root?
>
> Email me offline and I'll keep your name out of it.  :-)
>
> Thanks,
> Joe
>
> --
> "For a new software system, the requirements will not be completely
> known until after the users have used it."  Humphrey's Requirements
> Uncertainty Principle.
>


-- 
"For a new software system, the requirements will not be completely
known until after the users have used it."  Humphrey's Requirements
Uncertainty Principle.