AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos and change some grammatical constructions

Browse Source
This commit is contained in:
daniel.motzko
2021-07-02 10:31:14 +02:00
parent 28005ee0b6
commit 8bfcbe8ae7
6 changed files with 13 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2017-03-01/api-first-design-approach.md
View File

@@ -9,7 +9,7 @@ The API-First Design Approach puts the API design at the beginning of the implem
There are several advantages to this approach. For example, it can help to avoid reflecting the internal structure of the application or any internal constraints. Furthermore, as one of the most important design aspects is consistency, one can define features such as the behavior of security, URL schemes, and API keys upfront. It also helps speed up parallel implementation. A team that consumes the API can start working directly after the API design because it can easily be mocked. There are several advantages to this approach. For example, it can help to avoid reflecting the internal structure of the application or any internal constraints. Furthermore, as one of the most important design aspects is consistency, one can define features such as the behavior of security, URL schemes, and API keys upfront. It also helps speed up parallel implementation. A team that consumes the API can start working directly after the API design because it can easily be mocked.
There are several tools for modelling an API, but here at AOE we mainly use [RAML](/tools/raml.html) as it provides a rich set of tools for generating documentation, mocking and more. For mocking we use [Wiremock](/tools/wiremock.html), for example. There are several tools for modelling an API, but here at AOE we mainly use [RAML](/tools/raml.html) as it provides a rich set of tools for generating documentation, mocking and more. For mocking we use [WireMock](/tools/wiremock.html), for example.
Related to the "API-First" approach is the "Headless" approach where an existing application (with or without existing API) is used as a backend for a separate frontend. We used this with sucess for Magento-based E-Commerce platforms. This allows encapsulating the core features of that application, while integrating it into a larger landscape of components using its API as a unified way to interact between components. Decoupling the core logic from its presentation layer allows picking the best technology stack for the various parts independently. Related to the "API-First" approach is the "Headless" approach where an existing application (with or without existing API) is used as a backend for a separate frontend. We used this with sucess for Magento-based E-Commerce platforms. This allows encapsulating the core features of that application, while integrating it into a larger landscape of components using its API as a unified way to interact between components. Decoupling the core logic from its presentation layer allows picking the best technology stack for the various parts independently.

2
radar/2017-03-01/spring-rest-docs.md
View File

