Software Development
Programming languages, frameworks, tools, and architecture patterns
A technical archive documenting software development, infrastructure, system design, and debugging notes.
This blog serves as a living repository for technical learning. Architecture notes, implementation details, operational trade-offs, and debugging lessons are documented here so they stay searchable and useful over time.
The archive is organized as a technical notebook: each log should explain a concrete concept, decision, failure mode, or engineering pattern clearly enough to revisit later.
Writing the logs reinforces understanding and creates a permanent record that can be reused during future builds, reviews, and troubleshooting sessions.
Programming languages, frameworks, tools, and architecture patterns
Interview questions, tricky technical prompts, reasoning paths, and worked solutions
Real problems encountered during development, debugging notes, fixes, and prevention lessons
Each post is written from implementation experience, source reading, debugging, or system analysis rather than passive note taking.
The goal is to capture the reasoning behind technical choices: what problem was being solved, which constraints mattered, what failed, and what pattern can be reused.
The frontend intentionally shows only software development content. Other draft or personal files may remain in the content folder, but they are not part of the visible archive.