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 10, 2008
There is value (to prospective employers and co-workers, and others too) in knowing something about people's competencies. We might as well call that "certification". The Agile community, as a whole, has more knowledge about who's competent in the areas that define Agile, and what these areas are, than any sub-group of the community could have. Therefore, a scheme for "certification" which involves the entire community is more valuable, if it is feasible at all, than one which involves only a central certifying authority.The basics of how it works, from the site:
That it is feasible at all is a relatively new idea, which explains why it hasn't been done before - I became aware of that only after reading Clay Shirky's [book] Here Comes Everybody.
People sign up to a Web site, after which they can certify people they know. They do this by entering a Statement of Certification.We Vouch For... is a "For the People, By The People" effort; it has a chance of working only if you get involved, and no real chance if you don't. Visit the site and decide for yourself what you think. And, as always, please take a moment to let others here know what you decide.
A Statement of Certification is a strong, solemn, formal statement. 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."
It's important that it should include all parts: someone who states that he/she is a member of the community, the name of someone he/she wants to certify, an area of competence, an assessment of the person's skill in that area : serviceable, highly valuable, outstanding; and mention of the substantial evidence on which this judgement is based.
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
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!
...but how is it better than recommendations on LinkedIn?
I see several problems. If you an outsider to the community who do you trust first? You have to pick someone you trust and then see who their web includes.
Second the community can be very clubby and self serving - lets say I recommend Mike B.; Mike recommends Joshua K. and Joshua recommends me. Seems a little bit self serving and definitely not impartial.
Finally if you're not currently a consultant and work inside an organization (especially a small one) then it might be very difficult to gain the recommendations of the these external consultants.
Finally not all certifications are bad the Scrum Alliance put a lot of work into creating the Scrum Coach Certification (www.scrumalliance.org/view/guide_level_of_certi...) and the standards behind are quite rigorous. See the pdf file: www.scrumalliance.org/resource_download/312 for an explanation of the requirements.
Hi Mark,
Is it self-serving? Maybe, but certainly no more so than LinkedIn. As for impartiality, I don't really care. If I'm shopping for a product or service I prefer a recommendation from a friend over an impartial review, although in the absence of a recommendation from someone I know and trust, an impartial review is better than nothing.
I've seen certifications gamed before, although admittedly the CSC is rigourous. My Dad worked in the insurance industry, and he once talked about a salesman who consistently led the Ottawa region in sales for the company in which my Dad worked. He won awards and free trips, etc. What wasn't well known was that he also led in lapsed policies, i.e. those that weren't renewed, because he never really followed up or had any concept of after sales customer care.
I could see someone similar as a coach, moving from engagement to engagement providing some short-term value but not much that really "stuck". He could likely get a couple of recommendations from past clients and have the other qualifications required to become a CSC.
Would that same person make it through a peer-driven process like We vouch For?
Dave Rooney
Mayford Technologies
Most certifications of this sort just mean you've accomplished some MINIMUM standard. It doesn't mean you actually put it into practice. Thus, I think having someone vouch for you is indeed a good idea.
But then, I'm one of those who favors some sort of licensing for software engineers.
Dave - I think that "We Vouch For..." could be gamed in the same way. Also nothing stops me from creating sham accounts at "We Vouch For..." and then giving myself glowing recommendations.
While I'm not certain that certification is the solution at least we called people's references and asked them non trivial questions that might expose such a scam.
A key line of the story:Said another way, to have <strong>someone credible</strong> vouch for your credibility.
So, the idea is not only that I go see that someone thinks <em>you</em> are credible, but I have at least some ability to make an assessment of that someone's credibility as well (presumably to increase my confidence in their recommendation of you). So, it's not just the singular vouches that are important, but, really, more the <strong>network</strong> that supports the reliability of the whole thing.
Indeed, probably not a perfect system, of course not. And, sure, if someone really wanted to spend their day gaming the system, technically they could. But the hope is "the network" factor could surface scams and the like. Further hope, of course, is that their occurrence is minimal in the first place. I think it's worked for LinkedIn, hopefully could for this too.
Jim - I can't speak for most certifications. I can speak a little about the Scrum Coach Certification. To get it you have to be practicing coaching (and keeping a log) for 1500 hrs or the better part of a year full time. In addition to the hours, you have participate in the community, etc. Finally there is a competency test and its full of essay questions and not questions with cut and dried answers. So I suggest in this case the certification is rigorous. It might be as Dave suggests vulnerable to scam artists and charlatans, but its better than you might expect.
To be fair, I do find the "scrum coach" cert is somewhat reasonable. It's the "SCM" cert that I find a bit questionable. (And, yes, I am a 4 year SCM grad myself).
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.
7 comments
Watch Thread Reply