Code Wiki¶
A structured, continuously maintained technical knowledge base covering software development concepts, tools, best practices Tips and Tricks.
This documentation is designed as a personal reference system and a long-term learning archive, with an emphasis on clarity, consistency, and practical usability.
Purpose¶
The purpose of this wiki is to:
- Centralize technical knowledge and reusable solutions
- Document practical experience and real-world implementations
- Maintain concise references for tools, frameworks, and workflows
- Support continuous learning and long-term skill development
This is not a tutorial blog, but a reference-oriented documentation system.
Scope¶
The documentation is organized by technical domains and focuses on:
Fundamentals¶
- Coding principles
- Development shortcuts
- SSH, system tools, and environment setup
- General developer utilities
Backend¶
- API design and architecture
- REST principles
- Security and best practices
- C# and .NET-related concepts
- Python principles
SQL¶
- Query patterns
- Data modeling
- Performance considerations
Frontend¶
- Core concepts
- Tooling and workflows
Docker¶
- Container fundamentals
- Installation and usage
- Common workflows and patterns
Automation & Tools¶
- Productivity tooling
- Automation concepts
- Developer utilities
How to Use This Wiki¶
- Navigation: Use the left sidebar to browse by domain
- Search: Use the search bar to quickly locate topics
- Reference-first: Pages are designed to be read non-linearly
- Copy-ready: Commands and examples are provided in copy-paste form
Content Philosophy¶
This documentation follows these principles:
- Clear separation between concepts, usage, and examples
- Minimal verbosity, maximum clarity
- Consistent structure across all pages
- Focus on practical, real-world scenarios
- Long-term maintainability over short-term trends
Audience¶
This wiki is intended for:
- Software developers
- Backend and system-oriented engineers
- Developers working with C#, Docker, SQL, and related tooling
- Anyone who prefers structured technical documentation over ad-hoc notes
Maintenance¶
This documentation is actively maintained and evolves as new topics, tools, and patterns are encountered.
Last updated: 2026-01