3 ms·
I guess the devil is in the details: 1. How is a task estimated? What if it's wrong? How many misses before you fire the person? what if that person is taking m
by sharemywin 11y ago
I guess the devil is in the details:
1. How is a task estimated? What if it's wrong? How many misses before you fire the person? what if that person is taking more risks and taking on more responsibility and challenging tasks?
2. Usually you need some kind of process and task dependencies. What if there is a total bottleneck of "progrmmaing tasks" or "QA tasks" does someone go a week with pay to "work" for you?
3. what about benefits? Is this 1099 or W-2 work?
4. What about team based contributions? I help team mate X out with something is that a task? Do I get any contribution from it?
5. Who pays for training and education time? reviewing code?
6. What kind of rate are you targeting? What would my monthly pay look like?
7. what about strategic types of contributions. I know guy or I want to take sub market and run with it? or did you ever think about xyz? If your piecemeal-ing the work is there an allowance for that?
8. is there an opportunity to "buy-in" via time or contribution or even real money and get % of the profits or company?
9. how does the system evolve over time? fix problems? do "workers" have a say?
Sorry I'm really into the idea of marketplaces and using technology to build hyper-efficient eco-systems.
- harel 11y ago1. Task estimation depends on the task really. I always thought a feature is debated, decided upon and the outcome speced to some degree, wireframed etc. Duration can be estimated by the developer. Over time people learn to estimate more accurately. I don't want people to overstretch. I want realism in estimation. Under those conditions, if I have to fire someone, I'd be pretty pissed off that they put me in that position after I'm really trying to make something that works for everyone. You'd have to take the piss quite blatantly for that to happen. 2. Some positions are task based, like development. Some are continuous like QA or admin etc. The flexibility on hours and deadlines is extended where it makes sense. Its unfortunately not 'every role gets same conditions' situation. Fairness is the keyword here. 3. Not sure about that part yet. I'm not American, but my partner is. This is to be figured out still. 4. You don't get paid by your contributions. You get paid your salary like you would in any full time job. But that salary doesn't buy your soul. 5. You're an employee as every other employee. You were hired when the role made sense to have. Training is part of the job. 6. I want to pay well. Above market rate. But I want to hire only when the money for that person is allocated and put aside a year in advance. If I need 1 developer and can afford one dev, I hire one dev. I've been in scenarios where I had a budget and was told to buy resources. Those end up with hiring more resources than you know what to do with and that's not good either. 7. One thing I want to stop is white labeling and and bending backwards because client X said they want a feature that makes sense only to them. sub markets etc. are built into this product. If it makes sense - why not. If it deviates the product too much, i rather not. 8. I guess share options would be a thing at some point. We're privately owned, never took a penny from anyone. Also something to be figured out. 9. I am open to evolution, hear what everyone has to say, fix what needs fixing. This is why I've posted this here. This plan has been in my head for a long time now. I'm not ready to go with it just yet ,and a lot is balancing on the relaunch and its success. But I rather be prepared for that eventuality. Thanks for all your points here. It gave me a lot to think about.