Some day, somewhere in the net there was iBlog. It was about everything and nothing. A few persons was reading it, some of them maybe even liked it. But I am not interested in writing about myself anymore. This blog will be about Project Management. Less personal, but in fact it will be my personal tool: to not forget what I have learnt. And what I ll learn in future.
RSS
niedziela, 21 grudnia 2008

I love Zope. It connects python's well-known hiperproductivity, Java's best design patterns and component oriented programming. It is a real mental amusement to code in Zope.

Last months I haven't been programming too much. But I have a bad, worrisome feeling that Zope3 development pace has slew down. But I just thought this just means that I've lost my interest in Zope when I switched my job.

But today I've looked to zope wiki and discovered that there are virtually no new articles. I've also found that last release is almost one year old and zope 3.4.0c0 is not even a real release, but a release candidate.

Someone would say: hey, but maybe the development has just been decentralized? Zope 3.4 is the first eggified release, so maybe the development just moved to eggs (z3c.* and others). 

But I digged deeper and displayed some stats of Zope3-Users traffic, thanks to google. What I found is below.

Zope3-Users List Traffic - compared 2007 to 2008. 2008 traffic is more than half lower.

Maybe the traffic moved somewhere else? This hypothesis haven't worked: I looked to zope 3 wiki and:

  • the last new topic is 3 months old
  • last month there is one edit of a topic
  • After July 2008 there was not a one month with more than 5 edits.

To summarize: It seems that zope3 development and engegement have been stalled for over half a year.

Any thoughts? Have I missed some switch to other communication channels? Has grok really took of all the hearts and souls?

What are the causes of the slowdown?

niedziela, 14 grudnia 2008

Indicators tend to direct your attention toward what they are monitoring

Andy Groove, "High Output Management": Managing the breakfast factory.

 

piątek, 12 grudnia 2008

For over 4 years I was accustomed to the meetings making sense.

I knew that everyone coming to the meeting will accept or reject invitation, will come on time, will be prepared and will be constructive.

It would be simple when your company's boss name was Andy Groove: http://meetingsnet.com/strategy/cases/meetings_meeting_effectiveness/

Otherwise meetings become distorted, unorganized bunch of people presenting their statements whenever they manage to interrupt a statement of others, not listening others and not seeing any purpose of the meeting except that they can always say after the meeting that "look, I told you at the meeting that this can happen, you haven't listened to me, or you haven't reacted to what I said. You are stupid, you are the guilty!"

Effective meetings... how much I miss them,,,

 

One statement is a packaged set of multiple informations on different layers.

  • Facts
  • Self-disclosure: about me and my feelings
  • Relational: about relationship between sender and receiver
  • Appelative

It is important to remember everytime you send a message (email, telephone, f2f), you actually send four messages.

Different people receive these four messages with varying strengths: some of them receive mainly one of the layers, others receive all equally, or one of them depending on situation. But be prepared that someone understood your statement in very different way you mean.

 A good example: a marriage in a car. The husband is driving. They have stopped at traffic lights. The wife tells: "look, we have the green light!".

  • Facts: there is the green light, we can go ahead
  • Self-disclosure: I'm in hurry to the hairdresser!
  • Relational: You are hindsighted, I would drive to the destination much faster than you! How could I marry such a muff!
  • Appelative: please hurry up!