Food prices are up. Quality is down. You already know that if you’ve bought fruit in the last year.

And at some point, the thought crosses your mind that you could probably do better yourself. You can.

That part is true.

The best peaches I’ve ever had didn’t come from a store. They came from a school garden on Orcas Island. Same with tomatoes, greens, berries. When it’s grown well and picked at the right time, it’s not even close. Store-bought stops being the reference point.

The question isn’t whether you can grow better food. It’s how most people go about it.

They start fast. Buy plants, build beds, move soil around, try to piece something together from whatever advice they can find on social media. Some of it works. Most of it doesn’t. It turns into more effort and expense than it should be, or it quietly underperforms, then fades back into a lawn.

Not because growing food is complicated.

Because they rushed into it without a plan and tried to piece it together from incomplete and untested information.

A former colleague at Microsoft used to say: “If you got time to do it twice, you got time to do it right the first time.” It’s dead on.

This series is for people who want to do it right. Whether it’s your first attempt or your third, whether you’re working with a small yard or something larger, the goal is the same: build something that produces consistently, without constant correction.

You can take this as far as you want. You can spend a lot of money, build out infrastructure, turn it into a full project. That’s one path. Or you can treat it as a system. Something designed around your site, your conditions, and what actually works there. That’s where you start getting real return—not just in yield, but in time, in effort, and in the quality of what you’re producing.

Before we go much further, this is about where you stop reading for a minute and go outside.

You’re not going to figure this out from a chair. Not from a map, not from memory, and not from what you think the space is doing. You need to be in it.

Put your boots on. Bring a shovel. Bring your kids. Walk the ground.

You’re not designing yet. You’re getting to know the place the way it actually behaves. Where it collects water, where it dries out, where things grow easily and where they don’t. You’re looking for patterns you won’t see unless you’re standing there.

If you do this right, you’ll start to see your site differently. Not just as a yard or a piece of land, but as something with structure, limits, and potential.

That’s what this step is for: Understanding the Site Before You Change It

Site Assessment: Boots on the Ground

Before you check anything, slow it down. There are things you need to see, touch, smell, hear, and analyze first.

Every property has patterns you won’t see in a single afternoon, week, or month. Water movement, frost pockets, wind exposure, where the sun actually lands over the course of a season. If you’ve lived on the landscape for a while, you’ve already seen some of this.

If you haven’t, you can still move forward. You just need to fill in the gaps.

Talk to the previous owner if you can. Ask neighbors what they’ve noticed over time. Look for physical signs. Water marks, erosion, leaning trees, bare patches, valleys of soil deposition. Use tools if they help. Sun tracking apps, weather history, county GIS data, anything that gives you a clearer picture of how the site behaves beyond the moment you’re standing in it.

You’re not trying to predict everything.

But you are trying to avoid being surprised by something that happens every year.

Flooding, drought, animal movement, seasonal winds. These are patterns. If you ignore them now, they tend to show up later, usually after you’ve already put time and money into the ground.

Once you have a basic read on the site, you can start checking whether it’s workable.

Before you go further, take a look at what it actually takes to make a site produce food.

Because most spaces don’t start there. You bring them there.

Sometimes that’s simple. Sometimes it isn’t. It might mean fencing to keep animals out, running water where there isn’t any, working around shallow or rocky soil, or opening up space that’s been shaded or neglected for years.

None of this is unusual. But it does cost time, and it usually costs money.

If you’ve ever priced out deer fencing, you already know how fast that adds up. And that’s before you plant anything.

You don’t need to overthink it. Just don’t expect the first season to pay for the setup. What you’re building here is something that works over time, not something that turns a profit right away.

So instead of jumping ahead to design, start with a simpler check.

Walk the site and see what’s already in place, and what isn’t.

There are a handful of things that matter more than the rest. If those are there, or close enough that you can put them in without a fight, you’re in good shape.

If they’re missing, that’s where your effort goes first.

The Things That Matter

1. Protection — Can You Keep It Safe and Alive?

Start with the obvious question:

What’s going to eat this before you do?

In most areas, that means vertebrates: deer and rabbits. Sometimes it’s people. If they have access, they’ll use it.

You don’t need to account for everything yet. Birds and smaller pressures come later. Right now, focus on the animals that can wipe things out overnight. Without a proper fence, they will.

In my experience, fencing is the only reliable option, but it comes with constraints.

• Some HOAs restrict orchard style fencing entirely, or limit height

• Deer fencing typically needs to be at least six feet, often eight depending on pressure. If rabbits are an issue, rabbit guard on the bottom is recommended

• Rocky or shallow soil can make post installation difficult and expensive

• In our area, finding someone reliable to do installation is a problem to solve

• A structurally sound fence that looks good is expensive

These aren’t edge cases. They show up often.

Natural vegetative barriers aren’t reliable not matter what TikTok tells you. Dense planting, hedges, brush—deer move through all of it.

If you’re fencing, keep it simple and controlled.

• Fewer entry points. You should only need one. Make sure it’s wide enough for machinery to pass through.

• Gates that close on a spring, cleanly

• No easy or tempting gaps. You don’t want to rescue a stuck animal.

The weak point is always the gate. It gets left open once, that’s enough to hurt.

You don’t need to build it yet. But you should know if it’s possible, what it will take, and whether the site supports it.

If you can’t protect your food, don’t plant it yet. Optimism, deer spray, soap bars, sprinklers will not keep them away.

Once you know you can protect your food, the next question is whether you can support it.

2. Water — Can You Support It Through Summer?

Next question:

Can you keep things alive when it actually matters?

Water isn’t usually a problem in spring. It shows up in the middle of summer, when everything is dry and plants are under stress.

That’s the condition you plan for.

Start by identifying your source.

• well

• city supply

• surface water (pond, creek, stored water)

Any of these can work, and work way better with a mulch strategy. The question is whether they hold up when demand is highest.

Wells are the one to pay attention to.

Some produce steadily year-round. Others drop off in summer or only deliver a limited flow rate. That matters more than people expect, because that’s exactly when your system needs the most water.

You don’t need exact calculations yet, but you should know:

• does the well slow down in dry months

• is there a known gallons-per-minute limit

• has it ever run low

If you don’t know, it’s worth finding out.

If supply is uncertain, storage becomes part of the solution.

A lot of systems rely on stored water. Tanks, cisterns, or even simple setups that give you a buffer when supply drops. You’re not creating water, just holding it so you’re not dependent on real-time flow.

Running out of water in peak summer is one of the faster ways to lose a system.

Also check reach.

• Can you get water to where you plan to grow?

• How far is the source?

• Will pressure hold at that distance?

This is usually solvable, but it’s better to see it early than fight it later.

You don’t need to test water quality at this stage. If it’s safe for you, it’s fine for plants.

The goal here is simple:

Make sure you have enough water, in the right place, at the time of year it’s needed most.

After that, it comes down to what the site can actually produce.

3. Sunlight — What Can This Site Actually Produce?

Next question:

What can this space actually support?

Sunlight sets the ceiling. You can work around soil, you can bring in water, you can build protection. You can’t create more sun.

Start with a simple baseline.

Most productive plants need at least half a day of direct summer sun. More is better. Less than that, and your species options narrow quickly.

Don’t guess. Check it.

Watch where the light actually lands over the course of a day. Make note of it. This will factor in to where you plant. Morning and afternoon both matter. A spot that looks bright at noon might only get a short window of direct sun.

Also pay attention to what’s creating shade.

• trees

• neighboring structures

• your own house

And remember, this changes over time.

Summer sun sits higher. Winter sun drops lower. Deciduous trees open up in winter and close in during the growing season. If you’re only looking once, it’s easy to misread the space.

If you’re unsure, use a sun tracking tool and map it out. It doesn’t need to be perfect, but you should have a realistic sense of how many hours of direct light you’re getting in different areas starting in the Light Surge phase of planting.

Then match expectations to reality.

• full sun areas → fruit trees, most vegetables

• partial sun → berries, some greens

