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 Mark Levison on May 27, 2008
Dissatisfied with other Agile Certifications, S.M. Kripanidhi has proposed a "Community Certified Agile Practitioner".
Kripanidhi has a number of reasons for believing certification valuable:
He suggests that we use local communities to judge if the practitioner is worthy of certification:
Who better knows an Agile Practitioner other than the actual
stakeholders (manager,customer,team,peers,community) involved with
him. They are the best judge if the Agile Practitioner is good in
Agile.
Kripanidhi proposes five certifications: Practitioner (an individual team member), Leader, Trainer, Coach and Evangelist (existing and emerging thought leaders). Certifications would be renewable on an annual basis.
David Spann suggests we start by asking who the audience of these certifications and asking why they want a certification:
Who: the person with the certificate
Why: they want to have proof of accomplishment and ability the world
can easily understand, e.g., a college degree, an author, a certified
practitioner
Now that the community is too large for everyone to know each other Laurent Bossavit and Brian Marick have implemented the first version of an alternative to Certificates. Replacing certificates individuals make formal statements of certification, example:
I, Laurent Bossavit, a member of the agile community, certify Rachel Davies as having outstanding skills in Retrospective Facilitation, based on the following evidence: I attended a Retrospective which she facilitated at a conference and took away key learnings from the experience.
When you've collected several statements in a given area potential employers or clients will know that you have some expertise. In Starting Ideas a number of possibilities are explored that explain how this individual statements can be turn into a useful measure(s) of trust.
18 agile and lean practices for effective software development governance
SCM best practices for multiple processes, releases & distributed teams
Agility at scale, become as agile as you can be
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!
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.
No comments
Watch Thread Reply