InfoQ Homepage Culture & Methods Content on InfoQ
-
Software’s Hidden Clockwork: A General Theory of Software Defects
Les Hatton theorizes the possibility to predict the number of defects in software systems based on the observation that such systems have properties independent of why, how or who implemented them.
/presentations/Clockwork-Software-Defects/en/smallimage/Hat.JPG)
-
Entirely Predictable Failures
Poul-Henning Kamp considers that if developers are not getting better, we are going to repeat many of the major IT project failures. He exemplifies with major Denmark project failures.
/presentations/Predictable-Failures/en/smallimage/Poul.JPG)
-
Embracing Variability
Don Reinertsen proposes addressing uncertainty not by considering it harmful nor by embracing it but by efficiently reducing it in the context of the economic laws governing the software dev process.
/presentations/Embracing-Variability/en/smallimage/Don.JPG)
-
Bootstrapping Clojure at Groupon
Tyler Jennings presents how he ended up choosing Clojure, how he is using a Ruby tool-chain in Clojure, plus advice on introducing Clojure to a team.
/presentations/Bootstrapping-Clojure/en/smallimage/Ty.JPG)
-
Panel on Outsourcing
Aditya Bansod, James Mitchell, Martijn Verburg, Tony Grout, and Aino Corry (moderator) share their insight and lessons on doing outsourcing for software development.
/presentations/Panel-Outsourcing/en/smallimage/all.JPG)
-
Agile Leadership, Get the Rhythm
Martin Harbolt discusses Agile leadership practices promoting self organized teams and finding the proper rhythm for completing Agile projects with success.
/presentations/Agile-Leadership-Rhythm/en/smallimage/Martin.JPG)
-
The Lazy Learner
Chris Matts discusses ways of learning - Kolb’s Circle of Learning, Meme Wombling, Hangover – with a focus on the cycle starting from Unconscious Incompetence to Conscious Competence.
/presentations/Lazy-Learner/en/smallimage/Lazy.JPG)
-
Technical Debt, Process and Culture
Michael Feathers advices on creating an organizational process and culture that can enhance software development in a way that reduces technical debt.
/presentations/Technical-Debt-Process-Culture/en/smallimage/Michael.JPG)
-
Accruing Technical Debt: Practical Decision-Making and Its Business Relevance
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
/presentations/Technical-Debt-Practices/en/smallimage/Ebe.JPG)
-
Continuous Testing in Clojure
Bill Caputo discusses adopting continuous testing for Clojure, what are the goals of such a practice, how it differs from other languages, practical considerations (tools, setup) and a demonstration.
/presentations/Continuous-Testing-Clojure/en/smallimage/Bill.JPG)
-
Anarchy, Cooperation and the Bazaar
Ola Bini discusses using open source in distributed teams from a sociological, political, and organizational point of view, providing some lessons useful in daily development.
/presentations/Anarchy-Cooperation-Bazaar/en/smallimage/Ola.JPG)
-
The Generative Generation
Aaron Bedra shows code samples for writing Clojure tests using the test.generative framework, explaining why this framework and testing are useful.
/presentations/Clojure-Generative-Testing/en/smallimage/Bedra.JPG)