If you've a clear idea of my stance on Milestones, you know that I'm unsatisfied with them. If you don't, now you do. Fact is, I have a very clear set of goals for that system, and I'm trying to design it around them. I've come to you guys and to the staff for help on it, but mostly nothing's fit my criteria.
I'm just making a very small tweak for right now, just to see how well it works out.
My primary goal being to teach an understanding of how much power is deserved for a certain amount of change and growth:
ALL MILESTONES, SUCCESSFUL OR NOT, WILL BE INFORMED WITH MY OWN ESTIMATION.
For example, I might deny your 1000 and say "600 was more appropriate." Or I might look at your 500 and say "you could have gone up to 700 on this one."
I'M STILL GOING TO BE APPROVING/DENYING BASED ON WHAT YOU ASK FOR.
I don't want this to turn into a way you can use me as a disposable gauge. I want to go by your score, and I want over time our ideas to converge. If you think mine should move, not yours, convince me. I budge.
Thank you for your continuing patience. I know milestones and requests in general are a little sketchy, and they may continue to be for a while. But I am interested in making the process better.
Don't tell anyone, but any waiting periods you see in the rules are kind of silly and pointless. Fact is, it's possible to grow a lot in under a week, and if so why should I make you wait?
For me, these time limits are another one of those "soft" rules. Call them guidelines. You probably shouldn't be requesting more rapidly than that, unless there are extenuating circumstances. They're also an excuse for me to not review the same request twice in a very short time, which is as tedious for me as it is for you to make a new one. So sometimes I let requests sit for a couple days extra in order to make the lesson actually have a (small) consequence.
That's a separate situation from leaving requests for a week and more, though. That's my own fault.
Post by Colin Arascain on May 14, 2014 2:56:11 GMT -5
Good to know, but it doesn't really answer my question.
I request 1000. My request is denied, you tell me I should have requested 600.
What happens next?
Do I have 600?
Do I have the option of saying 'Okay, so give me 600'?
I mean, we both know that ideally the person will make an updated request with more threads and post it again later on to try again for their original requested value, but supposing that doesn't happen, what then?
Is it that they have to develop further before they get anything...?
Not trying to give you a hard time here, man, just trying to cover all outcomes.
I'M STILL GOING TO BE APPROVING/DENYING BASED ON WHAT YOU ASK FOR.
I don't want this to turn into a way you can use me as a disposable gauge. I want to go by your score, and I want over time our ideas to converge. If you think mine should move, not yours, convince me. I budge.
You have 0. I move the request into the "Finished" bin. You then choose to either wait and do some more development or come back with the same request. Copy paste if you like. Makes it cleaner for me.
Post by Fulfillment on May 14, 2014 12:01:16 GMT -5
This is fantastic, and exactly what many of us wanted! Wherever this takes milestones in the future, I'm really excited to get some feedback as to what you think we should be asking for.
Post by Rania Fujikagi on May 14, 2014 12:19:57 GMT -5
He IS telling you though, isn't he?
If you requested 500 but Mithutaka thinks 700, you still get 500. In time, he wants that amount to converge to the same number so you're both thinking along the same lines.
If you requested 1000 but he thinks it's only worth 600, you get zero until you post the same request again for 600 GP or for the original amount and more development
Post by Souta Suzuki on May 14, 2014 12:22:19 GMT -5
Mika, "telling us what we get' means he just tells us how much GP he gets. Instead of Us requesting a number, we just submit the request, and then he assigns the number.
Post by Rania Fujikagi on May 14, 2014 12:46:16 GMT -5
But you are requesting GP for your development.
I can see where you're coming from but in the end, it's not something I personally think he should be giving you. It's something you should hopefully be able to accurately judge for yourself too. The whole "give a man a fish versus teach a man how to fish" argument in a sense?
Mika's spot on. I've heard your desire for me to just give it to you straight, but that's not my deal here. I want to teach something that goes beyond my own personal understanding; something that would stay if I'm gone, a skill that reflects more the writing itself than my interpretation of it.
Post by Fulfillment on May 14, 2014 14:14:12 GMT -5
That's the point of the update though. Before we were just kind of cruising along, sort of kind of getting feedback if we'd overreached. Now we see each time what our growth was potentially worth or not worth, and after a bit of watching that number you should get a better grasp over where you're going and the impact you're having, etc. This helps not just Mitsu, but us as well.