New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Nov 28, 2008
In this presentation filmed during Agile 2008, Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD). The presentation intends to be a primer for managers who want to understand the value of TDD, and of Agile in general, in software development.
Watch: Manager's Introduction to Test-Driven Development (1h 19 min.)
The presentation starts with Karl showing a simple TDD example used to created an Excel worksheet including some Visual Basic macros. The purpose of this example is to show the difference between a static specification - a piece of paper with some specs - and a working one - code that runs and can be checked for errors.
The audience is then introduced to the various results generated by an increased design debt: increased costs, reduced velocity, raised number of defects, increased time spent on defects, increased support costs.
After demonstrating the value of TDD, Dave gives some advice to managers which do not have the technical skills to drive the implementation of TDD by their development teams:
Case Study: IBM's Agile Transformation
A Guide to Branching and Merging Patterns
A practical guide to choosing the right agile tools
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Poor video production, poorly prepared speakers, and misses the central point of TDD - its role as a design tool.
Shameful.
For those who want to see what inspired the two guys:
www.clarkeching.com/2006/04/test_driven_dev.html
Personally, though, I think the exercise is too technical for managers, and it's actually a great example of TDD not automatically giving you a neat solution without a lot of sweat (which is how reality works sometimes, unfortunately :-) )...
I once saw a very convincing presentation of RSpec by Aslak Hellesøy, and I sat next to a very non-technical colleague. She got really excited about TDD (or, rather, BDD) from the presentation, so I think RSpec is a much better platform for such a presentation than Excel/VBScript. Your opinion may differ.
I don't agree. I actually think Karl and Dave give pretty good arguments for managers - remember, the target audience is managers, not us technicians. But even though I'm a technician, I can still use the points from the presentation, as I often have to deal with managers and convince them that TDD is the right thing to do.
Great presentation! Congratulations!
Bob wrote:
> Poor video production, poorly prepared speakers, and misses the central point of TDD - its role as a design tool.
Bob, to be quite blunt: your comment was rude, thoughtless and unhelpful.
Clarke
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
5 comments
Watch Thread Reply