How I Build Software
Welcome to the technical documentation for amiable.dev. This section contains Architecture Decision Records (ADRs) and contribution guidelines that demonstrate how I approach software engineering decisions.
What You'll Find Here
Architecture Decision Records (ADRs)
ADRs document significant technical decisions made during development. Each record captures:
- Context: The situation and constraints at the time
- Decision: What was chosen and why
- Consequences: Trade-offs and implications
This practice makes my decision-making process transparent and provides insight into how I think through technical problems.
Featured Decisions:
- ADR-001: Enable Docs Plugin - How this documentation section came to be
- ADR-002: GitHub Projects Showcase - Designing a portfolio page with live GitHub data
Contributing Guidelines
Information for those interested in contributing to projects, including AI attribution standards for AI-assisted content.
Why Document Decisions?
Good engineering isn't just about writing code—it's about making thoughtful decisions and being able to explain them. ADRs serve multiple purposes:
- For future me: Understanding past context when revisiting code
- For collaborators: Onboarding and understanding project history
- For recruiters/engineers: Demonstrating technical thinking beyond just code