Photo from back corner of garage towards the front, showing one year (or less) of erosion on one side of the garage. This is the downhill side, the right side back in post #7. Seller had piled old 2x6 boards there, to try to reduce erosion from roof runoff. He took those boards with him, just before the closing.
Photo from back corner of garage, across the back wall's width. The concrete pier shown is the same one that is at the extreme right side of prior photo in this post.
The ground slope is steeper to the right of this photo. Around 70 ft. away is a very steep gradient.
My amateur idea for the sides is to dig sloped trenches in the roof drip zone, install sleeved drain pipes and then backfill with gravel.
For the structure's back wall, because of the strong slope, I think a retaining wall could be built 5 ft. to 8 ft. from wall, with drain pipes and gravel again. All drains would be extended a few feet beyond the right side of the second picture, towards the steep slope and the creek at the bottom.
But there is no clear path around the barn toward the back yard seen in the background. Maybe a second, lower, retaining wall is needed to cover the drainage pipes and to provide a level surface for small equipment (Kubota BX size) to access the back yard. The well is in the front yard, so back yard access would be for septic, tile field, etc. That second retaining wall isn't vital now, but there's a fenced area between the house and barn preventing passage. The far end of the house does not have much room between multiple tree trunks and the air conditioner unit. There are also natural gas pipes and sprinkler water lines on that far side.
I know I give too much info. A habit I picked up over many years of dealing with specs on building and modifying computer systems. I would tell team members "Give them what they need, not just what they ask for." And then I would have to explain to the dismayed users (who wrote the initial specs) that I meant the final product should be better than their initial request's wording. Talking through their business requirements and then asking "what if" questions would give them what they really required.
After 38 years in computers, I can say that only ONE system user every handed over PERFECT specifications for EXACTLY what he NEEDED. Every variable, every combination of variables, every condition and contingency - all thought out before we first met to discuss his project. He told me everything that was needed, from memory. I wrote it all down as he dictated complex rules as if he was calling out a grocery list.
That guy was in charge of all service departments and all service personnel training for a national car manufacturer. He might not have been the Dos Equis "most interesting guy in the world", but he was damned talented.
- He knew the names of each of the hundreds of mechanics working in the service areas of all the dealerships.
- He successfully raced motocross bikes, as in winning trophies.
- He could talk, in detail, about any aspect of the engines and transmissions used in their cars.
- He played classical 12-string guitar. Talented enough that people at the corporate HQ looked forward to his concert at the annual holiday part.
- His Christmas cards were incredible pencil LINE drawings of detailed holiday scenes. Artwork, actually.
I'd tell new users of that guy's talents, and that he had thought of EVERY aspect of the programming he needed. I'd say "Let me hear your list of talents. Match or beat his expertise and I'll think we don't need to discuss your specifications."
// Sorry, just an old guy trying to take his mind off of worries about the new barn!! //
