- Automatic update/cloud deployment
- Crash recovery
- Reduction of dependencies through standards
- Continuous build/integration/release/test
- Initial code quality
- Convergence of the user and test community
Saturday, February 18, 2012
Why software is better
Thursday, February 16, 2012
Alistair Cockburn. Collaboration: the dance of contribution
Key Ideas
Lift others: Be courteous. Lower your social posture. Listen intently. Recognize others.
Increase safety: Be yourself. Donate. Widen the boundary. Support others. Challenge but adopt ideas. Build personal relationships. Don't betray.
Make progress: Success breed success. Say something valuable. Clarify the way forward. Focus. Get a result.
Add energy: Challenge. Contribute.
Key Ideas
Lift others: Be courteous. Lower your social posture. Listen intently. Recognize others.
Increase safety: Be yourself. Donate. Widen the boundary. Support others. Challenge but adopt ideas. Build personal relationships. Don't betray.
Make progress: Success breed success. Say something valuable. Clarify the way forward. Focus. Get a result.
Add energy: Challenge. Contribute.
Wednesday, February 15, 2012
Mobile-Social-Cloud
Three trends that change business: Mobile, Social and Cloud
"We are at the beginning of the next twenty years of IT evolution. These trends will combine to create the biggest technology shift since the Internet. Successful companies will use these technologies to transform the business."
Monday, February 13, 2012
Creativity Patterns
Creative Thinking Hacks by Scott Berkun
and implementations in SW development.
1. Journal
Backlog, Test List, To Be Improved part of Retrospective, Futurespective
2. Escape
Focus-Manna, Pomodoro, Break
3. Invert
If you're stuck, come up with ideas for the opposite of what you want
Assert First, Test First, DIP?, IoC?
4. Partner
Can't find a partner? Find a rival.
Pair Programming, Mentoring/Coaching, Peer Code Review, Coding Dojo
5. Fail
The first draft of anything is shit
-Ernest Hemingway
Prototyping, Spiking
6. Switch Modes
If stuck: find new way to represent the problem, using a
different mode of communication.
and implementations in SW development.
1. Journal
Backlog, Test List, To Be Improved part of Retrospective, Futurespective
2. Escape
Focus-Manna, Pomodoro, Break
3. Invert
If you're stuck, come up with ideas for the opposite of what you want
Assert First, Test First, DIP?, IoC?
4. Partner
Can't find a partner? Find a rival.
Pair Programming, Mentoring/Coaching, Peer Code Review, Coding Dojo
5. Fail
The first draft of anything is shit
-Ernest Hemingway
Prototyping, Spiking
6. Switch Modes
If stuck: find new way to represent the problem, using a
different mode of communication.
Thursday, February 9, 2012
Subscribe to:
Posts (Atom)