An experienced architect recognises a familiar pattern and proposes the solution that worked before. What are the risks, and how are they managed?

The value

Pattern recognition is most of what experience buys. Recognising that a symptom is a retry storm, a hot key, a cache stampede, a distributed monolith or constraint drift saves weeks of investigation, and the recognition is usually correct.

The risks

1. Surface similarity, different cause. Two systems with the same symptom can have different underlying problems. A growing queue may be insufficient capacity, a slow downstream dependency, oversized messages, a poison message, or an ordering constraint — and the remedies are different, with some actively harmful if misapplied.

2. Context that has changed. A solution that worked at a previous company assumed that organisation's scale, team structure, expertise and constraints. Transplanting it without checking those assumptions is the most common form of this error, and it is invisible to the person making it.

3. Confidence outrunning evidence. Rapid recognition suppresses investigation. The pattern is asserted, the team defers to experience, and nobody checks.

4. Recency and availability bias. The last serious incident shapes the next diagnosis disproportionately.

How to manage them

• State the pattern as a hypothesis with a test. "This looks like a slow-dependency queue problem; if so, workers will show high blocked time and low CPU. Let us check." That converts experience into a fast diagnosis rather than an assertion.
• Name the assumptions the previous context supplied, explicitly, and check each one here.
• Ask what would falsify it, and look for that specifically.
• Invite the team to disconfirm. Resistance frequently contains information — people close to the code know assumptions that do not hold.
• Note the near-misses. Patterns that nearly fit are the dangerous ones, because they generate confidence and a wrong remedy.

The framing

Pattern recognition should accelerate diagnosis, not replace it. The senior contribution is generating the right hypothesis quickly and the cheapest test that distinguishes it from the alternatives — the second half is what separates experience from prejudice.