concepts

Concepts

Version control

Pro Git book, first three chapters
Patterns for Managing Source Code Branches

Development process

Scrum
Kanban

Unsorted

Coding Interview University
SOLID
Abstraction principle
Software design patterns
Database normalization
Abstraction
Separation of concerns
GRASP
Unix philosophy
Worse is better
YAGNI
Dependency injection
Inversion of control
Software Architecture Guide
Catalog of Patterns of Enterprise Application Architecture
Automated Software Testing
Integration testing
Continuous Delivery
Enterprise CI/CD Best Practices
Microservices
Microservices Guide
Software Delivery Guide
Data Guide
Refactoring
12 Factor Application
Zwölf Regeln für Web- und Cloud-Anwendungen
Domain-Oriented Observability
Domain-Driven Design, DDD ressources
Domain-Driven Design Starter Modelling Process
The Bounded Context Canvas
Domain Storytelling, Domain Story Modeler
EventStorming Glossary & Cheat sheet
Behavior-Driven Development
Test-Driven Development
Package principles
Software package metrics
Layering Principles
Presentation Domain Data Layering
Consumer-driven Contract Testing
Knigge für Softwarearchitekten
Cannot Measure Productivity
Command Query Responsibility Segregation – martinfowler.com
Command Query Responsibility Segregation, Event Sourcing & co. – cqrs.com
Event Sourcing
Roca Style
Technical Writing Guide
Supply chain Levels for Software Artifacts, GitHub repo
Trunk-based Development
Database change management
Responsible Web Applications
Google DevOps Resources
The Road to Cloud Native: The Best Practices to Design and Build Cloud Native applications
Clean Code Cheat Sheet
Clean Architecture Cheat Sheet
Backends for Frontends
DORA Research Capability Catalog
DORA’s software delivery performance metrics
Five Orders of Ignorance
Business Intelligence Guidebook
Independent Systems Architecture (ISA)
Self-contained Systems
CUPID
Documentation System, documentation quadrants
Team Topologies Key Concepts
Richardson Maturity Model – steps toward the glory of REST
Zalando API Guidelines
REST APIs don’t need a versioning strategy - they need a change strategy
arc42 Quality Model
GitOps
The Four Golden Signals – Monitoring Distributed Systems, Google Site Reliability Engineering
A pattern language for microservices
Open Practice Library
- Architecture Decision Records
- Behavior-Driven Development
- Blue Green Deployments
- Burnup Chart
- Cognitive Loadometer
- Continuous Integration
- Continuous Delivery
- Continuous Deployment
- Cynefin Frfamework
- Stacey Matrix
- Domain Storytelling
- Event Modeling
- Event Storming
- Everything as Code
- Feature Toggles
- Five Whys (5 Whys)
- GROW Model for 1-2-1 Coaching
- GitOps
- Kanban
- Limit Work in Progress
- Kano Model
- Manage Flow
- Minimum Viable Product
- SWOT Analysis
- Scrum
- Stakeholder Map
- Start with Why
- Technical Debt
- Test Driven Development
- User Persona
- Value Stream Mapping
- Vision Statement
- Visualization of Work
- Weighted Shortest Job First
- Westrums Cultural Typology Assessment
- Yes And
Code is a liability (not an asset)
Organisationshandbuch: Standardwerk für organisatorische Fragestellungen des Bundesministeriums für Digitales und Staatsmodernisierung

concepts.txt · Last modified: 2026-07-21 14:54 by mrks