• heavy shade → limited production without major changes

You can open up light by removing trees, limbs, or structures, but that’s a separate decision with its own cost.

For now, just answer the question:

Where do you actually have usable sun, and where don’t you?

Because that determines what belongs there before you plant anything.

Then you check what it’s growing in.

4. Soil — Can Anything Root Here?

Now you get a shovel in the ground.

Up to this point, you’ve mostly been observing. This is where you start testing things directly.

You’re not looking at nutrients or pH yet. That comes later if needed. Right now, you’re looking at structure, depth, and how the soil behaves.

Dig several test holes, not just one.

Different parts of the site can vary more than people expect. A spot that looks the same from the surface can be completely different a few feet over.

As you dig, pay attention to a few things:

• Depth — how far down can you go before hitting rock, hardpan, or dense clay

• Resistance — does the shovel move easily, or are you fighting it

• Composition — sand, silt, clay, or a mix

• Moisture — holding water, draining, or dry

You don’t need to classify it perfectly, but you should be able to tell the difference between sandy, rocky, and heavy clay soils.

In an ideal case, you’ve got a balance of sand, silt, and clay. In reality, you work with what’s there.

Some variation is fine. Most soils can be improved over time.

But there are limits.

Shallow soil over rock, dense compacted layers, or areas that stay saturated can restrict what you can grow, especially for trees and larger perennials.

You can work around those conditions, but you should know where they are before you decide what goes where.

If you’re unsure about drainage, do a simple test.

Fill the hole with water and see how long it takes to drain. That gives you a quick read on whether water moves through the soil or tends to sit.

The goal here isn’t to fix anything yet.

It’s to answer a basic question:

Do you have usable soil at a depth that supports what you want to grow?

If not, you’re either improving it over time or designing around it.

And finally, you account for what might limit you before you even start.

5. Constraints — What Could Stop This Before It Starts?

Last check:

What limits are already in place?

Some of these are obvious. Others only show up after you’ve started digging, and by then they’re a problem.

Start with what you can’t ignore.

• Utility lines — before you dig anything, you need to know what’s in the ground
  Water, gas, electric, septic. Hitting one of these isn’t a small mistake. It stops work immediately and can get expensive fast. Call 811 before you dig. Always.

Then look at external restrictions.

• HOA rules — fencing, structures, visibility

• local regulations — setbacks, height limits, water use

• property lines — where you can and can’t build

These shape what’s possible whether you like them or not.

There are also less obvious constraints.

Not common, but real.

I’ve seen two separate projects—one in Texas, one on Orcas Island—where digging uncovered human remains. Work stopped immediately and stayed that way for months while it was sorted out.

Most sites won’t have that kind of history. But once you start disturbing ground, you’re working with whatever’s there, not just what you expected.

Then there are practical limits.

• budget — what you can afford to build now vs later. You’ll want infrastructure first.

• materials — what’s available locally

• time — what you can realistically maintain

You can work around most of these, but they don’t go away.

The goal here isn’t to solve everything.

It’s to see the boundaries clearly, so you don’t run into them halfway through the work.

Keep Going. Step by Step.

At this point, you’ve already done more than most people ever do.

You’ve walked the ground, looked at how it actually behaves, and started to see where things will work and where they won’t. That alone puts you ahead of the usual trial-and-error approach.

You don’t need perfect conditions. You don’t need to solve everything yet.

You just need a clear read on what you’re working with.

From here, problems don’t go away, but they stop being surprises. You start to see them early, and when you see them early, you can design around them instead of reacting after the fact.

That’s where this starts to come together.

The next step is deciding what you’re actually building, and where it goes.

This is where most people get it wrong. Not because they don’t have good ideas, but because they try to force those ideas onto a site that doesn’t support them.

We’re going to do the opposite.

We’ll take what you’ve just seen—water, light, soil, pressure—and use it to shape a system that fits the space and holds together over time.

And this is where the cost of doing it wrong starts to show up, and where doing it right starts to pay off.

The next step is planning and design—taking what you’ve just seen and turning it into defense-first design that really works on your site. That’s where we go next.

This first step is free. The rest of the series—design, installation, management, and and getting yield, is available to paid subscribers.

If you do this well, it becomes something you build on, enjoy, and pass on, not something you keep fixing and putting money into.

What’s more interesting isn’t that I haven’t used fertilizer. It’s that I’ve rarely found a situation where it actually made sense to.

What I see every spring is a kind of reflex. Fertilizer panic shows up all over social media, numbers and bad advice get discussed, and trees get fed because that’s what you’re supposed to do this time of year. The assumption is simple: if the tree is going to grow, produce, or stay healthy, it must need something added to the soil. That’s pure projection. That’s dangerous for our non-human neighbors.

People tend to treat trees the way they understand care in their own lives—if something is living, you feed it, you support it, you intervene to keep it healthy. That instinct works for domesticated animals, for gardens, for things that depend on regular input. But a tree isn’t a dependent system in that way. It’s adapted to operate within constraints, to regulate its own growth based on conditions, not continuous support. When we project our version of care onto it, we end up intervening where it doesn’t help, and often where it creates new problems. Over-pruning is a great example.

This tendency made us targets.

Sold on a fertilizer system that doesn’t fit the home orchardist

The N–P–K fertilizer model, nitrogen, phosphorus, potassium, comes out of agricultural chemistry. It was built to simplify plant nutrition into something measurable, repeatable, and scalable. In large production systems, that made sense. You needed predictable inputs, and those three nutrients were the ones most likely to limit yield.

But that model didn’t stay in agriculture.

As fertilizers became widely available, the same simplified logic was packaged and sold for home use. Three numbers on a bag, a sense of balance, a clear prescription. It’s easy to understand, easy to apply, and it gives the impression that you’re doing something precise and necessary.

And it was marketed that way, consistently. Healthy lawns, perfect trees, clean, controlled landscapes. The message is subtle but persistent: growth and health come from adding the right product. If something looks off, you’re missing an input. If you want better results, you apply more of the right thing.

Over time, that becomes the default way of thinking. Not because people have studied soil systems, but because they’ve been shown, repeatedly, what “care” is supposed to look like. The model is simple, the messaging is constant, and the alternative, doing nothing, feels like neglect.

So it persists. Not because it’s always correct, but because it’s easy, familiar, and removes just enough uncertainty to act. And once that habit is in place, it carries itself forward, season after season, whether the system actually needs it or not.

Applying NPK to solve a problem that isn’t there

Most of the time, no one has tested the soil, no one knows what’s actually present or available, and no one has defined a specific problem they’re trying to solve. The decision starts with a product, not a condition. And once you start there, everything else becomes guesswork dressed up as care.

The strange part is how confident it feels. The numbers on the bag—N, P, K—give the impression of precision. It looks measured, balanced, even scientific. But those numbers only describe what’s in the bag. They don’t describe your soil, your site, or your tree. They don’t tell you what’s already there, what’s accessible, or what’s limiting growth in the first place.

So what you end up with is a very specific input being applied to a system that hasn’t been observed, measured, or understood. And that’s where most of the problems begin.

Underneath all of this are two assumptions that almost no one questions. The first is that fertilizer is what keeps a tree healthy. The second is that more nutrients lead to more fruit.

Both sound reasonable. Both are wrong often enough to cause problems.

Fertilizer, especially nitrogen, doesn’t create health. It pushes growth. And those are not the same thing. A tree can be growing aggressively and still be structurally weak, more susceptible to disease, and less productive over time. In fact, that’s a common outcome when growth is pushed without regard for the conditions supporting it.

The same goes for production. A well-fed tree doesn’t prioritize fruit. It prioritizes expansion—more shoots, more leaves, more structure. Fruit tends to come when growth slows and the system stabilizes, not when it’s being pushed forward.

So the logic most people are operating on—feed the tree to make it healthier and more productive—starts from a misunderstanding of what fertilizer actually does, not how a tree works and what it needs.

Do your trees really need fertilizer?

