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 Mike Bria on Sep 16, 2009
One thing well known by most programmers is that the best (only?) way to learn programming technique is by example; specifically, watching someone else doing it. Antony Marcano & Andy Palmer's PairWithUs gives people a great place to do just that.
The styles and techniques of software craftsmanship, things for example like Test-Driven Development and Refactoring, take time to understand, get the hang of, and do well. One of the best ways to accelerate this process is to work with other people who can show you different ways of doing it. Pair Programming is a great way to do this, simply watching other people pair can often be another. Further, the practice of pairing in and of itself is one of those things that you need to see work to really get it.
Knowing this, Antony Marcano and Andy Palmer have launched the new PairWithUs initiative, what they refer to as "agile software development (user stories, tests, code and more), broadcast live and recorded for your future viewing pleasure." Through this site the two provide access right into real live pair programming between them - you get not only the code screencast but also travel with the two of them as they pair, experimenting with varying ideas and techniques, which is probably the real gem of what they're doing.
In their own words:
We aren't trying to teach any specific technology or technique. Instead, we'd like to share how we combine several software craftsmanship techniques, shown in the style of a fly-on-the-wall documentary.
The main learning point that we hope our viewers take away is that it's ok to make mistakes and to change your mind. Things don't have to be perfect, first time, every time, as long as you progressively make things better.
We aim to show the real deal including uncertainty, debate and eventual clarity (along with some petty arguing and occasional tangents).
But most of all... we're two guys who have fun programming :-)
The pair have used Vimeo to post nearly 70 25 minute pair programming sessions (aka, pomodoro's). Most of the videos so far track their progress through a "FitNesseNarratives" project, one in which they are providing FitNesse users a way to use the common BDD-influenced "Given-When-Then" style for FitNesse pages.
There's no charge, its free (.."as in beer"). Take some time to check out what these guys are doing, use it for yourself or someone you know who might be having some trouble understanding (or believing) some of the things you're telling them about pairing and craftsmanship.
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
Agility at scale, become as agile as you can be
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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.
2 comments
Watch Thread Reply