Your blog post about living systems says planned systems cannot incorporate living systems. I tried to distribute decision making by leading without authority and to adopt asynchronous communication channels as much as possible. As a result, I was warned about severance. I wouldn't mind unemployment normally, but I'm legally bound to my company until Feb 2015 before which severance is a severe damage to my life. I gave up on bringing a creative chaos to my company.
Oh... life is sad. On the positive side, I will probably start building new projects on top of ZeroMQ next year. Making security convenient on user side is important. If average teen girls had to generate a private/public key pair to log in a web service, they would freak out. How do you think we'll achieve security for laymen? On Fri, Feb 21, 2014 at 11:03 PM, Pieter Hintjens <[email protected]> wrote: > On Fri, Feb 21, 2014 at 2:00 PM, crocket <[email protected]> wrote: > >> By the way, the issue has been going on for months. 0mq community policies >> are more like a social technology than a business model, but I want to >> address this community terms of business. A typical corporate >> manager/executive wouldn't be patient enough to wait for indefinite amount >> of time for an issue. That's why they prefer to make us suffer long commute >> and interrupt us in offices. How do I best apply the wisdom of crowd to my >> current company or my job? > > My last blog post about Living Systems, hintjens.com/blog:74 may help > answer that. > > -Pieter > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
