Prep Monday—Finding the Right Property


We spent Saturday on the Great Property Search. I suppose I could call this chapter one, because it might yet turn into a full-length novel . . . I do a lot of research before we even get in the truck and head out: location, size, terrain, area, neighbors and developments, aerial view, plat, etc., and yes, we’re working with an agent. We left the house around 7:30 and got back at 2:30, covering 200 miles.

It was a LONG trip. Long. My point is that I’m not in very good shape when it comes to driving that much, so now I have something else to add to the prep list. Besides Advil, that is.

The parcels we looked at? Oh, yeah:

The first one was 42 acres, plus a lake lot at an adjoining development. That last part worried me. According to the mapping, etc., there were two parts of a development surrounding two lakes—now, each lot was about 5 acres or so, but it was still a planned community and we don’t want that.

We only made one wrong turn, and didn’t go too far out of the way, and then we found the road into the “subdivision.” I thought surely it was the back entrance . . . but no.

Ever driven through a creek bed? This was exactly like that.

The term “gravel road” can apparently apply to anything that has gravel on it. Anything.

This road was about as wide as my truck. Barely. It dropped straight down from the paved road for about 20 feet, crossed a slab of concrete that passed as a bridge, then rose straight up for another 50 feet before curving to the right. And by “gravel,” I mean rocks ranging from pea-sized to boulder-sized.

We pressed on.

The road leveled out some, and by that I mean no more ups and downs, but it was far from level. Or a road, for that matter. So we wound around for a few minutes, dropping into first gear a few times, then we reached the intersection. The property was to our right, so we turned onto the next road.

All we could see through the trees were, well, more trees. And a huge drop-off, about 20 yards in; to my relief, the word “development” appeared to mean “one or two houses actually built back here, because no trucks could possibly deliver materials.”

So there was that.

I pulled over into a flat-ish, cleared area, and my husband decided to walk down the clearing to check the lay of the land. I waited for our agent, who arrived in a tiny Toyota. She’d come in the “main entrance.” Finally, my husband showed up again, and announced: It’s a damn cliff down there!

Cliff or not, I’d already had nightmares of trying to bring in anything—even a trailer—and so we left. Barely. The road out was almost as bad, again, exactly like driving through an up-and-down creek bed. Exactly.

The next stop was about an hour south. Seemed farther than the map had shown, but not by much.

It was darn near perfect, in spite of being at the high end of our allotted budget. We parked in a 30-foot clearing that was actually owned by a neighbor; we stepped over a stretched cable and walked another 30 yards or so to a chain barrier—this was also owned by a neighbor, a different one, but had deeded access. I should also add that, in spite of the cable and chain, there was a fairly level but slightly overgrown gravel road that lead back to the center of the property. This was also 40 acres.

We walked around for half an hour or so and decided that yes, we could do something with this. Beautiful.

On the way out, we saw a couple come walking in—they said they had permission to be there, and had seen it before, and were going in search of boundary markers. We shrugged and moved on. While standing by the cars, talking with our agent, a pickup truck pulled up.

Out stepped a rather large man, dressed in camo. Naturally.

Was I worried? No, just wary. Especially since he’d blocked us in.

Turns out, he was the neighbor who owned the second part of the access road; said he was supposed to have been notified and no one was allowed to come out without an agent. We had, of course, and had been told he’d gotten a call. Oops.

The other people who were there, no idea. Not my problem, but the guy left after a few minutes of conversation:

He told us that it would likely cost $20K to bring in electric from the road and to drill a well. Yikes! About four times my previous estimate! Which, of course, if that pans out, will move this property off our list. Very fast!

He also said that the access on which we were parked was NOT deeded, and that the owner, Butch, had refused to do so. Not sure why, I mean, come on, 30 feet? Whatever. That, too, could be a problem at any point. Regardless, we’re on hold here until the utility estimate comes in later this week. He could be way off base. Maybe.

Oh, and by the way: there is definitely WiFi out there!

We still have nearly a dozen properties to go look at, but not till the end of the week. Most are further out than I’d like, but that’s where the cheap land is—it will, however, make developing and moving a little more problematic. Not impossible, not at all, but a little more difficult.

Time to be flexible, which is, of course, a basic tenet of prepping. You can plan, but things don’t always go according to that plan . . .

 

Writer Wednesday—Beware the Ides of Social Media


You’re moving right along, doing your thing, promoting yourself and your books, and all of a sudden—BAM!

You lose friends; people say mean things; sometimes, even, people threaten to “stop” buying your books and say hateful things about you.

What the hell just happened?

People. That’s what happened.

First, it’s really hard to comprehend because you probably aren’t like this. You probably don’t send hate messages and you probably don’t jump to conclusions and you probably don’t spread rumors. And it’s really hard not to take this personally.

I’m telling you, resist that temptation.

Fix the problem, if there is one, and issue an apology and move on. Assuming, of course, that what happened is not at all justified. If it is, you’re kinda screwed . . .

A couple years ago, there was a message board circulating that said some not-very-nice-things about me. These people assumed that since RHP was a new publishing house, we were either A) crooks and criminals or B) clueless. On this particular site, folks seem to jump to conclusions quite a lot; there are many long-time writers on there who seem to “know everything.” I use the word “writers” because most of these people haven’t been published; I reserve the term “author” for ones who have.

I addressed the concerns mentioned with simple answers; those didn’t satisfy a few people, but I stopped. I’d answered their questions. An RHP author saw the thread and jumped in and said, basically, hey, RHP is JUST FINE. I SIGNED WITH THEM.

End of story.

Last week, an RHP author had a social media account hacked. No other explanation. The alleged post, of which I only saw a screenshot, was completely out of character for this author and anyone with half a brain would have realized that.

Sadly, it seems many people do only possess half a brain; I started receiving email. Not the author—no one asked the author. They felt it necessary to email the publisher and threaten not to purchase any more RHP book if we didn’t immediately remove this author.

One of them also couldn’t distinguish between “your” and “you’re,” but I digress . . .

I didn’t ask if they had EVER bought an RHP book, although I did tell one of them that I doubted they’d intended to “place a large order.” Whatever that means.

It was kind of a cluster there for a couple days.

Long story short, the author issued both a private and a public apology via social media, as did RHP. Okay, RHP’s post was a little weighted on sarcasm, but come on! DON’T jump to conclusions, right?

Lesson: periodically Google yourself, see what’s out there; check your social media accounts for “bad” things. Fix problems immediately. And issue an apology.

Then forget it and move on.