Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Ben Hughes on Jun 15, 2007
From discussions on several mailing lists, it is very clear that people who aren't a CSM recognize the deception, people who are CSMs recognize the deception, and even the CSM trainers recognize the deception. Yet the CSM program carries on ....... It is clearly deceptive to claim that you're a "certified master" of something after taking a two-day course. Although an argument currently rages within the Scrum community over whether the problem is the use of the word "Certified" or "Master," this serves merely to distract people from the real issue.Scott discusses the kind of experience-backed courses that could be applicable to the Agile world, and draws some ideas from other certification programmes that he feels set the certification standard for the IT industry, and outlines the characteristics of what he believes a successful certification should be:
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
Certification in processes like Agile are essentially a scam to bilk unsuspecting people out of their traning budget. There hasn't ever been a process-based certification hasn't been discreditied or outright corrupted.
Consider CMM and CMMI. You can make some big money as an auditor, especially when defense contractors bribe you to get the rating that allows them to even bid on contracts.
Then there is six-sigma, which is the same nonsense with a cool karate belt theme.
ISO 9001 is by far my favorite. To get certified all you need to do is have a process. Even if your process is "Ignore all bugs until the customer is screaming, then drop everything and fix them.", counts so long as you write it down.
What would an Agile certification be anyways? By its very definition any answer you give is right so long as you back it up with "We tried it and it works for us."
Make more sense to me..
Scams aside - there is a problem that needs a solution. The problem is: how do I get people who know how to practice 'X' correctly?
Let's be fair- consultants will tell you they know this thing inside-out and backwards and will claim that THEY have done wonders with Agile (whatever that is exactly varies...)
So - how do you suggest solving the problem? Or is there not a problem to start off with?
By the way - I'm not in favor of certification as it always have been done. But we need a solution other than "Certification is stupid so we won't do it."
Something like "Certification is stupid and therefore we should do X instead to solve the existing problem" is a better approach. Unfortunately, I have no idea what X is at this point in time.
I believe I've seen this title inside an organization somewhere... in an organization it makes sense, where there is a program an apprentice can follow - making books available and allowing them to shadow or help more senior practitioners.
However, as a purely classroom experience of certification, the active sense of apprenticeship is not so clearly present: you sat thru the class... what are you doing now?
Ok, the problem is: "How do I get people who know how to practice 'x' correctly"?
1. Define "correctly".
2. How does certification prevent customers from hiring people that don't know what they're doing? If certification was a guarantee, there wouldn't be malpractice lawsuits.
I've done both the CSM and PMP. I mostly did it just for knowledge. In both cases I wish I had my money back. If there were to be some sort of agile certification tomorrow, I would not sign up for it. I would continue to practice as I always have. If, at some point, it became impossible to get a job without this certification, I would grudgingly comply, no doubt finding myself a few thousand dollars poorer and absolutely no wiser.
Since neither you or I knows what we should do to solve the problem, I suggest we do the simplest thing possible: nothing.
Can you please provide me the reference of where this report of Scott Ambler cited above, was published. I wish to read it in full.
Thanks for the heads up. Done :-)
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
7 comments
Watch Thread Reply