248 lines
8.4 KiB
JSON
248 lines
8.4 KiB
JSON
{
|
|
"category": "Culture",
|
|
"icon": "fas-lightbulb",
|
|
"skills": [
|
|
{
|
|
"id": "clean-architecture",
|
|
"name": "Clean Architecture",
|
|
"description": "Principes d'architecture logicielle visant à créer des systèmes maintenables, testables et indépendants des frameworks",
|
|
"links": [
|
|
"https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html",
|
|
"https://martinfowler.com/articles/practical-test-pyramid.html"
|
|
],
|
|
"icon": "fas-layer-group",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "ddd",
|
|
"name": "Domain Driven Design",
|
|
"description": "Approche de conception logicielle centrée sur le domaine métier et la logique métier",
|
|
"links": [
|
|
"https://martinfowler.com/bliki/DomainDrivenDesign.html",
|
|
"https://www.domainlanguage.com/ddd/"
|
|
],
|
|
"icon": "fas-sitemap",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "event-sourcing",
|
|
"name": "Event Sourcing",
|
|
"description": "Pattern d'architecture consistant à stocker tous les événements qui ont modifié l'état d'une application",
|
|
"links": [
|
|
"https://martinfowler.com/eaaDev/EventSourcing.html",
|
|
"https://eventstore.com/docs/getting-started/"
|
|
],
|
|
"icon": "fas-history",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "cqrs",
|
|
"name": "CQRS",
|
|
"description": "Command Query Responsibility Segregation - séparation des responsabilités entre lecture et écriture",
|
|
"links": [
|
|
"https://martinfowler.com/bliki/CQRS.html",
|
|
"https://docs.microsoft.com/azure/architecture/patterns/cqrs"
|
|
],
|
|
"icon": "fas-exchange-alt",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "hexagonal-architecture",
|
|
"name": "Architecture Hexagonale",
|
|
"description": "Architecture logicielle qui isole la logique métier des détails techniques et des frameworks",
|
|
"links": [
|
|
"https://alistair.cockburn.us/hexagonal-architecture/",
|
|
"https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html"
|
|
],
|
|
"icon": "fas-hexagon",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "tdd",
|
|
"name": "Test Driven Development",
|
|
"description": "Méthodologie de développement qui écrit les tests avant le code de production",
|
|
"links": [
|
|
"https://martinfowler.com/bliki/TestDrivenDevelopment.html",
|
|
"https://www.agilealliance.org/glossary/tdd/"
|
|
],
|
|
"icon": "fas-vial",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "bdd",
|
|
"name": "Behavior Driven Development",
|
|
"description": "Approche de développement qui décrit le comportement attendu en langage naturel",
|
|
"links": [
|
|
"https://cucumber.io/docs/bdd/",
|
|
"https://www.agilealliance.org/glossary/bdd/"
|
|
],
|
|
"icon": "fas-comments",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "pair-programming",
|
|
"name": "Pair Programming",
|
|
"description": "Pratique de développement où deux développeurs travaillent ensemble sur le même code",
|
|
"links": [
|
|
"https://martinfowler.com/bliki/PairProgramming.html",
|
|
"https://www.agilealliance.org/glossary/pair-programming/"
|
|
],
|
|
"icon": "fas-users",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "code-review",
|
|
"name": "Code Review",
|
|
"description": "Processus d'examen du code par d'autres développeurs pour améliorer la qualité",
|
|
"links": [
|
|
"https://martinfowler.com/articles/code-review.html",
|
|
"https://github.com/features/code-review"
|
|
],
|
|
"icon": "fas-search",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "refactoring",
|
|
"name": "Refactoring",
|
|
"description": "Restructuration du code existant pour améliorer sa lisibilité et sa maintenabilité",
|
|
"links": [
|
|
"https://refactoring.com/",
|
|
"https://martinfowler.com/books/refactoring.html"
|
|
],
|
|
"icon": "fas-tools",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "design-patterns",
|
|
"name": "Design Patterns",
|
|
"description": "Solutions réutilisables aux problèmes de conception logicielle courants",
|
|
"links": [
|
|
"https://refactoring.guru/design-patterns",
|
|
"https://www.oodesign.com/"
|
|
],
|
|
"icon": "fas-puzzle-piece",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "solid-principles",
|
|
"name": "Principes SOLID",
|
|
"description": "Cinq principes de conception orientée objet pour créer des logiciels maintenables",
|
|
"links": [
|
|
"https://en.wikipedia.org/wiki/SOLID",
|
|
"https://blog.cleancoder.com/uncle-bob/2020/10/18/SolidPrinciples.html"
|
|
],
|
|
"icon": "fas-cube",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "agile",
|
|
"name": "Méthodologies Agiles",
|
|
"description": "Approches itératives et incrémentales pour le développement de logiciels",
|
|
"links": [
|
|
"https://agilemanifesto.org/",
|
|
"https://www.agilealliance.org/"
|
|
],
|
|
"icon": "fas-running",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "scrum",
|
|
"name": "Scrum",
|
|
"description": "Framework agile pour le développement de produits complexes avec des équipes auto-organisées",
|
|
"links": [
|
|
"https://www.scrum.org/",
|
|
"https://www.scrumguides.org/"
|
|
],
|
|
"icon": "fas-sync",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "kanban",
|
|
"name": "Kanban",
|
|
"description": "Méthode de gestion du flux de travail visant à optimiser le processus de développement",
|
|
"links": [
|
|
"https://kanbanize.com/kanban-resources/getting-started/what-is-kanban",
|
|
"https://www.atlassian.com/agile/kanban"
|
|
],
|
|
"icon": "fas-columns",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "devops-culture",
|
|
"name": "Culture DevOps",
|
|
"description": "Philosophie qui favorise la collaboration entre développement et opérations",
|
|
"links": [
|
|
"https://aws.amazon.com/devops/what-is-devops/",
|
|
"https://www.atlassian.com/devops"
|
|
],
|
|
"icon": "fas-handshake",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "continuous-learning",
|
|
"name": "Apprentissage Continu",
|
|
"description": "Pratique de développement professionnel continu pour rester à jour avec les technologies",
|
|
"links": [
|
|
"https://www.thoughtworks.com/insights/blog/continuous-learning-software-development",
|
|
"https://martinfowler.com/articles/developer-productivity.html"
|
|
],
|
|
"icon": "fas-graduation-cap",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "knowledge-sharing",
|
|
"name": "Partage de Connaissances",
|
|
"description": "Pratiques de diffusion et d'échange de connaissances au sein des équipes",
|
|
"links": [
|
|
"https://www.atlassian.com/team-playbook/plays/knowledge-sharing",
|
|
"https://confluence.atlassian.com/"
|
|
],
|
|
"icon": "fas-share-alt",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "mob-programming",
|
|
"name": "Mob Programming",
|
|
"description": "Pratique où toute l'équipe travaille ensemble sur le même code en temps réel",
|
|
"links": [
|
|
"https://mobprogramming.org/",
|
|
"https://www.agilealliance.org/glossary/mob-programming/"
|
|
],
|
|
"icon": "fas-users-cog",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "technical-debt",
|
|
"name": "Dette Technique",
|
|
"description": "Coût supplémentaire futur causé par le choix d'une solution rapide plutôt qu'une meilleure approche",
|
|
"links": [
|
|
"https://martinfowler.com/bliki/TechnicalDebt.html",
|
|
"https://www.agilealliance.org/glossary/technical-debt/"
|
|
],
|
|
"icon": "fas-credit-card",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "code-quality",
|
|
"name": "Qualité du Code",
|
|
"description": "Ensemble de pratiques et métriques pour maintenir un code de haute qualité",
|
|
"links": [
|
|
"https://martinfowler.com/articles/is-quality-worth-cost.html",
|
|
"https://www.sonarqube.org/"
|
|
],
|
|
"icon": "fas-star",
|
|
"importance": "standard"
|
|
},
|
|
{
|
|
"id": "documentation",
|
|
"name": "Documentation",
|
|
"description": "Pratiques de création et maintenance de documentation technique et utilisateur",
|
|
"links": [
|
|
"https://www.atlassian.com/software/confluence",
|
|
"https://docs.github.com/"
|
|
],
|
|
"icon": "fas-book",
|
|
"importance": "standard"
|
|
}
|
|
]
|
|
} |