2 ms·

> you were claiming the source of tax code complexity was from "desire to reward specific behaviors", which it (still) isn't. Of course it is. The whole point

> you were claiming the source of tax code complexity was from "desire to reward specific behaviors", which it (still) isn't. Of course it is. The whole point I'm making is that the end result of a system isn't what people asked for at the beginning. It's a result of countless small decisions made by (often) countless people with a wide variety of motivations. The definition of "income" is subjective. Short of a physics simulation, humans are always part of the "inherent domain complexity". I'm no fan of JIRA.... which is why I'm looking forward to your issue tracking system with all of JIRA's flexibility and none of the performance issues. I genuinely wish you the best of luck in this endeavor.

SilasX 7y ago
Did you read my second and third paragraphs? I was agreeing that “asking to tax income” is a case of “customer”-unrealized complexity and pointing out that it still isn’t the kind of thing reasonably described as individual rewards someone explicitly asked for. > I’m no fan of JIRA.... which is why I'm looking forward to your issue tracking system with all of JIRA's flexibility and none of the performance issues. I genuinely wish you the best of luck in this endeavor. Then it sounds like you’re walking back on your original claim that that JIRA’s bloat and UX failures are an inherent result of asked-for things like custom workflows?