Andy Hume shares details of the processes and approach used by The Guardian in developing and implementing quality in their front-end software.
Jim McCarthy makes a passionate call for developers to rise up to their call and make their software great, sharing their light with the entire world.
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.
Ahmed Syed explains how to use testing and defect management in an Agile project to ensure product quality, addressing design quality, legacy systems, and how build management affects quality.
Hamlet D'Arcy explains the Lean principles - Eliminate Waste, Build Quality In, Create Knowledge, Defer Commitment, Deliver Fast, Respect People, Optimize the Whole – in the context of using Groovy as programming language.
Traditional thinking says the more critical the application, the more tightly its development must be planned, staged and controlled. The truth is, a flexible culture is stronger, safer and more robust. This talk gives practical tips for adopting an agile approach to planning, team interactions and risk management. When the culture shifts, teams achieve goals sooner and safety is greatly enhanced.
This presentation covers how to rapidly evolve a web site that receives over 25 million unique users and 218 million page impressions a month using a "just in time" approach to architecture. The site was guardian.uk with a long history of innovation that has enabled it to lead the market. The "just in time" approach to architecture introduced complexity into the architecture only as needed.
It is possible to measure certain properties of code, and on the one hand, correlate them with project factors known to have economic merit and on the other, with programmer-pleasing practices. This session surveys emerging evidence that we can measure the effect of the technical practices of Agile development, and explores what we might be able to do about it to our benefit.
In this video recorded during QCon London 2008, Pete Goodliffe presents two Linux-based audio products with a complete different outcome, software design making the difference.
In this talk from RubyFringe, GitHub's Tom Preston-Werner talks about a methodical approach to solving problems and debugging. Also: he explains how to use the "Deathbed Filter" for choosing projects.
Developer-driven testing is probably the most influential software development technique of the last 10-15 years. There's no question that it has improved the practice of building software. And in a dynamic language like Ruby, it's hard to get by without it. But is it really the best way to find defects? Or is the emphasis on testing and test coverage barking up the wrong tree?