Most trees don’t need fertilizer, especially once they’re established and growing in reasonably intact soil. If the tree is putting on steady growth, holding healthy leaf color, and not showing clear deficiency symptoms, adding fertilizer is unlikely to improve anything and often makes things worse. Where it can make sense is at the margins: newly planted trees in poor or disturbed soil, sites where topsoil has been stripped or compacted, or situations where a specific deficiency has been identified through testing or clear symptoms. Outside of those cases, fertilizer is usually being applied without a defined problem, which makes it a guess, not a solution.

What matters more is whether the system supporting the tree is functioning. A fruit tree isn’t responding to inputs in isolation, it’s responding to conditions. Roots need access to oxygen. Soil biology has to be active enough to cycle nutrients into usable forms. Water has to move through the soil without pooling or disappearing too quickly. And growth needs to stay in balance, not constantly pushed into excess. When those conditions are in place, trees tend to regulate themselves. When they’re not, fertilizer doesn’t fix the problem, it just pushes growth on top of it.

At a practical level, those conditions come down to four things:

1. Oxygen in the root zone
Roots need air as much as water. If the soil is compacted or stays saturated, roots can’t function properly, no matter how much fertilizer is present.

2. Active soil biology
The tree doesn’t pull nutrients directly from the soil. Microbes and fungi convert and move nutrients into forms the tree can actually use. Without that activity, nutrients can be present but unavailable.

3. Water moving correctly
Not too much, not too little, and not stagnant. The soil has to hold moisture while still draining and allowing air in. Most water problems are really structure problems.

4. Balanced growth
A healthy tree grows steadily, not aggressively. Excessive, fast growth usually means the system is being pushed, often at the expense of strength, resilience, and fruiting.

That’s the system. If one of those is off, adding fertilizer won’t fix it. It just pushes the tree harder inside a system that isn’t working properly.

How Do You Know the System Is Functioning Properly?

You don’t need a lab test to get a read on this. Most of it is visible if you know what to look for. A tree in a functioning system shows steady, moderate growth and consistent leaf color through the season. Its reproductive cycle is also a useful signal. It flowers and sets fruit in a way that’s proportionate to its age and stage, not excessively vegetative and not completely stalled.

You’ll also see a baseline level of resilience. The tree can tolerate normal environmental stress and routine pathogen exposure without significant decline. Its defensive responses are intact. That doesn’t mean it’s immune to serious diseases or that it won’t ever fail under pressure. Some diseases can overwhelm even well-supported trees. But in a functioning system, the tree is not constantly struggling, and minor issues don’t escalate into chronic problems.

Water moves through the soil without pooling, and the ground under the tree doesn’t feel lifeless or bare. Taken together, it looks stable rather than reactive, with fewer swings between stress and overgrowth.

If It’s Not Functioning, What Actually Fixes It?

This is where most people reach for fertilizer, because it’s the simplest lever available. Add something, expect a response.

But if the issue is oxygen, biology, or water movement, adding nutrients doesn’t correct any of those. It just pushes growth inside a system that’s already underperforming.

What actually fixes it is structural.

You’re not adding inputs. You’re changing the conditions the tree is growing in. That means improving how the soil holds air and water, building biological activity that can cycle nutrients properly, and covering the ground so the system can regulate itself instead of constantly resetting.

There’s a way to do that deliberately, using a small group of plants and materials that work together around the tree. Done properly, it replaces the need for fertilizer almost entirely and reduces the amount of intervention over time.

That’s the part most people never see, because it doesn’t come in a bag.

If you want to understand what that system actually looks like, and how to build it in a way that supports the tree instead of competing with it, that’s where we go next. And it will save you money, time, and effort.

Read more

This is where landscape enters, not as backdrop, not as scenery, but as orientation.

Some places don’t inspire us so much as they steady us. They don’t ask to be improved or explained. They remain. Over time, people begin to return to them without needing to say why. Children find them. Adults recognize them. Elders measure time by them. The place does the remembering when we can’t.

Landscape, in this sense, is not about beauty or rarity. It is about position. About knowing where you stand before deciding what to do next.

Sometimes orientation is not a landscape you can walk through. Sometimes it is the only living thing you can see.

A Tree Through an Attic Slot

Anne Frank was born in Frankfurt and grew up in a Europe that tightened around her year by year. By the time her family fled to Amsterdam, Jewish life had already become conditional—work restricted, schools separated, movement narrowed. When the German occupation followed them into the Netherlands, those conditions hardened into orders. Registration. Curfews. Identification. Deportations that began quietly and did not stay quiet.

In 1942, when Anne’s older sister Margot received a summons to report for a labor camp, the family did not debate philosophy or fate. They disappeared.

They moved into a concealed space behind the offices of Otto Frank’s business—rooms hidden by a bookcase, stacked above storage and work floors, cut off from the street they had once walked freely. The decision was not dramatic. It was logistical. Stay visible and be taken, or vanish and hope time behaved differently than the authorities predicted.

That is how Anne arrived at the attic. Not by accident. Not by symbolism.

By calculation under pressure.

One Tree was Enough

The attic was hot in summer and sharp-edged in winter. The air never quite moved. The stairs were steep and memorized by touch. Every sound had to be weighed before it was made. Even standing carried risk. You learned where your feet could land without announcing you. From that space, Anne Frank could see almost nothing of the outside world. Not the street. Not the canal. Not the ground. Just rooftops pressing close and a narrow opening of sky.

And a tree.

“As long as this exists, this sunshine and this cloudless sky, while this lasts, I cannot be unhappy.”

A horse chestnut stood in the courtyard beyond the buildings. Far enough away to be unreachable. Close enough to watch. It rose past the brick like it didn’t know the walls were there.

She noticed it the way you notice the only thing that still behaves normally. She noticed when the branches filled in. When the leaves dropped. When birds returned. When light caught differently on the bark.

“Our chestnut tree in the courtyard is in full bloom. It’s covered with leaves and is even more beautiful than last year.”

These weren’t reflections. They were observations. Notes taken by someone whose own movement had been stripped down to almost nothing. It gave her continuity.

Inside the attic, days lost their edges. Time stopped arriving cleanly. The rules kept changing. People vanished without explanation. Fear had no schedule. Everything felt conditional.

The tree wasn’t.

It didn’t speed up. It didn’t hesitate. It didn’t respond to danger. It followed seasons because seasons were still happening, whether anyone could participate in them or not.

She wrote about the tree because it was still part of the world, a world that had not collapsed entirely into rooms and whispers. It gave her a fixed reference outside the hiding place, something that didn’t require permission to exist.

The tree didn’t comfort her. It didn’t offer escape. It didn’t suggest a future.

It did something smaller and more necessary. It told the truth about where she was.

Orientation doesn’t save you. It keeps you from dissolving.

The tree outlived her. That’s not a moral. It’s a fact. But while she was there, while the attic pressed inward and time lost coherence, that tree remained visible, legible, indifferent, alive.

One tree was enough. Not to fix anything. To locate her inside a world that was trying, methodically, to erase her position within it.

Staying as Orientation

The cut was small. A nick from shaving, barely worth remarking on. Something that shouldn’t have mattered, something that would have healed if medicine had learned how to listen sooner. Instead, it darkened. Tightened. The jaw locked. Breathing became work. Days stretched thin and then snapped.

Henry Thoreau did not leave the room. He wasn’t losing a nation, an identity, an idea.

He was losing his brother.

He sat with John while the body failed in increments: muscle by muscle, hour by hour, until speech went, then swallowing, then sleep. There was no argument to win, no intervention that mattered. Just the mechanics of dying, unfolding at home, in the town where they had grown up, where paths were known and days had always returned to them both.

When it was over, nothing else changed, and Concord did not notice.

The road outside still ran where it always had. The river kept its bends. Morning came on schedule. People went to work. Bells rang. The ground did not register what had been lost. That was the most difficult part.

Motion did not help.

Leaving did not help.

John’s death created a hole that movement could not fill.

