Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Tiny




Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.


Chad Fowler is CTO at 6Wunderkinder. He is co-founder and organizer of RubyConf and RailsConf and author or co-author of a number of popular software books, including Rails Recipes and The Passionate Programmer: Creating a Remarkable Career in Software Development. Twitter: @chadfowler

About the conference

Code Mesh, the Alternative Programming Conference, focuses on promoting useful non-mainstream technologies to the software industry. The underlying theme is "the right tool for the job", as opposed to automatically choosing the tool at hand. By bringing together users and inventors of different languages and technologies (new and old), speakers will get the opportunity to inspire, to share experience, and to increase insight. Via presentations and case studies, we aim to raise awareness and extend the knowledge of all participants, mainstream and non-main stream users alike.

Recorded at:

Mar 26, 2015

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Presentation good, but could be more "tiny"

    by Johnny FromCanada,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Generally good presentation. Skip the first 9 mins to get to actual content.

    "Tiny" AKA "Keep Things Small" seems to be just another expression of the ubiquitous Lean-Agile "tighten feedback loops" or "rightsizing".

    Liked the "dissonance" mental trick, and presenter's general pragmatism. Also liked the references to human/social psychology studies, and to actual data.

    For more on how team structure is like code per Conway's Law (see Allen Kelly's presentation on Conway's Law and Continuous Delivery). I suspect a successful team/code structure going forward will be "Reactive" (see Reactive Manifesto).

    For more on self-organizing "anarchist" ways, see Programmer Anarchy (by Fred George).

    On local optimization, it is implied that Lean is fundamentally about small relative changes, i.e., "Kaizen" (continuous change). But Lean also has a sister concept of "Kaikaku" (radical change).

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p