References:
Saturday, October 12, 2013
Mindfulness and critical mass of time
References:
Monday, September 30, 2013
Paranoid or wise, corporate philosophies, their fate!
265 B.C., king Ashoka ruled the single undivided kingdom from Sri Lanka to Afghanistan. This paranoid king fought and won several battles or wars. Often corporate philosophies like "only paranoid survive" or "demanding perfectionist", "rule over the world and moon" are few such examples. These examples showcase the paranoid or war derived behavior. Are these mere extensions of Darwins theory of "survival of the fittest"? The battle of Kalinga was Ashoka's final battle, this battle made him much wiser or extremely emotional. He lost interest in kingdom, he also cared less to choose the right successor for the kingdom. Most of the original eastern philosophies were full of emotions and wise behavior.
In the midst of paranoid corporate philosophies, often there are fresh messages popping up. These fresh messages are based on works of "8 habit: Wisdom by Stephan Covey" or "Emotional Intelligence". Does this help make the paranoid behavior any milder? If yes, what for? Paranoids perish, so does the wise, former contributes to history and later care not.
References
- http://en.wikipedia.org/wiki/Ashoka
- Only the paranoid survive … by Andy Groove from Intel Inc.
- Steve Jobs by Walter Issacson
- George Bernard Shaw Man and Superman (1903) "Maxims for Revolutionists"
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
Thursday, August 29, 2013
Is measuring software productivity still a grey area?
Most of the time we are busy (productive?) developing and delivering the software tools and methodologies. Product delivery or code delivery dates are decided based on the end product or software component. Productivity is a very relative varying between different product teams and companies such as startup and market leaders. Decades ago software productivity was measured as lines of code, then it was measured as the number of projects or components developed. There are plethora of other techniques such as functional points and then the business values achieved by a team or an indiviual. It is ROI after all. It is too late to identify actual returns until the very end and so productivity is purely function of past experience or a grey area. Individual or teams working on same kind of software and having different ROI respectively depending on the final business value, so business value cannot be actual measure of software productivity.
• References: "Cannot Measure Productivity" by Martin Fowler http://feedly.com/k/17omkp1
Tuesday, July 23, 2013
Train resting neural networks, responsible child's for lack of attention
NLP: meta-model of behavior during managing a change, a quick summary!
- NLP for work, a practical guide by Dianne Lowther