So Thoreau stayed, because he knew orientation is not knowing what to do.

It is knowing where you are while you don’t know.

The pond lay a short distance from town. Close enough that the day still reached it unchanged. Far enough that the noise thinned before he arrived. He walked there because it was where his body ended up when he stopped trying to decide.

In winter, the surface was hard. Not evenly. Not reliably. He learned where to step and where not to. Learned how far his weight carried. Learned how much attention it required simply to remain upright. The ice did not instruct him. It registered him as he was now, not as he was the year before. Each morning, he found out where he was by standing on it.

This was what staying gave him.

After John died, his sense of position had failed. Not direction — position. He could move, but movement no longer told him anything. Roads did not orient him. Time did not orient him. Thought only widened the gap between where he stood and what had happened.

At the pond, that gap became measurable.

He returned because the place did not move with him. The shoreline remained where it had been the day before. The break in the ice returned to the same place. Light crossed the surface at roughly the same hour. Even when nothing made sense, these relationships held.

John was gone. The pond was still here.

That contrast did not resolve anything, but it allowed him to locate himself inside it. Not as explanation. As fact.

When thought failed, his body did what bodies do. He split wood. He ate when hunger arrived. He slept when the cold made it necessary. These were not rituals. They were checks. Each one answered a single question: are you still here.

The place answered back by remaining.

Over time, memory loosened its grip. Not because it faded, but because it no longer had to carry the burden of orientation alone. The pond held that burden too. It marked the day without asking him to interpret it. It allowed him to stand somewhere long enough for his internal bearings to re-form.

Later, when he surveyed land for others, the same need followed him. Claims drawn cleanly on paper failed when they reached water or slope. He learned to trust position before conclusion. To locate himself before asserting anything else. Accuracy came not from confidence, but from return.

That order stayed with him.

When he wrote, it was not to resolve what had happened to John. It was to avoid losing his place again. Sentences were tested against days that had already proven themselves. He stopped when words began to outrun what he could still stand inside. Writing did not move him forward.

It kept him oriented.

The pond continued to do its quiet work. Winter ended unevenly. Ice broke where it always did. Spring arrived without explanation. He did not ask it for one. He only needed to know where he was when the day changed.

This was not retreat. It was re-establishing position.

People would later say Henry David Thoreau went to the woods for ideas, or solitude, or clarity. That version mistakes orientation for insight. He stayed because staying was how he learned where he was again, after losing that knowledge completely.

The landscape did not tell him what to do next. It told him where he stood while he didn’t know.

That was enough.

The Nameless Fir That Orients Generations

A fir stands alone at the edge of Cascade lake on Orcas Island, leaning out over the water like it wants to be there. It appears in photographs from the early twentieth century, already mature, already angled, already doing the same quiet work it does now. The posture hasn’t changed. The world has. People have.

It’s summer. Towels are piled on a log. Kids circle the tree like gravity is warming up.

A girl hangs back, watching her brother climb. He makes it look easy—always does. Bare feet finding holds polished smooth by decades of use. He doesn’t look down. He never does. He looks out. When he jumps, there’s a clean pause, a sharp intake of breath from the shore, then the sound of water breaking and the immediate laughter that means he’s fine.

She hadn’t planned to climb. Not today. But standing there feels worse than the height would.

The bark is warm. Sap sticks to her fingers. Halfway up, doubt arrives late and loud. The water looks farther now. The voices below flatten into noise. For a moment she considers climbing back down and living with that version of herself instead.

Someone calls her name. Not encouragement. Just recognition.

She goes further.

At the edge, there’s no time left to negotiate. The lake smells like summer and cold. Fear tightens, then releases. She jumps.

When she comes up, hair in her face, she’s laughing too hard to speak. Pride. Someone cheers. Someone claps. Her brother grins like this was always inevitable.

She doesn’t say anything. She doesn’t need to.

The tree has done its work.

Children climb it and jump. So did their parents. So did their grandparents.

There are accounts of great-grandfathers doing the same in the 1920s, not as legend, but as casual fact, offhand proof that this was already a place you went to test yourself. The tree didn’t host an event. It didn’t mark a boundary. It offered a choice: climb, hesitate, jump, or climb back down. That choice repeated, generation after generation.

Artists painted it because it held stories and shape.

No plaque explains it. No fence protects it. No one owns it. That’s why it works.

The fir doesn’t orient people by instruction. It orients them by return. People don’t come to remember one thing. They come to confirm that something still holds. That courage still feels the same in the body. That water is still cold. That fear still tightens the chest at the same height above the lake.

This is orientation across time.

Not memory preserved in text or monument, but memory carried forward through use. The tree anchors sentences rather than maps. That’s where we jumped. That’s where your grandfather climbed. That’s where it still leans. That’s where she grew up.

If the tree were gone tomorrow, no one would say they lost a landmark. They would say, that’s where… and trail off.

That unfinished sentence is the measure of its importance.

Position

They did not offer answers. They did not point forward.

The tree outside the attic window. The pond that held its shape while grief did not. The fir leaning over cold water, unchanged while generations tested themselves against it. Each of them did the same quieter work. They made it possible to know where you were when knowing what to do was impossible.

They did not resolve anything. One marked the passing of days when days had lost their edges. One allowed a man to remain located inside loss without turning it into motion. One gathered bodies back to the same height, the same fear, the same leap, decade after decade. Different conditions. Same function.

They held position while lives moved through them.

We live inside acceleration now. Most of it demands response. Much of it rewards motion whether it earns it or not. In that environment, orientation is easily mistaken for progress, and movement for meaning.

What these places demonstrate—without instruction, without argument—is that orientation comes first. Something must remain still long enough for a person to arrive there, locate themselves inside what has happened, and only then decide what movement, if any, is honest.

Not to be saved.

Not to be inspired.

To know where you are standing before you leave it.

Not a complete failure. Just enough fruit to suggest the system was breaking somewhere you couldn’t see. Yes, the system.

I approached it the way I usually do, starting with the simplest explanation first. Call it Occam’s Razor if you want, but it’s just a way of not overthinking the obvious. Weather. Cold snaps during bloom. Rain that keeps bees grounded. A compressed spring that forces everything open at once. All plausible. None of it explained why this small orchard had produced reliably for years and then stopped.

So we stepped back and asked a better question. What changed.

Boom. Here it was.

A crabapple had been removed the year prior. It had stood off the main plantings as an ornamental. Old, overgrown, nothing special to look at. It came out as part of landscape crew cleanup. Yes, that happens way too much. At the time, it didn’t register as important. He trusted the crew.

But that tree had been carrying more than anyone realized.

In apple systems, pollination isn’t guaranteed by proximity. It depends on timing. Each variety blooms within a defined window, often referred to as a flowering group. Some open early, some mid-season, some late. Those windows have to overlap for pollen to move between trees and for fruit to set. If two trees bloom at different times, sometimes by even a few days, they might as well be isolated.

The crabapple had been bridging that gap. I call it a pollination engine.

Most crabapples produce heavy, extended bloom and viable pollen across a wider window than many dessert varieties. It was functioning as a pollination engine, covering multiple flowering groups without anyone needing to think about it.

Once it was removed, the remaining trees were left to rely on each other. If their bloom periods did not overlap, there would be no exchange, regardless of how healthy the trees looked or how active the bees were.

We didn’t know the varieties. The trees were too old to identify reliably. So instead of guessing, we rebuilt the timing. A crabapple was reintroduced into the system, positioned to restore overlap across the bloom window.

The following season, the crop returned.

Nothing about the trees themselves had changed. The structure of pollination had.

This is the part most planting schemes miss. Apples aren’t just selected for flavor or harvest time. They are selected for when they flower, and whether that timing aligns with something else in the system. That alignment isn’t incidental. It is the difference between blossom and fruit.

This is what modern tags reduce to a number.

The Flowering Groups: 1 through 7

It sounds bureaucratic. It isn’t. It’s a record of centuries of watching.

