Bobtuse Bobservations

Less than obtuse observations
about software development
& teamwork

by Bob MacNeal

31 December 2009

Scintillatingly Significant 2000-2010


10.
The 10th Planet
10th Planet

9.
The Large
Hadron Collider
The Large Hadron Collider

8.
FOXP2 Gene
FOXP2

7.
Extrasolar
Planets
Extrasolar Planets

6.
The Toumaï Skull
Toumaï Skull

5.
Cloning
Dolly

4.
Water on Mars
Mars

3.
MicroRNAs
MicroRNA

2.
The Genome Zoo
Genome

1.
The Kiwi Frog
The Kiwi Frog
Tweet it on Twitter Tweet this!
Bobtuse
by Bob MacNeal at 12/31/2009 05:30:00 AM 0 comments
Labels: 2000-2010, Decade
Older Posts
Subscribe to: Posts (Atom)

Posts

  • ▼  2009 (68)
    • ▼  December (4)
      • Scintillatingly Significant 2000-2010
      • No One Likes to be Managed - What's Next?
      • Socket To Me - The Web Socket Primer
      • Lessons From The Google Rocket
    • ►  November (6)
      • Instant Boot Bliss
      • What We Need To Know About Chrome OS
      • Information Discovery & Chirpitude
      • Story Board for Google Wave
      • Ain't No Code Monkey
      • Software Teams versus Groups
    • ►  October (7)
      • Launch Early and Learn
      • Professional Persona Primer for Twitter
      • The Missing Link in Google Wave - UI For Primates
      • A Plan B Approach to Planning
      • Map and Terrain - The Limits of Planning
      • The Good, The Bad, and The Mail-It-In
      • Design Serves Human Purpose
    • ►  September (4)
      • Software Development Discovery Skills
      • Surfing The Transition Waves
      • Agile's Chicken Kiev Duality
      • Tomato Logic - Pomodoro Primer
    • ►  August (10)
      • Team Decisions & Commander's Intent
      • Agile That's Made to Schtick
      • Beware Ceremony
      • Lazy Man's Agile
      • Quality's Okay, But Who's Paying the Freight?
      • Usage-Centered User Stories & Story Mapping 2
      • Usage-Centered User Stories & Story Mapping 1
      • What Does Best Practice Mean?
      • Agile & Optimal Foraging
      • The Emergence of Google Wave-Etiquette
    • ►  July (4)
      • Festering Manifestos - What is Software Quality?
      • Will Google Wave Overtake Microsoft Groove?
      • Software Teams, Comedic Improvisation, & Acceptanc...
      • Google Wave and Collaborative Projects
    • ►  June (3)
      • User Story Tweets
      • When Did Agile Jump the Shark?
      • 100% Coverage is a Crock of Clam Juice
    • ►  May (7)
      • If Software's Like Farming, How Do I Certify Organ...
      • Simple Design or Swiss-Army Knifing?
      • Team Manifesto - Craftsmanship, Behavior & Minutia...
      • Beware The Seductive Narrative
      • Is Version One a Software Chindōgu?
      • Code Cleanup - Stupefyingly Satisfying
      • Baffle, Befuddle, & Bewilder - Obscuring Url Token...
    • ►  April (4)
      • Laconic Look-see into Quality
      • Beginner's Mind, Dumb Luck & Agility
      • Pavlov's Programmers
      • Why Design-Build?
    • ►  March (4)
      • Scrum Method-ist or Pragmatist?
    • ►  February (8)
    • ►  January (7)

 Subscribe in your reader

Loading...

About Me

Bob MacNeal
Bob MacNeal
View Bob MacNeal's profile on LinkedIn

An Invitation

An Invitation

agile .net practitioners is a global community for .net practitioners who have adopted a practical approach to agility. If that is you, please join us by clicking our logo above.

We limit our group to practicing software professionals. We have lively discussions, topical news, events, a member-aggregated blog list, and screened gig postings.

~ Bob MacNeal, moderator

Read-Worthy

Tag Cloud

acceptance Agile Agile Aptitude Test Agile Manifesto Agile roles Agile Teams Agile Transition architect Augusto Boal Beginner's Mind Blink Brevity Ceremony change Chindōgu CIO ClustrMap Coding Standards Collaborative Software collective intelligence Commander's Intent Concise Writing contracts Craftsmanship Craftsmanship Contract Creativity Backlog Cross-Functional Team CSharpistan customer value Daily Scrum decision making Decision-Making Design Charrette Design-build Developer Stories Discovery distributed Duality effective Teams Emergent Behavior emergent design Evolutionary Design expedience vs. quality Extreme Interview Fallacies of Code Coverage Fixed bid Google Wave Google Wave Adoption Googleplex Grooming and Feeding Backlog Groove growing software Hiring Impediments List Improvisation Individuals and interactions over processes and tools Innovation Innovation Backlog Inter-Personal Debt List intuition iPhone Iteration Planning Joanie's Cafe lasting ideas Lazy Man's Agile Lean Manufacturing Made to Stick metaphysics of quality Microsoft Groove minimum viable product Mobile Application MVP Naming Scrum Projects Naming Sprints Narrative Fallacy Nomenclature Non-dogmatic Opportunities opportunity Optimal Foraging Theory Organizational Change paired programming Paradox Personas Pomodoro Technique Product Backlog Product Owner Project Names quality Refactoring Reflection Resharper Respect the Tomato Retrospective Scrum Scrum dogmatist Scrum Pragmatist Scrum Tips ScrumMaster Self-examination self-organization self-organization in nature Self-organizing teams Sho Shin Social Behavior Social Conventions Social Intelligence Software metaphors software quality Sprint Standup Strength Subjugation of Ego SUCCES Sustainability SWOT systems integration Team Identity Team Manifesto Team Unity Team-Reflection teamwork Technical Debt List The Black Swan The Manifesto for Software Craftsmanship Theatre of the Oppressed Threats Time Management tomobako Transitioning to Agile truisms Tweet Unit Test Usability Usage-Centric Design Use Case User Experience User Story User Story Mapping User-Centric UX Version One Wave Etiquette Wavetiquette WD-40 Weaknesses XMPP xplanner
Locations of visitors to this page