Books Teach Patterns. Architects Teach Context

After years mentoring engineers and helping companies make architecture decisions, I’ve realized something simple but powerful:

The “right” advice depends on who you are… and where you are.

We love books.
We love patterns, best practices, principles, and models.
They make us better.

But every book was written from a specific place:
a certain team, a certain culture, a certain moment in time.

And that place is not yours.

That’s why two people—or two companies—can read the same chapter and walk away with completely different needs.

When mentoring, I’ve learned that people don’t need the same advice

I’ve mentored engineers who seem to face the same situation but need totally different guidance.

For example:

• One engineer over-engineers because they’re afraid of making mistakes.

• Another cuts corners because they’re overwhelmed.

• One applies best practices like if they were laws.

• Another avoids patterns because they were burned before.

• Some need more structure.

• Others need more freedom.

Same challenge on paper.
Different human on the other side.

So the advice changes.

And that’s normal.
That’s good.
That’s mentorship.

Books explain concepts.
Mentors understand people.

The same thing happens when advising companies

As architects, companies expect us to give them “the best solution.”

But the best solution is always contextual:

• team skills

• deadlines

• pressure

• risks

• legacy systems

• culture

• business priorities

You can design the most elegant architecture…
but if the company can’t maintain it, it’s not a good architecture.

Sometimes the “ideal” design creates more pain than value.

So what do we do?

• We simplify when teams are stressed.

• We make things more opinionated when alignment is weak.

• We prefer incremental changes when risk is high.

• And sometimes, we break the rules—on purpose—because the real world demands it.

Books describe perfect worlds.
Architects work in real ones.

The common thread: context changes everything

Whether advising a junior developer or helping a business decide its next architecture step, the pattern is the same:

Good decisions come from understanding context, not from memorizing best practices.

Patterns are tools.
Principles are guides.
Books give us a starting point.

But judgment…
that’s where the real craft is.

Because the perfectionist may need to relax.
And the rushed team may need to slow down.
And the company obsessed with speed may need a more solid foundation.
And the company stuck in analysis may need to ship something now.

Same problem.
Different system.
Different answer.

The human side of technical leadership

At the end of the day:

Books teach us what can work.
Architects and mentors help people find what will work for them.

That’s why context matters.
And that’s why our role exists.

Because technology moves fast, but humans and companies grow through understanding.