Update README.md

Author: justinamiller

README.md

@@ -76,8 +76,8 @@ Keep in mind the problem-solving principle Occam’s Razor which states to prefe
 
 ## (4) Code
 Even as an Enterprise Architect, the most abstract level of architecture, you should still know what developers are doing on their daily basis. And if you do not understand how this is done, you may face two major problems: 
-(1) Developers won’t accept your sayings and 
-(2) You do not understand challenges and needs of developers.
+  1. Developers won’t accept your sayings and 
+  2. You do not understand challenges and needs of developers.
 
 * Have a side project: The purpose of this is to try out new technologies and tools to find out how development is done today and in the future. Experience is the combination of observations, emotions and hypothesis (“Experience and Knowledge Management in Software Engineering” by Kurt Schneider). Reading a tutorial or some pros and cons is good. But this is just “book knowledge”. Only if you try out things by yourself you can experience emotions and can built up hypothesis about why something is good or bad. And the longer you work with a technology the better your hypothesis will get. This will help you to take better decisions in your day to day work. As I started programming I had no code completion and only some utility libraries to speed up development. Obviously, with this background I would make wrong decisions today. Today, we have tons of programming languages, frameworks, tools, processes and practices. Only if you have some experience and a rough overview in the major trends you are able to take part of the conversation and to steer development into the right direction.
 * Find the right things to try out: You cannot try out everything. This is simply impossible. You need a more structured approach. One source I recently discovered is the Technology Radar from ThoughtWorks. They categorize technologies, tools, platforms, languages and frameworks into four categories: Adopt, Trial, Assess and Hold. Adopt means “strong feeling to be ready for enterprise usage”, Trial means “enterprise should try it in one project that can handle the risk”, Assess means “explore how it affects your enterprise” and Hold means “process with caution”. With this categorization it is easier to get an overview of new things and their readiness to better evaluate which trend to explore next.
@@ -111,8 +111,8 @@ From my observations this is one of the most underestimated skill. If you are br
 ## (8) Balance
 * Quality comes at a price: Earlier I talked about quality and non-functional requirements. If you overdo architecture it will increase costs and probably lower speed of development. You need to balance architectural and functional requirements. Over engineering should be avoided.
 * Solve contradicting goals: A classic example of contradicting goals are short- and long-term goals. Projects often tend to build the simplest solution whereas an architect has the long-term vision in mind. Often, the simple solution does not fit into the long-term solution and is at risk to be thrown away later (sunk costs). To avoid implementation into the wrong direction, two things need to be considered: 
-  (1) Developers and business need to understand the long term vision and their benefits in order to adapt their solution and 
-  (2) managers who are responsible for budget need to be involved to understand the financial impact. It is not necessary to have 100% of the long term vision in place directly, but the developed piece should fit into it.
+  1. Developers and business need to understand the long term vision and their benefits in order to adapt their solution and 
+  2. managers who are responsible for budget need to be involved to understand the financial impact. It is not necessary to have 100% of the long term vision in place directly, but the developed piece should fit into it.
 * Conflict management: Architects are often the glue between multiple groups with different backgrounds. This may lead to conflicts on different levels of communication. To find a balanced solution which also reflect long-term, strategic goals, it is often the role of architects to help overcome the conflict. My starting point regarding communication theory was the “Four-Ears Model” of Schulze von Thun. Based on this model a lot can be shown and deducted. But this theory needs some practice, which should be experienced during communication seminars.
 
 ## (9) Consult and Coach