Evan X. Merz

In California, we are constantly struggling with space limitations. If you're an urban gardener like me, then you might be working with as little as a tenth of an acre. This can make composting somewhat difficult. It's hard to find space for multiple compost piles. Fortunately, there is a much easier way to improve your soil that requires no dedicated space in your yard.

What is composting in place?

Composting in place means composting in the place where you intend to grow plants. It means composting directly in the soil, rather than composting in a bin then applying the compost to the soil.

Composting in place has the advantages of requiring no extra space, and requiring very little time or effort. The drawback is that you have to dig up the spot where you want to compost, so you can't have anything growing there at the time. For that reason, composting in place is generally a fall or winter activity.

Composting in place is a great way to improve your soil without having to set up a compost bin, or learn how to turn it, or learn about greens and browns.

How to compost in place

Composting in place is exceptionally easy, but it takes around a month or more for the process to complete, so it's really only something to do in fall or winter.

1. Gather kitchen scraps. My partner and I keep a container near the sink and drop all our waste plant material into it. Most of the time that material goes into our regular compost bin, but in the fall and winter I try to bury as much of it as I can.

2. Identify a place in your yard where you want to improve the soil for planting in the spring. In my yard I have a long narrow strap of soil between my driveway and my neighbor's fence. I use it for planting flowers mostly.

3. Dig a hole around 12 inches deep.

4. Dump your kitchen scraps in the hole.

5. Cover the kitchen scraps with the removed soil and mulch.

6. Wait around a month.

There are just a few things to be careful of. First, don't bury animal products this way unless you understand the risks of attracting animals. Second, this will only work in non-frozen soil. So it works great in the fall and winter for most of California, but it's not great in places where the soil freezes. Finally, be careful about doing this in the late winter or spring, as you need to give the soil food web enough time to turn the food scraps into compost.

So get out there and start improving your soil while the weather is good! This is a great garden activity that you can repeat every day in the slow seasons.

It can be difficult to get started with native plants. There are so many questions. What plants are native? Where can I get native plants? How do I care for native plants? Why is it important to plant them?

The answers to all these questions are complex, but starting with native plants doesn't have to be. In fact, there are some native plants that you can start for free, and require little to no care to propagate.

In this post, I'm going to tell you why you should plant California Buckeye, and how to do so for absolutely no cost.

Why to plant California Buckeye

California Buckeye is a fantastic tree or large bush for California gardens because it is compact, well suited to most of the state, and great for native pollinators.

1. California Buckeyes are beautiful

In spring the California Buckeye grows beautiful tall white flowers that look a bit like candles. They tend to attract lots of butterflies, so they put on a great show.

2. California Buckeyes are perfectly sized for small yards

California Buckeye is not a large tree. Most California Buckeye I've seen are between 8 and 12 feet tall, and about as wide. When you see them in a thriving native forest, they may grow up to 40 feet tall, but that is exceptionally rare.

3. California Buckeyes require virtually no care

Are you tired of irrigating your trees? California Buckeyes are native to California, so they are perfectly adapted to the climate here. They only need water at the times of year when we get it. They start dropping their leaves in the summer in order to ensure that they don't waste water.

4. California Buckeyes are easy to grow from seed

California Buckeye grows readily from seed. Just collect the enormous pods in the fall or winter, place them in a pot, and when they're taller than a foot, transplant them into your yard. They don't require any special attention if you just leave the container outside to get the normal amount of water we get in the winter.

5. California Buckeye is a great replacement for small non-native trees

California Buckeye is a perfect replacement for non-native Crepe Myrtles and Japanese Maples.

I know you have seen streets lined with Crepe Myrtles. Yeah, they look beautiful occasionally, but do you ever see them swarmed with pollinators? No, because Crepe Myrtles aren't native to California. While they are well suited to the climate here, they are just pretty trees that do nothing for the local wildlife. California Buckeyes will grow to about the same size as Crepe Myrtles, they put on very similarly shaped flowers, and they will support local pollinators.

