Looking for Rails developer to join a startup and become co-founder
YL
It has to be someone who's passionate about software, knows the stuff,
doer, and can work alone. Phase one will take about 200-250 hours to
develop. Flexible hours, part time, from home. Compensation will be
high percentage equity, or contract fee, or combination of the two. If
interested, tell me about yourself, some work that you did, and why
you're interested.
The project has a business model and it revolutionizes an existing
one. It's powered by the community, but not for the purpose of plain
personal networking. You'd use it only if you need to do a transaction
-- and it's the type of transaction that most people do.
Phlip
YL wrote:
> Looking for Rails developer to join a startup and become co-founder.
> It has to be someone who's passionate about software, knows the stuff,
> doer, and can work alone. Phase one will take about 200-250 hours to
> develop.
Even when executives are just trying to help, they almost always cause
friction when they estimate hours. Speak in terms of the estimated number of
pages and the number of gadgets on each page.
Next, some developers only deal locally. This is my preference - and maybe
I'm the only one! But still, report where you are located. Distance is
another source of friction.
--
Phlip
http://www.oreilly.com/catalog/9780596510657/
"Test Driven Ajax (on Rails)"
assert_xpath, assert_javascript, & assert_ajax
YL
widgets per page. As we all know, it's rather difficult to estimate
software and I would like to box it in about 200-250 hours for the
first phase. I am based in New York City, but I am open for
development overseas.
YL
Robby Russell
On Sep 10, 2007, at 10:04 AM, Phlip wrote:
>
> Some advice on a startup jag...
>
> YL wrote:
>
>> Looking for Rails developer to join a startup and become co-founder.
>> It has to be someone who's passionate about software, knows the
>> stuff,
>> doer, and can work alone. Phase one will take about 200-250 hours to
>> develop.
>
> Even when executives are just trying to help, they almost always cause
> friction when they estimate hours. Speak in terms of the estimated
> number of
> pages and the number of gadgets on each page.
Just wanted to follow up on this...
I'd argue that focusing on # of pages and gadgets isn't a good way to
work either. We're building solutions and it shouldn't be measured by
the # of gadgets that show up on a screen. Even then... one
"gadget" (not a word I'd ever use on the web...) could take more time
than the rest of the application, so I'd not recommend focusing too
much on counting components/features/gadgets.
My two cents,
Robby
--
Robby Russell
Founder and Executive Director
PLANET ARGON, LLC
Design, Development, and Hosting with Ruby on Rails
http://www.planetargon.com/
http://www.robbyonrails.com/
+1 503 445 2457
+1 877 55 ARGON [toll free]
+1 815 642 4068 [fax]
Phlip
> I'd argue that focusing on # of pages and gadgets isn't a good way to
> work either.
I'm not talking about estimates while developing; I'm talking about up-front
estimates. Estimates while developing are a walking average.
> We're building solutions and it shouldn't be measured by
> the # of gadgets that show up on a screen. Even then... one
> "gadget" (not a word I'd ever use on the web...) could take more time
> than the rest of the application, so I'd not recommend focusing too
> much on counting components/features/gadgets.
You haven't had a Parisian boss e-mail you a list of >15 complex bugs that
someone else wrote, and say "now get these all done in two days".
--
Phlip
YL
that's not gonna happen here. You'll be writing the first line of
code!! I think it's a cool fact worthwhile mentioning...
Mitch Pirtle
YL
be able to make it to tomorrow's meeting, but I plan to attend the
next one on Oct 9. I look forward to it.
YL