Architecture Decision Record - ADR
Document 'Why', not What
How often have you wanted to update something you did not understand? Not just the logic behind it, but the reason why someone did something exactly that way? And how many hours/days(/weeks?) it took you to finally conclude that "that stupid piece of code" was actually pretty smart and that was you, who was wrong and has wasted a lot of time?
Books (22)
Opinions (12)
Tools (11)
Cloud Design Patterns (10)
Design Patterns (9)
Library (8)
Testing (4)
System Design (4)
Microsoft's books (4)
Distributed Systems (3)
Dapr (3)
Data Storing (3)
Diagrams (2)
New Generation IDEs (2)
Project Organization (2)
Obsolete Bytes (2)
AI (2)
LLM (2)
Startup (2)
Blazor (2)
Learning (2)
Flashcards (2)
Id Series (2)
Charts (1)
Statistics (1)
Build (1)
DevOps (1)
Console (1)
Large Language Models (1)
AI Interaction (1)
Streaming (1)
Data Synchronization (1)
Algorithms (1)
Performance Optimization (1)
Microservices (1)
Event-Driven Architecture (1)
Database Design (1)
Antipatterns (1)
Mistakes (1)
Dev Life (1)
Vim (1)
API (1)
Web components (1)
Startup Books (1)
ChatGPT (1)
Non-Technical Books from a Developer's Perspective (1)
Libraries (1)
Anki (1)
Architecture (1)
Resources (1)