The same thing goes for Japanese Maples, except Japanese Maples aren't even well suited to the climate in California. Japanese Maples are understory trees that need a fair bit of water, and prefer to grow in the shade of other trees. They only thrive in California if they are given artificial irrigation from water that is wasted on non-native trees in spots where native trees would require none. California Buckeyes will grow to roughly the same size as Japanese Maples, and they will require no supplemental irrigation.

How to plant California Buckeye

Possibly the best thing about California Buckeyes is how easy they are to grow.

1. Collect the seed from a tree in fall or winter.
2. Put it in the ground where you want a tree (in fall, winter, or early spring).
3. Wait.

I've grown several California Buckeyes from seed, so I know it's possible to be successful just by dropping the enormous seed in the ground, but you can also start them in large-ish containers then transplant them into the ground in a year.

Here are a few other things I do when propagating California Buckeyes.

1. Collect the seed directly from the trees right before they drop

California Buckeyes have absolutely massive seeds. They are just a little bit smaller than baseballs. So they are easy to collect. I don't think I've ever had one that failed to come up, but I always plant a few extra to ensure I get what I want. If you want one tree, then collect three seeds.

Here's what the pods look like when they are ready for collection.

I should say that you should get permission from your local trail or park before you gather seeds, but I don't know any wildlife that depend on the seeds (squirrels eat them, but they are toxic to most other wildlife), and I've never seen a tree that doesn't produce a mountain of seed. You only need one, and you are going to make more native plants.

2. Drop them in containers when you pull out your tomatoes

Are your tomatoes done for the year? It's time to pull them out. But what do you do with the soil? Tomatoes are such heavy feeders that it's difficult to reuse the soil.

But that's the perfect time of year to gather California Buckeye seeds and put them in the ground. Because they don't mind growing in poor soil, they will readily sprout in containers where tomatoes have been grown.

3. Don't worry about water

Unless you're in the desert, then the seed won't need any more water than nature provides. Just leave the container outside and forget about it. When the tree is transplanted into its final location (in the following fall probably) then you should make sure to water it regularly for the first few weeks until the rainy season begins in earnest.

Start today

So what are you waiting for? The seeds are falling from the trees in fall and winter. Go ahead and pull out your irrigation system, pull out that non-native tree, and drop in the seed for a California Buckeye. With very little work, you will reap the rewards of one of many beautiful trees that come from California.

More information

California Buckeye on Calscape

California Buckeye on Wikipedia

I sometimes consider changing the name of my blog to "the oldest millenial" because I was born in 1981, which is usually considered the start of the millenial generation. Sometimes people put the start of the millenial generation in 1982, but in either case, I mostly sympathize with millenials so I consider myself an old millenial rather than a young Gen-Xer.

My point is that I'm not young, but I'm young enough to see how much the elder generations have hurt young people. Stagnant wages, rising college prices, burning fossil fuels, and the shredding of the social safety net mean that everyone younger than the boomers has a far more difficult time finding success in life than the boomers did.

So when I learned about the rule changes coming from realtors, it struck a familiar chord. I don't know what the realtors are calling the new rule, so I'm going to call it the "Treat Young People Like ATMs Rule of 2024".

Who are realtors?

Realtors are a professional organization of salespeople who facilitate home sales. They aren't a part of the government. They aren't even a necessary or required part of the home buying process. They are simply salespeople who have banded together in an organized way.

They ostensibly make buying homes easier, but they have a mixed reputation, to say the least. Still, they are usually involved in both sides of any home sale. Both the buyer and the seller each hire an agent and they work together to help the buyer and seller achieve their goals.

The basic dynamics of the arrangement aren't changing.

The Treat Young People Like ATMs Rule of 2024

So what IS changing?

In the past, the fee for each agent came out of the seller's end. Each agent recieved around 2.5% to 3% of the sale price as their fee. So the seller would make 5% to 6% less than the sale price because that amount would go to the agents.

The new rule forces the buyer to pay the fee for the buyer's agent. It also forces the buyer to sign contracts that require them to work with and pay a specific agent.

How does this hurt young people?

