Perspective

This site is intended to organize the language for treating failures repeatedly observed in software development contexts not as isolated mistakes or errors in judgment, but as recurring structures.

The focus is not on judging specific technologies, methodologies, or organizational forms. Nor is it about presenting "the right way" or "how things should be."

It emphasizes making traceable how decisions have accumulated in software under operation, given incomplete assumptions and limited information.

Underlying Perspective

This site does not take a position against Agile or AI.
It considers that they become meaningful in practice only when appropriate assumptions and decision structures exist.

On the other hand, many problems that arise in practice often stem not from a lack of methodologies or tools, but from structures of assumptions, decisions, and learning not being made visible.

Therefore, this site focuses
not on "how to build,"
but on "under what assumptions decisions are being made."

The Perspective of "How It Breaks"

Failures are often treated as occurring accidentally.
In reality, however, it is not uncommon
for the same kind of failure to appear repeatedly in different forms.

What this site calls "how it breaks"
refers not to errors or failures themselves,
but to a state where they continue to recur under the same conditions.

By classifying and articulating how things break,
it becomes possible to discuss which assumptions have collapsed
without being dragged into individual incidents.

Why No Methodologies or Right Answers Are Shown

This site does not recommend specific methodologies, processes, or frameworks.
Their effectiveness varies greatly depending on context.

Instead, it aims to provide reference points for organizing how decisions and changes have been made, under what assumptions, and what outcomes they have brought.

This makes it possible to obtain a foundation for explaining and reconsidering one's own decisions, even amid constraints and situations that differ from one context to another.

About the Appendix

The concepts and vocabulary used in this site do not depend on a specific school of thought or single theory.
They are organized with reference to existing knowledge such as distributed systems, design principles, organizational learning, and control theory.

The concepts and theories that provide background are summarized in the Appendix.
They are not essential for understanding the main text, but are made available for reference according to interest.