Well, you heard a bit of conversation about it in the Uncle Bob interview.
I would like to introduce the idea and what it is and what its intention is.
Ammerse is simply a "way of thinking" of "design oriented" things "written down". At the moment the way in which it is written is rough, and can be thought of as a draft. However, I felt that after 8 years or more of having this "method", it was time to write some of it down quickly, before I chicken out or come up with reasons why its bad, and not worth pursuing and other negative thoughts that plague my head.
If you are anything like me, you procrastinate, and with really strong counter arguments, you eventually end all pursuit of it. I am trying to overcome this self concentrated mind game, by simply doing, simply making it happen and taking whatever comes my way.
Ammerse is this. You are faced with a project, and you need to get started. What is immediately involved with the decisions you need to make? What are the most important aspects? How do patterns and methods fit in. Ammerse points you to Patterns, more suitable (not exact matches, as you have to decide), but towards the ones that matter for that Principle. (I am still working through the list). The main aim of Ammerse is to provide an umbrella for the process, design, and implementation aspects of a project. It is an Index to Agile Methods and Patterns.
You can read about Ammerse, and tell me what you think so far.
I have still tons of things to add, and tons of clarification to make in the copy, but please send you comments. I will do my best to think about each one and filter it into the set of principles.
Previous Topic