Now, in a fair world, this could be seen as fair play. The seller pays the seller agent fees and the buyer pays the buyer agent fees. Fair enough, right?

But context matters.

The context of this rule change is that the people who own homes today didn't have to pay the buyer's agent fees when they bought their homes.

Now, in addition to the 10% to 20% downpayment that first time home buyers must accumulate, they must accumulate an additional 3% to pay their agent. Adding the additional 3% on the buyer means that more young people will be locked out of home ownership even longer.

It also means that homeowners will take a larger share of the pie. It's a wealth transfer from young, non-wealthy people, to old, wealthy people. Yet again, the older generation, rather than helping young people, is changing the rules in order to steal from them.

What's the point?

So why make this rule at all?

It's difficult for me to understand why this rule exists.

It will have the impact of artificially making housing prices look lower than they really are. This will confuse first time buyers.

It will have the impact of allowing home owners to take a larger share of the pie. This is the part where they're using young people like ATMs.

It will also make it easier for investors and the wealthy to scoop up homes at prices that first time home buyers can't afford.

It may temporarily prop up a housing market that is clearly heading for an "adjustment".

Shopping shouldn't be a contractual process

But the weirdest thing about this law, beyond the predictable greed, is that it makes shopping a contractual process. It forces people who want to buy a home to sign a confusing contract that locks them into fees with an agent who, in many cases, adds very little value to the process.

The realtors, as a professional organization, have clearly overstepped what any rational person would consider reasonable. Shopping shouldn't be contractual, and it's unfair to place even more of a burden on first time home buyers and young people.

When did this become okay?

When did older generations start seeing young people as their ATMs? When did older generations switch from supporting younger generations to stealing from them?

The greed embodied in credit scores, stagnant minimum wage, and this new rule is staggering. (Not to mention the unsustainable burning of fossil fuels, which is increasingly hard to ignore.)

As of this writing, I'm 42 years old. I don't consider myself an old person, but as I said at the beginning of this rant, I'm an old millenial. And frankly, I'm ashamed of everyone over the age of 40. How can any older person support putting more of a burden on young people, especially when it comes to housing?

I think that we're turning a corner on many of the issues mentioned in this rant, but regressive policy changes like this are a step in the wrong direction.

Since the COVID lockdown I've been spending more and more of my free time in my garden. It feels good to grow green things and the garden always has something to teach me.

I've realized that when you're working with living things, you never get it exactly right the first time. So whenever I try to grow something that I've never grown before, I always plan to fail. It's not that I intend to fail, it's just that I know how hard it is to succeed at growing something new the first time.

But setting expectations correctly doesn't mean that my failures don't surprise me and that they aren't great learning opportunities.

This year, I wanted to grow corn for the first time. So I read tutorials and watched youtube videos. I ordered high quality seed, and I thought I had a good idea what I was doing.

For instance, I learned that corn is wind pollinated. That means that the pollen actually has to fall down onto the silks, which will develop into the delicious ears of corn. For this to work properly, the corn has to be planted in a block, and that block has to be reasonably sized.

Since I'm gardening in the middle of the city, I had to carve out a new space for it. In the fall I dug out a section of my backyard and prepared the soil. In January I planted peas there so that they could do their nitrogen-fixing thing in preparation for the corn. I harvested the peas in May then I seeded the corn in dense rows.

I thought that maybe, just maybe, I could pull this off. Maybe I had grown enough as a gardener that I could actually get it right the first time.

Then the corn started coming up. Kind of.

It started emerging from the soil at the front of the bed, but not at the back, and I couldn't figure out why. I had watered evenly and deeply when seeding, then lightly for a week. Still the plants emerged slowly and unevenly.

In fact, they seemed to struggle more toward the back. Close to the sunflower.

I knew that sunflowers were allelopathic. Allelopathic plants use various strategies to prevent other plants from growing nearby. A fellow gardener had told me that sunflower seeds were allelopathic. That's why nothing grew under his birdfeeders. So as long as I didn't let the seeds fall, then I could plant sunflowers near other plants. Right?