@@ -6,4 +6,4 @@ quadrant: tools
--- ---
[Spring REST Docs](https://projects.spring.io/spring-restdocs/) auto generates [Asciidoctor](http://asciidoctor.org/) snippets with the help of [Spring MVC Test](http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle#spring-mvc-test-framework) or [RestAssured](/tools/rest-assured.html). So you can be sure that your tests are inline with the documentation. [Spring REST Docs](https://projects.spring.io/spring-restdocs/) auto generates [Asciidoctor](http://asciidoctor.org/) snippets with the help of [Spring MVC Test](http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle#spring-mvc-test-framework) or [RestAssured](/tools/rest-assured.html). So you can be sure that your tests are inline with the documentation.
At AOE, we use [Spring REST Docs](https://projects.spring.io/spring-restdocs/) to document our Rest Services and Hal Resources. We also use it to auto generate [Wiremock](/tools/wiremock.html) Stubs, so the consumer of the service can test against the exact API of the service. At AOE, we use [Spring REST Docs](https://projects.spring.io/spring-restdocs/) to document our Rest Services and Hal Resources. We also use it to auto generate [WireMock](/tools/wiremock.html) Stubs, so the consumer of the service can test against the exact API of the service.

2
radar/2017-03-01/wiremock.md
View File

@@ -1,5 +1,5 @@
--- ---
title: "Wiremock" title: "WireMock"
ring: trial ring: trial
quadrant: tools quadrant: tools

2
radar/2019-11-01/self-service-infrastructure.md
View File

@@ -1,5 +1,5 @@
--- ---
title: "Self-service infrastructure" title: "Self-Service Infrastructure"
ring: trial ring: trial
quadrant: platforms-and-aoe-services quadrant: platforms-and-aoe-services

18
radar/2021-01-01/complexity-management.md
View File

@@ -1,14 +1,14 @@
--- ---
title: "Complexity management" title: "Complexity Management"
ring: trial ring: trial
quadrant: methods-and-patterns quadrant: methods-and-patterns
--- ---
Our world is increasingly complex - our society and the economy system is developing fast - we constantly have to deal with surprises and uncertainty. This is especially the case in IT organisations that collaboratively and crossfunctional work on innovations, "digitalization strategies" or "transformation projects". Our world is increasingly complex - our society and the economic system is developing fast - we constantly have to deal with surprises and uncertainty. This is especially the case in IT organisations that collaboratively and cross-functional work on innovations, "digitalization strategies" or "transformation projects".
Complex is something, where it is not possible to relate all its elements at the same time. There is no clear cause and result relationship. Decisions processes cannot be well structured. Something is complex, when it is not possible to relate all its elements at the same time. There is no clear cause and result relationship. Decision making processes cannot be well structured.
But of course that should not be used as an excuse - this realisation can motivate us to find ways to better deal with it. To come to better and new ideas together, to take good decisions and to learn from them. But of course that should not be used as an excuse. This realisation can motivate us to find ways to better deal with it. To come to better and new ideas together, to take good decisions and to learn from them.
Complexity management capabilities describe the ability to deal with complexity. The more different dimensions are used to observe and analyse a situation, the higher they are differenciated and the faster this is done - the better complexity is managed. [C2M Model](https://www.carl-auer.de/magazin/systemzeit/komplexitatsmanagement-modell-stufen-formen) Complexity management capabilities describe the ability to deal with complexity. The more different dimensions are used to observe and analyse a situation, the higher they are differenciated and the faster this is done - the better complexity is managed. [C2M Model](https://www.carl-auer.de/magazin/systemzeit/komplexitatsmanagement-modell-stufen-formen)
@@ -17,19 +17,17 @@ The complexity in IT initiatives and projects comes from the uncertainties of ho
Agile methods and other best practices evolved from that challenges - and are now widely adopted - but without proper reflection and complexity management they can also lead to dysfunctional communication patterns. Agile methods and other best practices evolved from that challenges - and are now widely adopted - but without proper reflection and complexity management they can also lead to dysfunctional communication patterns.
Since we are solving problems in collaboration we also need to deal with the complexity of the communication system (social system): Since we are solving problems in collaboration we also need to deal with the complexity of the communication system (social system):
addressed
* We are often seeing how large and historical organisations have a hard time with their transformation initiatives. * We are often seeing how large and historical organisations have a hard time with their transformation initiatives.
* We are seeing teams, where over the time dysfunctional patterns have emerged. * We are seeing teams, where over the time dysfunctional patterns have emerged.
* We see teams where no clear communication is established and where the important conflicts are not addressed. * We see teams where no clear communication is established and where the important conflicts are not addressed.
* We see teams that argue one-dimensional and spend time and energy in useless debates * We see teams that argue one-dimensional and spend time and energy in useless debates.
* We see organisations that are full of internal orientation and activities - while they are losing the connection to the external customers and market * We see organisations that are full of internal orientation and activities - while they are losing the connection to the external customers and market.
An understanding of how communication systems are working - and what conditions for working communication (and therefore collaboration) exist, helps to address such situations better. It also helps to understand how we can use conflicts for creativity (creating new perspectives and ideas). An understanding of how communication systems are working - and what conditions for working communication (and therefore collaboration) exist, helps to address such situations better. It also helps to understand how we can use conflicts for creativity (creating new perspectives and ideas).
That includes the awareness that we can always learn from each other! That includes the awareness that we can always learn from each other!
That is the reason why we see systemic perspectives with proper system theoretical background emerging in the space of organisational development. We believe that proper learning of this perspectives and the awareness of complexity management capabilities can help organisations to form functional collaboration. This learning helps reflecting systems and oneself more conscious - and that can be a healthy condition for more impact and learning. It may also help that an organisation does not blindly follow the next model, agile "hype" or consultant promises. That is the reason we see systemic perspectives with proper system theoretical background emerging in the space of organisational development. We believe that proper learning of this perspectives and the awareness of complexity management capabilities can help organisations to form functional collaboration. This learning helps to reflect systems and oneself more conscious - and that can be a healthy condition for more impact and learning. It may also help that an organisation does not blindly follow the next model, agile "hype" or consultant promises.
More on that topic: [Systemic Communication](https://www.carl-auer.de/magazin/systemzeit/communication-reorganization-of-undetermined) More on that topic: [Systemic Communication](https://www.carl-auer.de/magazin/systemzeit/communication-reorganization-of-undetermined)

2
radar/2021-01-01/wiremock.md
View File

@@ -1,5 +1,5 @@
--- ---
title: "Wiremock" title: "WireMock"
ring: adopt ring: adopt
quadrant: tools quadrant: tools
featured: false featured: false