A Group 6 tree won’t wait for a Group 2. Their blossoms will never meet. There will be no quiet dusting of pollen, no swelling ovary turning toward fruit.

There will only be leaves. And leaves don’t feed you.

If you want apples in a yard today, real apples, not decorative promise, you’re stepping into that same cold arithmetic.

Two trees standing together like friends may look intentional. They may even flower beautifully. But if they bloom out of sync, or bloom without genetic difference, the air will carry nothing of consequence between them.

No exchange. No fertilization. No harvest.

Plant different varieties. Match their flowering groups. And consider a crabapple—riotous with blossom, generous with pollen—as a kind of anchor tree. In English orchards they were planted not for prestige but for reliability. A cloud of bloom against uncertainty.

An orchard has always been choreography against risk.

The blossoms are fragile. The bees are brief. Frost is indifferent.

Fruit belongs to those who design for overlap.

Weather Dependence in Flowering

Bloom timing isn’t fixed to a calendar. It’s negotiated with weather. A warm spell in late March can push early varieties open before the risk of frost has passed. A cold, delayed spring can compress bloom windows, forcing early and mid-season trees to flower almost at once. Extended rain can quiet bee flight just when pollen needs to move. Heat can rush petals open and shut them again in days. The orchard lives inside these fluctuations. Flowering groups give you structure—but weather is the variable that tests whether your overlap was designed with enough margin to survive it.

For the Casual Home Orchardist

The nursery won’t talk about it. Some don’t even know about it. They’ll sell you two varieties that will never speak the same flowering language.

You’ll watch both trees bloom and assume everything’s fine. Blossoms everywhere. Bees moving through. It looks productive. But if one opened a week earlier and the other followed after the pollen window closed, they might as well be in different states.

Nurseries label for flavor, color, and harvest time. They rarely emphasize bloom timing--flowering group, overlap, compatibility. You can walk out with two healthy, beautiful, entirely incompatible trees. They’ll grow. They’ll leaf. They may never fruit.

If you’re planting one or two trees, you don’t get redundancy. Every tree has to work. Before you fall for the name on the tag, ask one question: When does it bloom?

Fruit isn’t guaranteed by proximity. It’s secured by overlap. Know the bloom period so you’re not standing there wondering why there’s no fruit.

Read more

My grandfather died at sixty-seven. Too young. I know him mostly through stories, the kind of half-mythic anecdotes families hand down like worn tools: the three acres he cultivated during the war, the starving neighbors he fed, the angora rabbits, pigs, chickens, and geese he raised. But I never got to stand beside him in a garden. He never taught me first-hand how to graft, prune, or plant. Maybe he wanted to. Who wouldn’t want to pass on what kept them alive?—but time ran out six months after I arrived.

My father died even younger. Fifty-seven. He lasted that long only because he walked miles every day as a mail carrier, out in the weather, moving, breathing, living by necessity the kind of life modern people now have to engineer. That’s the part that haunts me: they were both outdoor men, but their bodies still had limits. They never got the quiet years. They never got to become the elders who show the rest of us how the seasons work. It’s instead carried by blood, and that feels distant but good enough.

So yes, when my mom asks why I’m up before dawn gathering winter lettuce in a gale for something as unromantic as a smoothie, I don’t hesitate. This is the work of staying here. This is the price of longevity. This is me refusing the inheritance of early endings.

And as I sit there, talking to her, the wind filling in the background like an insistent witness, I think about something else, something she never had to say out loud:

Our ancestors didn’t eat well in winter because they were virtuous. They ate well in winter because they prepared. And they survived because they didn’t pretend summer would rescue them.

But there were cultures who went further than preparation—cultures who turned the winter itself into a season of abundance. Not scarcity. Not struggle. Abundance.

And that’s where Part 2 truly begins.

Read more

Read more

I drove out on a clear day on Orcas Island—cool, bright, restrained. The sun wasn’t warming anything yet. It was just showing what was there.

I’d been here before, years ago, walking these same trees for a preservation orchard project. Coming back felt less like a retu…

Read more

I woke this morning and soon realized I was out of Aronia for my smoothie. I fingered through the fridge vegetable drawers. Nothing but a shriveled peach from an Orcas summer gone by. I went outside without a prayer, knowing I had already picked my shrubs clean of the deep purple temperate berry that is the cornerstone nutrient of my mornings. I debated having my smoothie without it. When I saw no greens either, I got in my truck and drove to a nearby food forest I built years ago. Loaded. I thanked myself for planting so many.

I began filling my coffers with the nutrient gold. Aronia’s nutrient profile reads like the fountain of youth. Blueberries? Cute. Losers compared to Aronia’s anthocyanin load. I’m freezing them today. I don’t want to repeat this in December.

That’s the thing about Aronia, or chokeberry. It doesn’t just sit pretty in the shrub layer of a food forest landscape. It shows up, takes over the neglected corners of your land, and hands you back fruit that could anchor a diet, a pantry, or a medicine chest. This isn’t an ornamental hedge. It’s survival dressed up in autumn fire.

Aronia’s Position in the Edible Landscape Design

Aronia is a middle-tier shrub in a food forest or edible landscape design, thriving between canopy and groundcover. It fills the sunlight gaps beneath fruit trees, works beautifully as a hedge or border, and tolerates wet spots that usually get ignored. Use it as an edge buffer, a wildlife corridor, or an understory planting that still pays you back with food.

I’ve planted Aronia in a diversity of soil types from clay pan to rocky and acidic. The production is staggering in balanced soil, a bit less cocky in clay or rocky, but Aronia still thrives wherever you put it. It doesn’t want your affection or babying. It wants a little water, sun, and to be left alone.

Permaculture Functions of Aronia melanocarpa

• Food: Superberries for juice, wine, preserves, and smoothies.

• Medicine: High antioxidant, anti-inflammatory properties.

• Wildlife Support: Flowers for pollinators, berries for birds and mammals, dense cover for nesting.

• Ornamental Value: Four-season interest — blossoms, glossy foliage, fall color.

• Soil Resilience: Tolerates clay, sand, wet ground; stabilizes soil.

• Privacy/Windbreak: Thick shrubs form natural screens.

Propagating Aronia

Aronia doesn’t make you beg or buy. It can be propagated by:

• Seed: Cold stratify for 3–4 months, then sow.

• Cuttings: Softwood cuttings root readily in summer with a little patience.

• Division/Suckers: Dig and split established clumps — the easiest way to multiply shrubs fast.

Once planted, Aronia requires almost no maintenance beyond occasional pruning. Tough, generous, and self-reliant. Exactly what you want in a permaculture ally.

Aronia’s Nutritional Punch (It Laughs at Your Kale Smoothie, Scoffs at Your Blueberry)

Aronia doesn’t just look good in a permaculture guild, it hits like a prizefighter in the nutrition ring. A hundred grams of these berries (that’s a small handful) clock in at only 47 calories. Hardly worth the guilt of eating them by the fistful.

Inside that same handful:

• Fiber: 5+ grams — double what you get in blueberries.

• Vitamin C: about 24% of your daily needs.

• Vitamin K: 12–15% of your daily dose.

• Manganese: 30% DV.

• Plus iron, folate, potassium, magnesium — the kind of mineral cast that usually shows up in “super greens.”

But the real brag? Antioxidants. Aronia’s anthocyanins run anywhere from 400 to 1,500 milligrams per 100 grams. That’s three to five times the load of blueberries. Add in its tannins and polyphenols, and you’ve got one of the most antioxidant-rich fruits on the planet. Which is why your mouth goes Sahara-dry if you eat them raw — that’s the good stuff at work.

How We Use Aronia at Pendragon

At Pendragon Orchard & Vine, Aronia isn’t a mystical species, it belongs. We freeze berries for winter smoothies, ferment them into dark country wine, and leave plenty for the birds to stage their annual feast. Aronia hedges hold the edges of our food forest, stitching together orchard rows with blazing fall color. For us, it’s not just another shrub. It’s the anchor of the middle layer, and a reminder that resilience can be delicious. The longer you wait, the less tannins you’ll taste and the sweeter the fruit. But, you will compete with birds, though I have planted enough to share. Consider netting them if they’re getting to them first.