Well, no. As it turns out, I misinterpreted what that gardener said. Yes, sunflower seeds are allelopathic, but so is all the rest of the sunflower. Every bit of the plant exudes chemicals that will prevent seeds from germinating properly or growing well. So the roots of my sunflower were digging into my corn bed and exuding chemicals that prevent my corn from developing normally.

And the worst thing is that it's too late to do much about it. I could dig out the sunflower before it flowers, till the soil, and heavily amend it. Then if I replanted the corn I might have moderately more success, but the allelopathic chemicals would still be there. And it's getting late in the season to start new corn. And that sunflower is 10 feet tall and still growing!

So, even with several years of gardening experience and learning, I managed to fail at growing corn the first time I tried it. I might harvest a semi-developed ear or two from my plot in a few months, but I won't get very much.

And that's a shame.

But at least I'll know better next year. I need to be very strategic about where I plant my sunflowers. Sunflowers seem to play nice with established plants, but they aren't so nice to young plants. I used to only plant sunflowers in my front yard, with established, decorative, native plants. I plan to return to that strategy.

As for corn, well, I'll try again next year. And this year I can go hard on the other two sisters. The squash and beans will have to make up for the failed sister!

For the last few years, I had been running this blog using Gatsby. In general, I liked Gatsby. I liked that it was so simple up front, but had such deep complexity under the hood. I liked that it supported React out of the box. I liked that it could generate websites in so many different ways.

I liked it enough that I made my own minimalist blog starter called Empress, which was a fully featured blog based on the tutorial but with several key features added. I used that for this blog for several years and I liked it.

But man, the leadership of Gatsby was bad. They took it in such weird directions. They tried and failed at so many weird features that the documentation, and the product itself just became a dumping ground.

It really went off the rails when they created Gatsby "themes" that had nothing to do with the colloquial use of "themes". Themes were really more like plugins, but they were already using that term, too. So it was a hot mess, and soon enough the feature seemed to disappear from the docs and from existence.

Then they were bought by Next. I still don't understand that acquisition. Next.js is a good product with sensible leadership. I liked using it at my prior job, and I considered using it for this site, but it was just overkill.

So when I could no longer navigate the crazy web of dependencies to upgrade my blog to the latest version of Gatsby, I essentially stopped writing. I was just so frustrated with it.

Until this weekend, when I decided it was time to change.

Hello, Eleventy!

I decided to switch to Eleventy mostly because it's the static site generator with the most hype right now. Sometimes it's good to try the tech that is currently being hyped. It's good to stay up to date and have that line on your resume.

But also, Eleventy is a good product. I planned on spending a few weekends getting my blog switched over, but it only took me a few hours on Saturday, Sunday, and Monday to get it 95% switched over. There are still a few minor bugs here and there - don't check the title tags on tag pages, and ignore the reverse chronological sorting in some places - but in general the switch was very easy.

I've been around web programming since the 1990s, and Eleventy feels like a return to an older way of working, but with some of the good infrastructural tech we picked up along the way. Like now I'm writing in markdown, and I don't need to run MySQL on my server, nor do I even need to run a traditional "server". I can just host my static site on S3, and use GitHub Actions to deploy it, just like with Gatsby.

And I've heard some of the blowback against Jamstack architecture sites in the last few years. It's why I briefly considered using Next for this. But I still think JavaScript + API is the best/fastest/cleanest way to run a website, whether it's a blog or something more complex. I don't have an API for this site, but I feel like I could attach one without too much trouble if the need arose.

I do wish that I could use React. I saw some people try to get Eleventy working with React experimentally, but I didn't see any updated package to do it. Nunjuks and markdown are okay for the basics, but I do think that a true component-based architecture is ultimately a cleaner way to build UIs than a template based architecture.

Until next time...

So I'm going to give Eleventy a shot for now.

But we all know that those of us who still quixotically maintain personal blogs in 2024 are on a perpetual upgrade cycle. We all know that no "upgrade" is the final upgrade.

I wonder what I'll "upgrade" to in a few years? Maybe Wordpress will come back around?