Introduction¶

This is the archive of Software Architect HJ. Gain ideas you can apply to your own projects through indirect experience.

What is recorded here?¶

Software architecture design and decision-making process: Covers design patterns applied in real projects and the reasons for those choices.
Personal perspectives: Shares personal viewpoints and interpretations on various aspects of development.
Productivity and development strategies: Discusses various methods to improve productivity, including teamwork and implementation strategies.

Why keep these records?¶

For personal retrospection
To systematically organize experiences and turn them into knowledge assets
To spread positive influence in the community
To share knowledge with junior developers and colleagues
To improve the developer community's understanding of architects and architecture

Why not a blog?¶

Knowledge and information do not exist in isolation — they are interconnected through similar concepts or different perspectives on the same event.

Proper use of knowledge means being able to utilize these connections; otherwise, it is mere memorization. Therefore, rather than simply recording retrospectives, it is necessary to create a network of knowledge based on relationships. In reality, this requires a lot of maintenance effort in a typical blog system. While wiki systems are somewhat similar, they are not productive enough for personal work. Thus, I built a static site using mkdocs.

All documents on this site are created in Markdown with VS Code, and are frequently updated as their interrelationships develop.

Contact and Consultation¶

If you have questions about architects or architecture, or concerns about your project, please refer to the documents below.