Dec 10, 2018, 7:12 PM

@kanye-qwest said in Constructive (keyword) Criticism of Arx Systems:

@pyrephox Yes. I don't honestly find this kind of display very constructive, because the projected margin is so slim it's in 'who gives a damn' territory, but is presented in a way that all but begs for interpretation by people who don't want to math out the systems as "oh no if I don't do this right I am at a big disadvantage".

I agree with this and I want to chime in here that I feel that a lot of mechanical discussion can be kind of misleading.

From my experience, a lot of 'this is an inefficiency, and will surely create problems' usually don't exist because an analysis of numbers only miss out on overwhelming contextual reasons that would otherwise prevent them. When I intentionally create huge incentives for something, and more people talk about how it is OP than actually engage with it and use it, that's worrying for entirely different reasons. Like as an example, there was 11 modeling coderuns since the assembly. There's was nearly a thousand separate uses of 'praise' last week. I'm certain without checking there was far, far, far more uses of 'work' than that.

So from a macro perspective, the analysis would be like, 'modeling has a lot of pain points that make it vastly underused and need to be tweaked' and that there's a lot of issues with the resources work generates compared to other incomes. And from a systems discussion, people kind of poking at the furthest edge cases alienates people from experimenting with the common, more rewarding common cases and is actively counter productive imo.

ETA because I know someone will ask- no, that's a thousand separate uses of the praise command, not individual praises. IE, someone doing 'praise/all' is counted as 1 in that thousand-ish count.