[core-workflow] workflow types: agile (gameplay) vs rigid (process)

anatoly techtonik techtonik at gmail.com
Wed Apr 30 15:31:14 CEST 2014


Hi Nick,

On Tue, Apr 29, 2014 at 9:39 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> Anatoly, if you try to be part of this project, I will leave it. Your
> complete lack of empathy for the point of view of others is not acceptable
> in environments I am attempting to work in.

I don't know how to react to that considering that it is a public email.

  em·pa·thy: the ability to understand and share the feelings of another.

I don't think that you can understand and share feelings of people who are
living in a world without perspective. Note I am not saying that I am such
person, but empathy might be the last thing that these people need. If you're
not ready to contact with such people - that's ok, but requiring to erase them
from the open space that is also interesting to them is a little bit too much.

I need tools that speed up development of technology, and started with
user experience of collaborative Python support process since the day
I landed my first related edit to the Python wiki. I believe it was
several years
ago. Since then I changed few jobs, but still couldn't find one that allowed
me to dedicate more time and energy to the cause.

My braincells are not loaded with knowledge how to earn a lot of money, but
details of various core Python tools, Roundup tracker architecture, and
observations on the processes that are enough to construct a vision. The only
problem that to become a useful approach it needs more data, experiments
and a little bit different environment. I am trying to send a signal to the
subscribers of this list - don't try to solve the problem yourself - create an
environment where people will be happy to solve that problem for you. You
need more feedback from outside than you probably imagine.


> Anatoly, if you try to be part of this project, I will leave it.

There is no need for you to leave. I am already banned or moderated from
the most of Python things that were kind of important to me, and passive
aggressive style of my writing won't hold me there for long. And I also don't
want to be an annoyance if anything good is going to happen.

If you need my expertise or feedback - I am open for collaboration, or ask
Ezio - he is a good communicator and has a unique ability to filter emotions
from rationale.


More information about the core-workflow mailing list