Thursday, July 1, 2010

Sore Legs Lactic Acid

Because in life you need ... to be agile:)


From childhood słyszmy from various "good uncles" what is "important in life." Unfortunately, it is rare to hear about adaptability or agility life (in the sense agilności).

Jadnak somehow everyone in the IT Agile - Some time ago I did a little research, in which hardly found one company in India, which openly says that it is not agile;)

When, however, take a closer look , with that Agile is like sex in teenagers - each with a This speaks but few are really doing (or at least they did several years ago in class mat-inf;)
say that Agile is difficult because of the seemingly easy - so easy that everyone seems to understand.

In this post I will not write about the problems with methodologies (by the way, the methodology is the study of methodologies). We will focus on soft matter, or problems with people.

How often do you encounter an almost fascist, anti-adaptive attitude type:

- do not write comments, write a self-commenting code (but self-commenting on whose point of view?)
- good code should have 70% of the comments so that one could play it by reading it (but why?)



- Stories are better / worse than the Use Case (at what level?)


- YAGNI and KISS (even if I have an intuition that is useful?)


- Java rules / .NET rules (but then it different?)

- always use IoC and ORM (but why and for what?)
- ORM is crap, only the SQL procedures (But at what cost?)

- just as the base Oracle / Postgres / ... (But to each project?)
- as the base is only noSQL (because it is sexy?)

- always write tests - "You are not allowed to write a single line of production code without a test first" - thundered some time ago, Uncle (nomen omen;)
Bob - you should have at least 80% coverage of the tests (and why not 85%? settery too?)
- do not write the tests never (ever!?)

- methods should be 5 lines (for 6 go to jail?)
- methods should be so long that it should be possible to understand them in 5 minutes (But to understand by whom)

- always use Maven (even in the 1910 draft jednomodułowym libami?)

- static languages \u200b\u200bare better (better for what?)
- dynamic languages \u200b\u200bare better (especially as to the String class's 150-Append methods



- browser / OS / IDE X is better (better for what? to help you say it or even to podroczyć?)

could just multiply indefinitely ... I do not know

whether it is an affliction only of our industry, but it inhibits what Agile is in the process of Authoritarianism in people. Perhaps authoritarianism is a general meme "inherited" after those in the first sentence wujaszkach. Perhaps it is embedded in our minds as their strict integrity ficzer - a coprocessor seek one naively simple equation at all.


Unless we have more and more often KNOW HOW TO KNOW WHEN missing.


can put it differently: in the equation

Wisdom = Knowledge + Context

most important is the context. The context is what distinguishes the theory and practice. Context allowing adapt knowledge. The context in which the Competency Model Dreyfus Brothers comes with time and experience. And experience is a reflection. Reflection is necessary to adapt approach.


//=================================

In most civilizations consistency is a virtue. The phrase "you're not consistent in their behavior" is very pejorative connotation.

But more agile is a different approach - an approach adaptive : "Consistency is the fortress of fools." Consequence exempt from observing, thinking, and adapt (not to be confused with the consequences of perseverance).

It is not about to zafiksować on something that has consistently put his head down and dig like a pig for truffles. From time to time we pick it up to check if the objective is still in front - and maybe on the horizon appeared a different, better target and it is worth adapt?