Why Aronia Belongs in Your Orchard or Edible Landscape

Here’s the pitch: hardy as hell, nutrient-rich, tough enough for bad soil, generous to wildlife, and gorgeous in every season. Aronia doesn’t just earn its place, it dares you to find something better. In permaculture, that’s gold. If your orchard is all canopy and groundcover with nothing in between, it’s not finished. Drop in Aronia and watch the system lock into place.

The vines had already died back for the season, leaving the trellis bare except for a few dry stems that rattled softly when the wind moved through them. I tipped one of the containers onto the soil and loosened the root from the sand. A long pale tuber slid out with it, cool and smooth, carrying that faint earthy scent that comes from soil that has held something growing for months.

Yamaimo always feels a little surprising when you lift it from the soil.

Above ground the plant spends the summer behaving like a vine, climbing lightly through whatever structure you give it. The leaves are simple and heart-shaped, the stems thin and quiet among the trellis.

But underground the plant is doing something entirely different.

While the vine climbs upward, the tuber grows downward, sometimes well over a foot into the soil.

To me it remains one of the more unusual species I use in edible landscape design. Not exotic because it’s difficult to grow, but because it occupies space in the garden in such an efficient way.

Food climbing upward. Food growing downward.

Once you notice that combination, it becomes difficult not to imagine where the plant might fit into a landscape.

Why Grow Yamaimo in Containers?

One of the challenges with yamaimo is harvesting.

The tubers grow long and narrow, often extending more than a foot into the soil. In heavy ground they can break easily when dug, which makes harvesting slow and sometimes frustrating.

Over time, and thanks to my friends at the Bullock’s homestead, I started growing yamaimo in deep containers instead.

The pots are filled with a loose mixture of sand and garden soil. The sand keeps the soil open and allows the tuber to grow straight downward without resistance. When harvest time arrives, the entire container can simply be tipped over and the root lifted out intact.

It makes the work considerably easier.

Container growing also allows the plants to be positioned wherever vertical space exists. A pot can be placed at the base of a trellis, fence, or arbor and the vine allowed to climb through the structure through the summer.

For gardeners experimenting with yamaimo for the first time, containers are often the simplest way to grow and harvest the plant successfully.

A Mountain Yam with History and Flavor

Yamaimo has been cultivated in Japan for centuries, long enough that it occupies a comfortable place in traditional cooking. The tuber is known for its unusual texture. When grated it becomes thick and almost elastic, forming a sticky paste called tororo that is poured over rice or noodles.

To someone encountering it for the first time the texture can be surprising, but in Japanese cuisine it is valued precisely for that quality. The root adds body to broths and sauces while carrying a mild flavor that blends easily with other ingredients.

In the mountain regions where it was historically gathered, the plant also carried a reputation as a sustaining food. It’s dense in carbohydrates and minerals and stores well once harvested.

Like many old crops, it quietly persisted long before it attracted the curiosity of modern gardeners.

Plant Profile

Common name
Yamaimo, Japanese mountain yam

Latin name
Dioscorea japonica

Native range
Japan, Korea, and parts of eastern Asia

Plant type
Perennial climbing vine grown for its edible tuber

Height
Vines commonly reach 6 to 10 feet depending on support

Spread
Climbs vertically rather than spreading outward

Hardiness
Cold tolerant compared to most tropical yams

Why Yamaimo Deserves a Place in an Edible Landscape

Read more

It’s quiet work this time of year. The garden doesn’t look like much yet. Just dark soil, labels, and the promise of rows that will fill out later.

But while I was moving through the beds I noticed something that happens every year.

The parsley was already there.

Not barely alive. Not limping through winter. Healthy, upright, leaves thick and deeply green, as if the cold months had hardly interrupted it at all. When you brush your hand through it the smell rises immediately, sharp and bright, that unmistakable green scent that sits somewhere between fresh grass and celery.

Some kale overwintered this year, which surprised me a little. Kale can be tough, but it doesn’t always make it here. Parsley does. Year after year it survives the rain, the frost, the weak winter sun, and the long stretch of gray days that define a coastal winter.

And it made me think again about something I’ve noticed for years.

Parsley may be the most overlooked plant in the edible landscape.

Not because it is rare. Quite the opposite.

Because it is so common people have stopped noticing it.

Most people encounter parsley as garnish, a decorative sprig pushed to the edge of a dinner plate. Something green that isn’t really meant to be eaten. In the garden it behaves very differently. It is one of the most reliable, useful, and well-behaved plants you can grow.

Which is why I plant it in nearly every landscape I design.

A Plant With an Odd History

Parsley has carried some strange associations over the centuries. The ancient Greeks connected it with death and funerary rites, planting it near tombs and weaving it into crowns for athletic games. Some stories claimed the plant sprang from the blood of fallen heroes, which gives it a darker mythology than its mild flavor suggests.

The Romans, practical as ever, ignored the superstition and embraced it in the kitchen. Parsley began appearing widely in Roman sauces and broths, eventually spreading through European cooking where it remains a staple to this day.

Medieval gardeners had their own explanation for parsley’s stubborn seeds. They believed the seeds had to travel to the devil and back several times before they would germinate, which was their way of explaining why parsley can take weeks to appear after planting.

Anyone who has waited for parsley to sprout can sympathize with that theory.

Why Parsley Earns Its Place in an Edible Landscape…

Read more

I walk the same roads through Eastsound most mornings.

It’s an old habit now. After enough years, a walk like that becomes a way of orienting yourself. Collar up against whatever the strait is sending inland that day, moving slowly through the town before it fully wakes. Thin light. Air thick with brine.

Over time you begin to notice the small continuities. What returned. What didn’t.

About ten years ago I started paying attention to a small orchard in town. Old trees. Apples mostly. Not ancient, but old enough to carry the posture of trees that have seen a few owners and a few philosophies of pruning. The sort of orchard you notice if you spend your life looking at fruit trees.

Every spring a crew arrives.

You can tell the day they’ve been there before you even see the trees. The branches scattered on the grass give it away first. Then the canopy. Cleaned up. Thinned out. The sort of work that looks good from the road. Uniform. Symmetrical. Like money well spent. The trees stand there afterward with that look we like. Order imposed. Symmetry corrected. Promises made.

And then the following spring the same thing appears again.

Vertical shoots, dozens of them, climbing out of the scaffolds like antennae. Thin, fast growth racing straight upward as if the tree were trying to escape its own shape. Water sprouts everywhere.

A year later the crew returns. The sprouts are removed. The canopy is shortened again. It looks tidy for a few months.

Then the shoots return.

I’ve been watching the same cycle repeat itself for nearly a decade. Every year the same trees, every year the same cuts, every year the same response from the tree itself. A quiet argument between biology and habit playing out above the grass.

Trees can handle a great deal of cutting. They are built for damage. But most of the time they don’t need to.

The trees weren’t misbehaving. They were responding exactly the way a tree does when its canopy is headed the same way year after year.

The crew wasn’t fixing a problem. They were maintaining it.

Walking past those trees again this morning, seeing the fresh cuts flash bright against the bark, I decided I would write about the cycle—and how to break it.

Because once you see it, you start seeing it everywhere.

Why Does a Tree Create Water Sprouts?

The reason those shoots appear isn’t mysterious. It’s written into the way a tree grows.

At the tip of every branch sits the apical bud. That bud produces a hormone called auxin, which moves downward through the stem and suppresses the buds behind it. As long as the apical bud remains intact, most of those lateral buds stay quiet. The branch extends outward under a kind of biological hierarchy.

Botanists call this apical dominance.

Remove the apical bud with a heading cut and that dominance disappears. The auxin signal stops. Dormant buds along the branch are suddenly released.

Several begin growing where before there had been only one.

