Hi Raj,

Thanks for reaching out, but unfortunately we are looking for someone local 
for this project. Nice looking site, though!

Jarin

On Tuesday, December 16, 2014 11:54:00 AM UTC-8, Raj Sanghvi wrote:
>
> Hi Jarin,
>
> We have done lot of work in ROR and one of our recent platforms is 
> www.villageunity.com, let me know if the work is remote.
>
> Regards,
> Raj
>
> On Monday, December 15, 2014 11:12:58 AM UTC-8, Jarin Udom wrote:
>>
>> Hi everyone!
>>
>> Some of you might know that I left the freelance game and I've been 
>> working for a small, private financial company (JMJ Financial) for the last 
>> year or so. It's been awesome.
>>
>> Anyway, we currently have an accounting system that's built in MS Access 
>> with a MySQL backend. We want to rebuild it as a web application. Why not 
>> just use Quickbooks or something, you ask? Well, this thing has a pretty 
>> darn complex data model/workflow. It needs to track loans, stock transfers, 
>> stock sales, commissions for the sales folks, and various tax and FINRA 
>> rules. It's more of a "track the assets as they get transformed between 
>> money and stocks and split into several buckets and then recombined into 
>> other buckets, but we need to know which buckets everything came from" 
>> system than a traditional accounting system.
>>
>> Part of the reason we need to rebuild this thing is the MS Access code 
>> has gotten out of hand, because the requirements have changed quite a bit 
>> since it was originally built. Don't worry, you're probably not going to 
>> have to even look at any of the VB.Net code unless you really want to.
>>
>> We've got the original developer on board with this rebuild, and she 
>> knows the way the accounting workflow works inside-and-out. Unfortunately, 
>> she's not super familiar with web frameworks yet, so we'd like to have 
>> someone more experienced come in to help build the thing while she gets up 
>> to speed. I'd be all about it, but I'm gonna be busy with another project 
>> during that timeframe.
>>
>>
>> Here's what we're looking for:
>>
>>    - Good at Rails. Like, you generally do things the Rails Way, but 
>>    you're all like "decorators are way better than helpers, yo", and you 
>> have 
>>    an opinion on factories vs. fixtures, and you've probably been burned by 
>>    using models in your migrations at least once. Maybe you had a brief 
>> fling 
>>    with Cells and Apotomo. We don't judge.
>>    - Someone who can come into the office for at least a good chunk of 
>>    the week, so they can pair program and be able to consult face-to-face 
>> with 
>>    the accounting department folks.
>>    - Strong test-writing skills, because this thing is dealing with 
>>    money.
>>    - Gotta know how to use git.
>>    - No slouch at databases, because eventually there will be a painful 
>>    and tedious data migration from the old database to the new one.
>>    - Familiar with some kind of server automation/deployment 
>>    (Capistrano, Moonshine, Puppet, Chef, Docker, etc.)
>>    - Considers cache invalidation and naming things to be easy. [nice to 
>>    have]
>>    
>>
>> What we've got to offer:
>>
>>    - Good rates. We pay well and on time.
>>    - Challenging and interesting project.
>>    - Friendly, professional office environment.
>>    - Possible full-time employment later on (I think about half the 
>>    people here started off as consultants, including me).
>>
>> Anyway, we've got about a month off for the holidays starting Thursday, 
>> so this project will kick off mid-January. I'll be in town for most of the 
>> break. If you're interested, hit me up and we can grab lunch or beers or 
>> something and chat about it. Please email me some examples of stuff you've 
>> done already if possible.
>>
>>
>> Jarin Udom
>> [email protected]
>>
>

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to