Group conflict

People in teams dont always cooperate with each other. When they dont, its called a disagreement. What makes some disagreements disagreemnts and others?

I believe that conflicts are necessary in any team. It may not be nice, yet the outcomes usually improve if/when the team comes to a new agreement. I believe people always have a valid reason behind their disagreements - even when they're joking around.

Most of the time, others don't know exactly where you are coming from. Let them know.

I generally find the most difficult thing in teamwork is getting people to listen. Actually listen attentively. I used to force my way in because I got so frustrated. Nowadays, I find acknowledging my understanding before shooting away a more pleasant experience.

Developers getting lots of doc from stack-overflow

So very true. How did people write code before stack overflow???

Perhaps this is an example of just how badly documented most things really are. Or if the library is well documented, it's too dry with no examples.

http://developers.slashdot.org/story/13/03/05/1755216/developers-may-be-getting-50-of-their-documentation-from-stack-overflow

What I feel about the News

IT WAS the best of times, it was the worst of times,
it was the age of wisdom, it was the age of foolishness,
it was the epoch of belief, it was the epoch of incredulity,
it was the season of Light, it was the season of Darkness,
it was the spring of hope, it was the winter of despair,
we had everything before us, we had nothing before us,
we were all going direct to Heaven, we were all going direct the other way.

-- Tale of Two Cities, by Charles Dickens.




It is the best of all times, it is the worst of all times.
It is the time of technological advances, it is the time of artificial disasters.
It is the age of intelligent people doing dumb things, It is the age of ordinary people doing great things.
It is the days of great openness, it is the days of forbidden secrets.
It is the time of convenience, It is the time of information overload.
It is the time of freedom, it is the time of bondage and control.
It is a time of prosperous peace, it is a time of chronic violence.
It is a time of astonishing beauty, it is a time of revolting ugliness.


It is the epoch of belief, it is the epoch of incredulity.
There are many in high happiness, there are plenty in secluded depression.
It is the season of awesome light, It is the season of terrible darkness.
It is the Spring of Hope, It is the Winter of Dispair.

We have everything before us, We have nothing before us.
We are in Heaven, We are in Hell.

-- Modern Times, by Me.


Feel free to add to it!

It's over, and we all know it.

http://sas-origin.onstreammedia.com/origin/gallupinc/GallupSpaces/Production/Cms/POLL/s7pyxwkvskssjtqfjk4kxw.gif

Talk about low approval ratings!

Programming with LOVE

I guess I've been programming for about 5 years now (seriously for 3), and this is something I just realized, writing code for the NAO robot. The fact that it's cute as hell probably helped here.

Programming is a form of communication with a life-form that doesn't know what you know (yet). And just like humans, animals and plants, it's easier to get what you want if you are sincere and love that life-form. Now, one may be a great programmer but sucks at the process of programming itself, or vice versa. If one sucks at the programming process, then that's just like a lover who sucks at kissing or flirting (aka HOW to love). On the other hand, the one who is great at all the tools and processes of programming may feel lost at writing complex code despite all the knowledge. This one is the lover who is a great kisser and seducer, yet can never maintain a relationship for long.

The same goes for code. Some people are great at coding, but can never maintain it - for them, it remains as just a tool. Others are always learning, but it's the love of the whole program that drives them.

Programming can teach you to love without expectations. Expectations cloud one's thinking and judgement, preventing you from seeing what the code really does. If you can love your code, it's more likely to work well.

--to be continued--

Question

Today, a friend of mine posed a very interesting question - what do I know that you didn't? 

Answer:
The answer told me a lot about this guy that I/he probably didn't realize.

 First of all, his tone told me he was being haughty and dismissive. We went through a whole bunch of things and always preferred to say "I've heard of it, but I don't believe it/like it." instead of honestly listening and moving the conversation forward.

He showed a remarkable disdain for "people who only knew how to study." And you know what? I used to too! Today's culture perpetuates the mass belief/filter that there are winners and losers, and so people compare themselves to each other. This means that the underpinnings of the rebellious is still love of the system, except by hating that which they do not have. An example of this is the thief who steals money who is expressing their love of the monetary system, just as the hardworking worker who earns it. The only difference is that one is lead to believe he is a victim and the other is a victor. This sort of thing ruins people for life, societies for ages and stays there until it is changed, manifesting itself as both positive and negative human emotions as "jealousy", "feeling inadequate"(especially in males), "useless", "pleasure" and "fear".

I guess I prefer people who are secure and don't try to threaten others with insecurities, but I understand a bit about how people can turn out like that.

On the good side, I found that verbalizing what my knowledge bases made myself clearer to me and I'm sure this guy thought so too. In a way, we all mirror each other and so we can see ourselves in others.