At the same time the root system below the soil continues doing exactly what it was doing before the saw touched the tree. It is still absorbing water. Still pushing minerals upward. Still supplying stored carbohydrates through a vascular system sized for a much larger canopy.

The tree suddenly has more energy than structure.

So it answers the only way it can. It grows fast.

The new shoots race upward toward light, rebuilding the leaf area that was just removed. Long, thin, vertical growth bursting from the scaffolds.

Those are the water sprouts.

But water sprouts aren’t useless wood. Given time, many will eventually settle down and produce fruit, though often high in the canopy and difficult to reach.

Sprouts can also serve other purposes. Occasionally one becomes structural, filling the space left by a broken limb or a branch lost to age.

But here’s the problem.

When a tree is pushed into this kind of regrowth year after year, the canopy fills with vigorous vertical shoots. Light disappears from the interior. Fruiting wood weakens. Air movement slows inside the tree, and in maritime climates that kind of congestion creates the damp conditions where disease thrives. As orchardists like to say, sunlight and air are the best fungicides. The tree ends up spending its energy rebuilding structure instead of producing fruit.

And when winter returns, the same shoots that filled the canopy are cut away again.

Which sends the tree right back into the same response.

That’s the cycle.

So the cuts meant to improve the tree slowly begin doing the opposite. And when the same heading cuts are repeated every year, the same response follows every year.

Which is exactly what those old apples in town have been demonstrating for the better part of a decade.

The Cut Heard Around the Orchard

The cycle usually begins with a particular kind of cut.

In pruning there are two basic moves: heading cuts and thinning cuts.

A heading cut shortens a branch. Somewhere along the limb the saw or pruners remove the growing tip and leave the rest of the branch in place.

When that happens, the apical bud disappears. The auxin signal stops. The buds behind that cut, lower down the branch, are released from suppression.

Several shoots often emerge where there had been only one.

That response is predictable. It is the biology of apical dominance doing exactly what it was designed to do.

A thinning cut works differently.

Instead of shortening a branch, the entire limb is removed back to its point of origin. One branch leaves the structure completely while the rest of the canopy remains intact.

Because the neighboring branches still carry their apical buds, the hormonal balance of the tree stays largely undisturbed. The tree loses some wood, but the overall structure and hierarchy remain in place.

Thinning cuts tend to calm a tree. Heading cuts tend to wake it up.

Neither is inherently wrong.

Young trees often need heading cuts to establish structure. A branch sometimes needs shortening for clearance, safety, or to redirect growth. Used carefully, heading cuts can shape a tree well.

But when mature fruit trees are shortened repeatedly in the same places, year after year, the tree receives the same signal over and over again.

The apical bud disappears. Dormant buds wake up. Water sprouts follow.

The result is the cycle those old apples in town have been demonstrating for years: a tidy spring canopy, followed by a summer explosion of vertical shoots, followed by another round of cuts the next winter.

Not because the tree is unruly. Because the instructions being given to it never change.

That’s the cycle. The good news is the cycle can be broken.

Can the Cycle be Broken?

Orchardists correct trees like this all the time. It isn’t permanent damage and it isn’t the end of the tree. But it does take a little patience. A canopy that’s been shorn the same way for years doesn’t return to balance in a single season.

With the right approach the structure settles again. Light returns to the interior. Fruiting wood comes back. The yearly surge of water sprouts fades as the canopy and root system come back into alignment.

Some of the corrective work is surprisingly simple. A few cuts in the right places. Sometimes a branch is removed. Sometimes a vigorous shoot is bent, redirected, or converted into fruiting wood instead of cut away.

The key is restraint. And over time the tree stops fighting you.

Once the balance is restored, the pruning becomes lighter. The tree holds its shape, and the yearly cycle of heavy pruning disappears.

Because once you understand why the cycle happens, correcting it becomes less about controlling the tree and more about guiding it back into balance and keeping it there.

Restoring a Tree That’s Caught in the Over- pruning Cycle

Breaking the cycle takes more than one winter.

Read more

Before a seed is sown or a spade breaks ground, the soil must be understood, not as matter, but as memory. Every bed, every orchard, every edible landscape inherits a story: what was built here, what was buried, what was broken.

The first act of cultivation is not planting. It’s inquiry. Test the soil. Read its chemistry and its silence. Some soils are burdened with metals, residues, or exhaustion from years of extraction. Others are simply asleep, waiting to be woken. You must know which you have before asking it to feed you and your family.

If the soil is burdened, the harvest will carry its weight and symptoms.

A sound soil hums with unseen life. It carries the pulse of microbes, the threads of fungi, the slow intelligence of decay. It breathes, digests, and reforms. Sound soil is not sanitized; it’s symphonic. It’s free of poisons but rich in conversation: bacteria speaking to roots, carbon to calcium, rot to renewal.

To restore a soil is to rekindle that dialogue. Compost mends structure. Biochar holds memory. Mycorrhizae weave trust between species. Cover crops heal the skin. In this way, the ground remembers how to be generous again.

True soil health is metabolism, the quiet conversion of death into nourishment, mineral into flavor, sunlight into sweetness. The nutrient density of a carrot, the vitality of a plum, the strength of a leaf, all are reflections of the microbial order beneath them.

This is where the story begins: not in the seed or the spade, but in the earth’s capacity to renew itself. The landscape’s flavor is decided long before the harvest, in the dark negotiations below our feet, where soil learns to feed, and we learn to listen.

Read more

Hudson’s Bay Company, the PNW Vintner Pioneers

Viticulture reached the Pacific Northwest not with romance but with recordkeeping. In the 1820s, clerks of the Hudson’s Bay Company planted grapes at Fort Vancouver, a small colonial outpost on the Columbia, to see what might survive at the far edge of empire. Those first vines were little more than experiments in curiosity, half trading stock, half sacrament, but they marked the beginning of a long, stubborn question: Can the vine live here?

It would take more than a century for the answer to find shape. East of the Cascade mountains, sunlight was abundance itself. But on the western side, where rain and shadow reigned, every cluster required cunning. The coastal growers of the twentieth century learned to do what their European counterparts in Burgundy and the Rhine had done for centuries: work with restraint, not excess.

That spirit found a home in Mount Vernon, where Washington State University began its western grape trials in the 1970s. There, amid fog and field drains, the modern rules for maritime viticulture were written row by row, wire by wire. From those trials emerged the quiet logic of cool-climate design: narrow spacing, upright canopies, air as medicine. The trellis wasn’t an accessory; it was the architecture of possibility.

Every vineyard west of the Cascades owes a debt to those plots: small, unglamorous, and endlessly instructive. They proved that wine on this side of the mountains would depend less on heat and more on structure. It wouldn’t be abundance that saved the grape, but geometry.

Read more

You don’t get to plant whatever grape you love most. Out here, heat and season length draw the boundaries, and if you ignore them you’ll be staring at green berries in October. Rootstocks aren’t an optional add-on either. They’re strategy. The right one can shave days off ripening, rein in wild growth, and shield vines from the pests and acidic soils that chew up western Washington.

Before we go any further, understand what a [grafted] grapevine really is: two plants fused into one. The scion is the top: the fruiting wood that decides what grape you’re growing, what the clusters taste like, and how the wine will turn out. The rootstock is the bottom: the root system bred from hardy American species that fights pests, tolerates hostile soils, and sets the pace of growth. They’re joined by grafting, so the scion rides the rootstock like a house on its foundation. One provides fruit and flavor; the other makes sure the vine survives long enough to deliver it.

Read more

Seattle and Western Washington don’t shout their potential; they keep it close, dare you to uncover it. And for those who do, the payoff is singular: wines that cut sharper, shine brighter, and speak more stubbornly of place than the broad-shouldered bottles from warmer valleys.

If you’re going to try, you’ll need more than vines and hope. You’ll need to reckon with heat units, rainfall patterns, slopes that carry cold air like water, and soils that can starve or spoil a root system if you don’t respect their chemistry. But each of those obstacles has its counterweight: the right site, the right rootstock, the right hands. Every decision, where you plant, what you plant, how you train it, becomes a chance to tilt the odds toward fruit worth crushing, toward a vintage that proves what this landscape can give.

