architect role and abstraction

Author: adrien1212

content/basics/abstraction.md

@@ -3,4 +3,8 @@ title = "L'asbtraction"
 weight = 5
 +++
 
+{{% notice style="tip" title="Ressources" icon="fa fa-book" %}}
+[When NOT to write an Abstraction Layer](https://youtu.be/tqqH_Ib_gDc)
+{{% /notice %}}
+
 Comme l'a noté Edsger W. Dijkstra dans son article "The Humble Programmer ", le but de l'abstraction n'est pas d'être vague mais de créer un nouveau niveau sémantique dans lequel on peut être absolument précis.

content/software_architecture/architect_role.md content/software_architecture/architect_role/_index.md

@@ -32,3 +32,12 @@ Il est primordial pour un architecte logiciel d'avoir des connaissances dans le
 Ainsi en plus des compétances technique, l'architecte devra évoluer fonctionnellement. Dans le cas contraire, il lui sera très difficile de comprendre les attentes et besoins métiers et d'y répondre de la plus juste des manière.
 
 > Les architectes les plus performants sont ceux qui possèdent des connaissances pratiques/techniques étendues ainsi qu'une solide connaissance de leur domaine métier.
+
+## Avoir des connaissances sur les non-requirement
+
+Ce terme n'indique pas des choses qui ne sont pas requises, il se réfère plutôt à des exigences qui ne sont énoncées nulle part.
+Cela inclut le contexte, les suppositions tacites, les dépendances cachées et d'autres choses qui n'ont jamais été explicitées.
+
+On trouve la scalabilité, la maintenabilité, la disponibilité, l'intéropérabilité, etc ...
+
+Débusquer ces exigences implicites et les rendre explicites est l'une des contributions les plus précieuses de l'architecte.

content/software_architecture/architect_role/what_is_not.md

@@ -0,0 +1,45 @@
++++
+title = "Ce que n'est pas un architecte"
+weight = 45
++++
+
+{{% notice style="tip" title="Ressources" icon="fa fa-book" %}}
+
+- The Software Architect Elevator
+  {{% /notice %}}
+
+Un architecte n'est pas un :
+
+- **Senior developer**
+  Developers often feel they need to become an architect as the next step in
+  their career (and their pay grade). However, becoming an architect and a
+  superstar engineer are two different career paths, with neither being supe-
+  rior to the other. Architects tend to have a broader scope, including organi-
+  zational and strategic aspects, whereas engineers tend to specialize and
+  PART | I
+  deliver running software. Mature IT organizations understand this and
+  offer parallel career paths.
+- **Firefighter**
+  Many managers expect architects to be able to troubleshoot and solve any
+  crisis based on their broad understanding of the current system landscape.
+  Architects shouldn’t ignore production issues, because they provide valua-
+  ble feedback into possible architectural weaknesses. But an architect that
+  runs from one fire drill to the next won’t have time to think about architec-
+  ture. Architecture isn’t operations.
+- **Project manager**
+  Architects must be able to juggle many distinct, but interrelated topics.
+  Their decisions also take into account—and affect—project time lines,
+  staffing, and required skill sets. As a result, upper management often
+  comes to rely on architects for project information, especially if the project
+  manager is busy filling out status report templates (Chapter 30). This is a slip-
+  pery slope for an architect because it’s valuable work, but it distracts from
+  the architect’s main responsibility.
+- **Scientist**
+  Architects need to sport a sharp intellect and must be able to think in mod-
+  els and systems (Chapter 10), but the decisions they make impact real busi-
+  ness projects. Hence, many organizations separate the role of the chief
+  architect from that of a chief scientist. Personally, I prefer the title chief engi-
+  neer to highlight that architects produce more than paper. Lastly, although
+  scientists may get their papers published by making things sound complex
+  and difficult to understand, an architect’s job is the inverse: making complex
+  topics easy to digest

content/software_architecture/definitions.md

@@ -42,3 +42,5 @@ An architecture is the set of significant decisions about the organization of a
 - Prendre des décisions sur l'organisation du logiciel, ses composants et leurs relations
 - Minimiser le coût du changement en écrivant un logiciel flexible
 - Les développeurs et les architectes doivent avoir une compréhension commune de comment diviser le système et comment les composants intéragissent entre eux. L'architecture n'est pas qu'un concept technique c'est également du _social_.
+
+> The best architecture is the one that fits the business needs, not the one that mimics the tech giants (Google, Netflix, ...)