Annotated SOA Manifesto. SOA Manifesto ramblings and observations PART 1. It has been a couple of week at least since we published the SOA Manifesto. Alas I have rather busy putting some of it into practice. But that is done now. So time to elaborate further. I plan to break this blog into 3 parts to provide some clarifications, some observations and some personal opinions about the SOA Manifesto.
In this blog I want to deal with three specific points in the SOA Manifesto. In the next two blog I will deal with much of the rest of the SOA Manifesto. The three specific points relate to the following: "Service orientation is a paradigm that frames what you do. "Service orientation is a paradigm that frames what you do. The term Service Orientation is the antecedent to SOA. Clearly we can use C++ in an non-OO way. Thus the terms OOA and SOA are types of things not instances.
Why is this important? "Business value over technical strategy"Providing a business context is all important. "Verify that services satisfy business requirements and goals. " Bre Pettis | I Make Things - Bre Pettis Blog - The Cult of Done Dear Members of the Cult of Done, I present to you a manifesto of done. This was written in collaboration with Kio Stark in 20 minutes because we only had 20 minutes to get it done. The Cult of Done Manifesto There are three states of being.
Not knowing, action and completion. Accept that everything is a draft. It helps to get it done.There is no editing stage.Pretending you know what you're doing is almost the same as knowing what you are doing, so just accept that you know what you're doing even if you don't and do it.Banish procrastination. Update: James Provost made the awesome poster for the Cult of Done Manifesto. And Joshua Rothaas made this poster. The Cult of Done Manifesto for Agile Software Development.