Nathaniel Talbott discusses the concept of Experiment Driven Design.
Brian and dave discuss what it might mean to be a true craftsman and why the idea of craft has become so popular of late. Other issues discussed include the question of why craft seems to be focused almost exclusively on programming and why everyone does not aspire to be a craftsman? Programming as performance art, programs as literary artifacts, and code "habitability" round out the discussion.
Tobias Mayer talks about the philosophy behind WelfareCSM, unbounded vs bounded creativity, the application of Scrum outside of software development, Kanban vs Scrum, the benefits of fast-failing, software development as an artitistic endeavour, software craftsmanship and XP, test-driven development, and the done state.
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should also practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
In this interview made by InfoQ’s Deborah Hartmann during Agile 2008, Rebecca Wirfs-Brock talks about software design, the need for good design and the technical debt that might accumulate slowing down the development process. The conclusion is that agile developers should not disregard design.
Debate sprang up at JAOO '07 around Bob Martin's assertion that "nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.
Pragmatic Programmer Dave Thomas, author of the 'pickaxe book' Programming Ruby, and co-author of Agile Web Development with Rails and The Pragmatic Programmer, found some time to talk with InfoQ about Ruby, Rails and the importance of choosing the right tool for the job.
Lean software gurus Mary and Tom Poppendieck share their years of practical experience, as they speak on the history of Lean thinking, the value of fast delivery and deferred committment, their use of Value Stream Mapping to identify and reduce waste, the importance of identifying and dealing well with cross-organizational and inter-organizational boundaries, and how Lean relates to RUP and Scrum.
Ron Jeffries' upcoming book looks at how tracking "Running Tested Features" is the essential element of Agility, from which all other practices and activities necessarily follow. Deborah Hartmann interviews Ron who takes to the whiteboard to explain how, when supported by XP's "simple design" practice, RTF helps teams deliver consistently without building up costly technical debt.
InfoQ editor Obie Fernandez asks David some hard-hitting questions about the future of Rails in the enterprise, profiting from his success and whether a vendor will fork Rails someday. Contains lots of good information for technologists staking their future on the Rails platform, including David's opinions on Rails adoption, service-oriented architecture and scaling Rails applications.