Clojure
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
- Java,
Tracking change and innovation in the enterprise software development community
Posted by Mark Levison on May 27, 2008 01:00 AM
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.
Evolutionary Design through Agile Development Podcast
Offshore software development: Making it a success with Agile Practices
Smart agile development within dispersed teams
White Paper: Writing Good Use Cases
Lean Software Development Governance, a whitepaper by Per Kroll and Scott Ambler
VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
We introduce the concept of Composite Oriented Programming, and show how it avoids the issues with OOP and reignites the hope of being able to compose domain models with reusable pieces.
Dan Farino talks about the system architecture and the challenges faced when building a very large online community. Dan explains how a .NET product scales on hundreds of servers.
Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.
Bernd Mathiske discusses Maxine VM, Java compatibility, swapping major VM components, research areas, Object handling, code examples, optimizing compiler, snippets, bytecode generation, JNI and JIT.
Joe Armstrong speaks on various aspects of the Erlang language, presenting its roots, how it compares with other languages and why it has become popular these days.
The java double-check singleton pattern is not thread safe and can’t be fixed. In this article, Dr. Alexey Yakubovich provides an implementation of the Singleton pattern that he claims is thread-safe.
Diana and Jim talk about patterns observed in CTOs' activity. CTOs emerge as real people caring for other people in their organization, and are put under a lot of pressure and constraints.
No comments
Reply