Read more

A century ago Orcas island wasn’t the quiet pastoral place people imagine when they step off the ferry. It was working land. Hillsides were cleared and fenced. Fields opened toward coves where steamers stopped for freight. Usable slopes held something meant to feed people or pay a debt: hay, cattle, potatoes, and fruit.

Fruit especially.

Apples proved reliable in the maritime climate, and farmers planted them wherever the soil would hold a root. Gravenstein, Baldwin, Winesap, King, Newton Pippin–-varieties that could handle the weather and travel well in wooden crates. In the fall the fruit was picked, sorted, packed, and loaded onto boats bound for Seattle, Bellingham, or Victoria. For a few decades the island functioned as a small orchard economy, each homestead carrying its share of trees.

Then the center of gravity moved east. Irrigation transformed the Yakima and Wenatchee valleys into something island farmers could never compete with: flat land, endless sun, low disease pressure, and orchards planted across thousands of acres in disciplined rows. Railroads moved fruit faster and cheaper than steamers ever could. The island orchards didn’t disappear overnight, but slowly they stopped making sense. Fields returned to brush. Barns collapsed.

Fences disappeared into the grass.

The apple trees remained.

They’re scattered across the island now, crooked remnants of that earlier landscape. Some stand alone in pastures where the house is long gone. Others grow in tight clusters where a homestead once sat. A few sit right in the middle of town, somehow spared when roads widened or houses went up, left standing because someone, at some point, decided they should stay.

They’re wildly overgrown.

Not trained. Not managed. Not pruned into the obedience demanded by commercial orchards. Limbs cross each other and twist upward through the canopy. Moss thickens along branches that haven’t seen a pruning saw in decades. By modern horticultural standards these trees look like failures.

Yet every fall they’re heavy with fruit.

When I walk the island I stop at a few of them. You learn the trees after a while. Most I recognize by variety. A few are remarkable seedlings that never had a name and never needed one.

The branches are chaotic, but the fruit is abundant.

I pick first from the sunny side of the tree, where the apples color deeper and carry a little more sugar. Then I reach into the shaded interior of the canopy and pull a few from the cooler side. Those are paler and slightly firmer. If you eat them side by side you can detect the difference.

Sunlight matters.

But the difference is smaller than people imagine.

Both apples are good apples. Often far better than the polished fruit stacked in grocery store bins, fruit that’s spent months in controlled atmosphere storage before being rubbed to a shine and arranged under bright lights.

Which makes the situation a little strange.

The island’s full of apple trees. They produce fruit every year. Yet most people walk past them without noticing and drive to the store instead. The trees stand quietly along fence lines and old foundations, doing what apple trees have always done: growing, fruiting, dropping seeds, repeating the cycle without the constant supervision we’ve convinced ourselves they require.

They grow, they produce, and they endure, while modern opinion insists that such trees shouldn’t produce quality fruit, or produce at all.

Read more

He worked in a scriptorium lit by high, narrow windows, winter light thin and lateral, flattening shadow against stone. Beeswax candles guttered in drafts, their smoke faintly sweet, clinging to wool and parchment. The room smelled of warmed tallow, scraped hide, damp lime from the curing vats.

He leaned over the vellum the way a man leans over something that cannot be wasted, shoulders rounded, neck forward, one hand steadying the calfskin while the other guided a trimmed goose quill, its tip cut and split with a knife so the ink would run true. Iron-gall ink pooled in the nib--metallic, almost bloody when fresh. Press too hard and it feathered into the skin before settling into dull permanence.

He wore coarse wool, cuffs darkened from use. The room wasn’t warm; in winter he could see his own breath in the thin light from the high window. The vellum felt cold beneath his palm until his body gave it heat. His hands weren’t delicate. Even scribes worked the ground. Soil lived in the seams of his knuckles, and ink lived there too.

He paused to scrape the quill sharp again, a small curl of feather falling beside the page. Outside, wind moved across the lake. Inside, he drew walls that didn’t yet exist. He wouldn’t sign the work--no flourish in the margin, no claim of authorship, no mark to say I was here. His name wouldn’t survive, but the page would.

What he was drawing wasn’t a chapel or a hall but an entire monastery: church, dormitory, refectory, workshops, gardens, orchard, cemetery, infirmary, storehouses, water channels, all in proportion, each structure set in deliberate relation to the others. He wasn’t sketching scenery. He was mapping a self-contained world.

The design would travel across the lake from Reichenau to Saint Gall, folded, carried, received as instruction and aspiration. It wouldn’t be built exactly as drawn; no place ever is. Yet the drawing would endure. More than twelve centuries later, the ink would still bite the vellum. The monk would have vanished into soil, but his lines would remain.

It was drawn during a time of peril.

Charlemagne was gone, and the empire he had bound together was already loosening at the edges. Authority traveled slowly. Harvests were uncertain. Viking ships pressed down river corridors. Roads failed in winter. Monasteries burned. Knowledge survived only if copied by hand, and copying required calm, light, vellum, time.

Nothing had collapsed outright, yet roofs were timber for fire and libraries were dry tinder. A failed harvest meant hunger within walking distance. A missed letter meant silence for a season. Stability depended on weather, on wood that didn’t spark, on hands that didn’t falter. In that exposed and unbuffered world, a monk designed beyond himself.

Read more

A drainfield isn’t a garden bed. It’s an engineered biological system that survives on oxygen exchange and undisturbed soil. Planting above it requires restraint more than creativity. What we’re building here isn’t decoration. It’s a surface ecology that cooperates with infrastructure.

If loam already existed in the drainfield profile with reasonable organic matter, there wouldn’t be much need for amendment beyond the standard topsoil cap. But in a 100% sand system, most perennials will struggle without additional structure. My county’s recommended three inches of topsoil is acceptable as a surface layer. In sand, however, integrating loam into the upper six inches, carefully and without disturbing infrastructure, will dramatically improve plant performance. The goal isn’t fertility. It’s stability.

Confirm all soil work with the septic designer before proceeding. Shallow blending only. No deep tilling. This system depends on intact layers.

Oxygen Exchange and Surface Integrity

No landscape fabric. No plastic barriers. Oxygen exchange isn’t optional in a drainfield. Anything that restricts airflow reduces system longevity. Air must move freely from the surface through the soil profile for the field to function properly.

Why Root Depth Matters

All plants listed below are shallow-rooted, fibrous, rhizomatous, or bulb-based. That isn’t aesthetic preference. It’s structural necessity. A drainfield disperses effluent through perforated lines laid in gravel trenches below the soil surface. Deep, woody roots don’t just search for water, they follow it. Over time, they can infiltrate distribution lines, clog perforations, and disrupt the soil’s ability to treat wastewater properly. Even when intrusion doesn’t occur, aggressive root systems can compact or shift soil layers that are meant to remain porous and oxygen-rich.

Shallow-rooted perennials stabilize the surface without disturbing the system beneath. They hold soil, reduce erosion, and provide seasonal cover while leaving the functional layer intact.

Read more

I don’t know who designed the orchard, but they answered a serious sweet tooth. Fifteen trees. All moderns. All fresh eaters. October arrives and the orchard collapses under its own generosity. Apples everywhere. The ground disappears. The air fills with that sharp, beautiful smell: fermenting sugar, cider vinegar in the making—and still it’s heartbreaking. Too many rot. Too many are carried, apologetically, to the heap of feeding wasps. Not because apples lack value, but because no one asked the harder question at the beginning.

I see this constantly. People plant apples. They rarely design orchards. They choose what they recognize from the grocery store, what everyone else already grows, which means everyone harvests at the same time and no one swaps. There’s no pollination logic, no storage plan, no thought given to cider, baking, or the simple truth that a small orchard should extend a season, not compress it into a crisis. What results is a collection. Earnest. Well-intended. And incoherent.

Read more