Every problem in software development will need a good interaction among people to bring about a solution. Where there is excellent software we will find a team able to communicate proficiently. Social intelligence, communities of expertise, user groups and open source projects are the real engine powering our growth as developers day by day.
Leverage your best: the others.
27. From Wikipedia: Sheldon is also a difficult person to work with. In "The Electric Can Opener Fluctuation", Sheldon finds out that the others have tampered with his experiment, in order to make him more pleasant to work with. He also found out that they were considering killing him and had even come up with a plan to do so. When Leonard comes up with an idea for an iPhone application to solve physics problems, Sheldon immediately tries to seize control of it. When Leonard makes it clear that he is in charge, Sheldon continues to annoy the others, resulting in him getting fired by Leonard. When he asks why, Leonard tells him "[he is] impossible to work with".
2009, LaGuardia Airport Lost power in both engines at takeoff Cpt. Sullenberg flew F-4 for seven years, onle then he started collecting 19K hrs of commercial flight experience. He worked in commissions investigating aircraft crashes and cooperated in improvign emergency methods. He flew gliders too, not a detail. He glided his Airbus in the Hudson river that day. Plane OK, all 150 pax safe “ That's what we're trained to do” 19000: more than 5 hrs a day for 10 years Coordination with flight assistants
Melbourne McBroom, captain, 28k hrs Known for his dominant and harsh attitude In 1978 he was about to land with his crew in Portland Landing gear was locked so he started to fly in a stand-by route, trying to fix the problem The story is short: while completely focused on the l.g. Issue, Cpt. McBroom completely ignored the fuel indicator and, absolutely not a detail, his crew was so locked by his anger that no one dared to tell The plane crashed killing 10 people This accident was the basis of the institution of many airline's Crew Resource Management programs..
Genius is like Dunning Kruger
Functional teams: skill centred, enhance excellence, incentivates suboptimization & unintended stops, due to dependencsies Even unethical behaviours!!! Cross-functional teams: business centred, enhance success & flow, waste of expertise, this is the price.
Community of expertise They are a way to mitigate or even solve the problem of expertise waste The best way to spot where we need a COP is to identify where standards are lacking.
. People working in remuneration companies have this agreement with their company: “I will show up for work and you will pay me for my time. If you want more, pay me more”. On the other hand: “I will treat you the way you treat me. I expect a fair compensation, but if you want care & commitment, I expect care & commitment and you will help me develop my full potential” Vicious circle: no sense in investing in people since they will move. But people will move even more if they sense a company doesn't care about them.
.
.
.
.
.
.
. So it seems I am not that HUGE nerd. I still find my self clicking on the 'random article' link on Wikipedia on a sunny sunday afternoon. Do you know the Latin name for the fruit fly? I know it! I still find my self spending nights writing lines of PHP code to implement a knapsack algorythm. All in all I still love to code my code. But I am sorry to tell that...
. The fact is times for old-school nerds are gone.
Reciprocity based companies or opensource!
Today fluffy talk, but lots of people speaking about super interesting topics today! I wish I had access to such a community in the early 90's...
SW developmnet needs standard. PHP even more! Let's ccoperate as much as possible and still there's lots to be done on this front. Symfony CMF is a try to standardize the world of PHP based CMS.
Valuable ideas can withstand scrutiny (Beck) Opensource is the best example We don't need full-time unanimity (Beck) We don't need compliance (Beck) Memetics and darwinian point of view Let's disagree if it provides us with *expertise*
Valuable ideas can withstand scrutiny (Beck) Opensource is the best example We don't need full-time unanimity (Beck) We don't need compliance (Beck) Memetics and darwinian point of view Let's disagree if it provides us with *expertise*
Naramore's PHP Benelux presentation Quality and then money
The Bible is a book, no books is a Bible Others provides insights, sometimes very distant ones
Network theory. Small worlds. Weak edges leading from a small world to another are the fruitful. Recruitment 2.0 Not to be hired only. To hire ! Quality has a nice taste for hiding. Communities snipe quality out of its lair.
“ No longer discussing perfection with people” Development skills Leading skills, leadership! Not as in “power” but as in “persuasion”
Community of practice Social anti-patterns can hurt performance
Learn how others are living the same problems Discover their problems are like yours Get yourself amazed staring at people self-organizing PUG Roma from 6 to 20+ in just a few months
Kickstart your own project Validate your skills, your readings & your failures Choose a new development path
Social anti-patterns can hurt performance Pair programming Close customers Technical managers Genba Opensource as evolutionary development
A beer, a drink Just meeting people Face to face vs. forums Low tech, low cost knowledge management
Perfect "docking"(?) for our tech & social skill development Community is the key to make it perfect for our needs Learn to customize methods to context