Thousands articles are exist to describe what it is. Perhap I should go with mine.
Tools. Programming.- Source Code Management
- Test-Driven-Development
- Continuous Integration
- Progress Monitor
- Risk-driven, result-oriented.
- Consolidate. Adjust. Compromise.
- Tight deadlines are creativity rush. Make many deadlines, iteratively.
iteration.each { |work| work.simpler, work.smaller, work.smarter, work.wiser }- Power. Politics.
- Right mix of people
- In time of darkness and despair, make the team learn the hard way
- Encourage learning environment
- Participatory decision making. Perspective has nothing to do with seniority, skillsets, IQ/EQ/AQ level, and experiences.
- I’m a dumb ...
- ..and lazy too.
- Law 10: Subtracting the obvious and adding the meaningful.
- Fuck the markitecture1. A markitecture looks great on paper and in diagrams, but doesn’t translate at all well into practice. Debugging is believing is only way to be.
Every bullet deserves succint explanation. I will do that later. So consider this as a roadmap.
Besides, it’s my “first” post. I need to know how Textile works in Mephisto ;)
1 Rod Johnson, J2EE Development without EJB p.71.

