Category: Articles

Tony is a solid name–tough and simple, like a horned lizard should be. I would pass my days soaking up the blistering desert sun, digging in the sand, and waiting for ants, which are my main source of sustenance. Life in the desert is harsh, but I would be ready. My large, flat body and sandy hue would keep me concealed, and if I ever found myself in a jam, I would have a few tricks up my sleeve. First, I would freeze, hoping my camouflage would save me. If that failed, I’d puff up to make myself big and hard to swallow. And if a predator actually went ahead and made a lunge to bite, I’d use my last trick—one that only the most powerful horned lizards can manage. I would shoot a little blood out of my eyes, just enough to make an attacker think twice about biting. But honestly, I would not wish to be a bother. I would stay in my own corner of desert, enjoying the hot sun, an occasional gentle breeze, and the ever-present plenty of ants which are my sustenance. Life as Tony the Horny Toad would be uncomplicated, peaceful, and appropriate to the one place I would ever need—the wide, open desert.

This made for an interesting morning of coffee and gummies. I might be getting another dog. It is lonely here on the asteroid.

Overview:

This discussion explores modeling a horse and cart as objects using Object-Oriented Programming (OOP) principles. It covers defining attributes (fields/state), behaviors (methods), and their relationship, particularly when the horse pulls or detaches from the cart.

---

1. Initial Concept – Software Object Representation

• The conversation began with an explanation of software objects in OOP, defining them as entities encapsulating both fields (state) and methods (behavior).
• A general software object diagram was provided to illustrate the concept.

2. Horse as a Software Object

• The horse was modeled as an object with:
  • Fields (State): Color, breed, age, speed, running status.
  • Methods (Behavior): run(), stop(), neigh(), eat().
• A visual representation was generated to illustrate this concept.

3. Cart as a Software Object

• The cart was modeled as an object with:
  • Fields (State): Material, wheels, capacity, color.
  • Methods (Behavior): move(), stop(), load(), unload().
• A corresponding visual was generated.

4. Relationship Between Horse and Cart

• The relationship was established where the horse pulls the cart.
• The horse has a pull(cart) method, and the cart’s movement depends on whether it is attached to the horse.
• A visual representation was generated showing this relationship.

5. Transition to a Bucking Bronco

• The scenario was adjusted to depict the horse as a bucking bronco, modifying its behavior:
  • New Methods (Behavior): buck(), kick() (in addition to run(), stop(), neigh()).
  • The detaches() method was introduced to allow the cart to become disconnected when the horse bucks.
• The updated relationship was illustrated with a new visual representation.

6. Code Representation of the Relationship

• A Python implementation was provided, demonstrating:
  • The Cart class with methods to attach, detach, and store attributes.
  • The Horse class with methods to pull, buck, and interact with the cart.
  • The relationship where the horse pulls the cart when attached but detaches it upon bucking.
• Example output of how the objects interact was included.

Conclusion:
The conversation effectively modeled a real-world system using OOP principles, highlighting how objects interact dynamically. The transition from a standard horse to a bucking bronco demonstrated flexibility in design, adapting object behaviors based on context.

This discussion provided conceptual diagrams and practical code to reinforce the learning process.

Historians can be categorized based on their approach, audience, and purpose. Here’s a general breakdown from the most scholarly to the most narrative-driven:

1. Academic Historians – These are professional historians, usually with PhDs, who conduct original research, publish in peer-reviewed journals, and contribute to the academic study of history. Their work is often theoretical, analytical, and deeply sourced.
   • Example: A university professor writing a book on frontier economics based on archival records.
2. Public Historians – These historians work outside academia, often in museums, historic sites, archives, or government agencies. They focus on making history accessible and engaging for the public while maintaining scholarly rigor.
   • Example: A historian curating an exhibit at a history museum or writing an interpretive panel at a historic site.
3. Popular Historians – Writers who produce history books intended for general audiences. They may have academic training but prioritize readability and engagement over deep historiographical debates.
   • Example: A bestselling author writing about the California Gold Rush in a way that appeals to casual readers.
4. Journalistic Historians – These historians approach history with a journalist’s eye, emphasizing compelling storytelling, investigative research, and connections to current events.
   • Example: A journalist writing a book on the Dust Bowl using interviews, personal stories, and archival research.
5. Historical Novelists – Writers who blend history with fiction, using real events, places, and people but taking creative liberties to fill in gaps or enhance the story.
   • Example: A novelist writing about a fictional prospector in Bodie during its boom years.
6. Folk Historians / Local Historians – These are individuals, often self-taught or community-based, who preserve and share regional or family histories. They rely on oral traditions, personal research, and local records.
   • Example: A longtime resident documenting the history of a small Mojave Desert town through interviews and old photos.
7. Storytellers / Mythmakers – These historians focus on lore, legends, and dramatized history. Their accounts may be based on real events but are often embellished or fictionalized for entertainment.
   • Example: A storyteller spinning tales of Death Valley Scotty’s hidden gold in a campfire setting.

Each type plays a role in how history is understood and shared. Academic historians establish the facts, public historians interpret them, popular historians make them engaging, and storytellers keep them alive in culture.

For generations, history classes have been bogged down by rote memorization-names, dates, and events drilled into students’ heads with little thought given to why any of it matters. Even today, many history teachers and local historians lean too heavily on disjointed facts instead of using them to build meaningful narratives that explain historical significance.

History isn’t just a giant list of trivia; it’s a web of interconnected stories shaped by social, political, and economic forces. A single event doesn’t exist in isolation—it has context, causes, and consequences. Without these connections, history is reduced to a collection of random tidbits, stripped of its power to help us understand the past, present, and future.

This is where public historians—whether in classrooms or local museums—have a real responsibility. Their job isn’t just to present facts but to interpret them, to connect the dots, and to explain why something matters. Trivia peddling is easy; real historical work is harder. It demands analysis, evaluation, and critical thinking. It also requires acknowledging complexity, contradictions, and uncomfortable truths.

And here’s a tough one: not everything that’s old is historically valuable. Sometimes, old stuff is just junk. Not every weathered building or faded document holds significance. Just because something has been around for a long time doesn’t mean it shaped history in a meaningful way. The real test is simple: So what?

That’s the question local historians should always ask. Why does this story, this place, or this artifact matter? How does it fit into the larger historical picture? If we can’t answer that, we aren’t doing history—we’re just collecting trivia.

Top 5 Things Local Historians Are Getting Wrong

The Mojave is a proving ground and gathering place, changing those who move through it alone and in community. It boils life down to its essence—heat, wind, rock, and sky—compelling individuals to face themselves in ways they never have before. In conflict, some individuals discover definitive answers, others find questions, and most sense a connection to something greater than themselves.

To the Indigenous people, the land is sacred, with spirits and tales. Springs, rock etchings, and ancient trails indicate sites for ceremony and connection, where individuals sought visions and where the community reinforced common beliefs. Treasure hunters, travelers, and outlaws found their own beliefs later–whether in luck, omens, or the promise of vast fortune. The desert has always been a place where people feel their faith, shaped by the quiet and the open space that appears to go on forever.

Socially, the Mojave has brought together people who are seeking diverse things. From campfire stories to new-age spiritual retreats, from the alien ambiance of the Integratron to the shared awe of a meteor shower over Joshua Tree, individuals have congregated to experience something unspoken but profoundly sensed. Even in solitude, there is community–rock circles, roadside shrines, and invisible footprints signal that someone else has passed through, leaving their own faint imprint.

In its nature, the Mojave is a mirror. It reflects back what a person has inside–hope, desire, belief, or fear. Some see a wasteland, and some see a haven. Some leave the same, and some are transformed. Whether contemplating alone or together, the desert is the same: a place where meaning is created, where faith and doubt are tried, and where the silence, in its own voice, speaks.

El Gobernador was a steam locomotive built for the Union Pacific in 1885. It was one of the largest locomotives of its time, designed specifically to handle heavy trains on difficult terrain.

Key facts about El Gobernador:

• It was a 4-10-0 type locomotive, featuring four leading wheels and ten driving wheels.
• The design aimed to provide greater traction for hauling freight trains over steep grades on the Union Pacific network.
• Due to its size and weight, it encountered operational problems, such as excessive rail wear and difficulty navigating curves.
• Despite its power, the locomotive was not a success and was retired after only a few years of service.

El Gobernador is an example of 19th-century railroad companies’ efforts to build more powerful locomotives to accommodate increasing rail traffic. However, not all innovations proved practical in the long run.

El Gobernador proved a few important things about locomotive design and rail operations in the 19th century:

1. Bigger Isn’t Always Better – The locomotive was built to be powerful, but its massive size and weight caused operational issues, like excessive rail wear and difficulty navigating curves. This showed that simply adding more wheels and power wasn’t always the best solution.
2. Engineering Limits – The locomotive highlighted the mechanical and structural limitations of railroad technology at the time. The tracks and infrastructure couldn’t always support such a heavy locomotive, leading to inefficiencies.
3. Experimentation Leads to Progress – Even though El Gobernador wasn’t a long-term success, its design contributed to later improvements in locomotive engineering. Railroads learned from its flaws and refined locomotive designs to balance power, efficiency, and practicality.
4. Specialization is Key – Instead of using oversized locomotives for all tasks, railroads moved toward specialized locomotives designed for specific terrains and train types, improving overall efficiency.

In short, El Gobernador was an ambitious experiment that demonstrated the need for balance between power and practicality in locomotive design. It helped shape the future of rail technology by showing what worked—and what didn’t.

The Mormon War (Utah War) of 1857–58 was a conflict between the U.S. government and the Mormons in Utah Territory, though it never escalated into full-scale fighting. President Buchanan, concerned that Brigham Young was prioritizing church laws over U.S. laws, replaced him as territorial governor and sent a military force led by Colonel Albert Sidney Johnston to enforce federal authority. In response, Young declared martial law, mobilized the Mormon militia, and recalled Mormon settlers from surrounding regions. Harsh winter conditions delayed the U.S. Army’s arrival, allowing time for negotiations, which ultimately resolved the dispute peacefully.

During this period, tensions were high, especially following the Mountain Meadows Massacre in 1857, which contributed to fears of conflict and influenced emigrant routes. Meanwhile, the Mormons were also exploring and attempting to expand their influence along the lower Colorado River. They hoped to establish an outlet to the sea for trade, increase missionary efforts among Native American groups, and prepare for possible military threats.

In Las Vegas, Nevada, Mormon missionaries established a mission in 1855 at Las Vegas Springs and explored the Colorado River’s navigability. Early expeditions, such as those led by Rufus Allan and later groups, scouted the river and surrounding lands but found the river largely unnavigable. With the rising tension between Mormons and the U.S. military, Jacob Hamblin and other Mormon scouts, including Ira Hatch and Dudley Leavitt, conducted reconnaissance on U.S. Army activities, believing an invasion was imminent. One Mormon spy, Thales Haskell, was caught aboard the military survey steamer Explorer but provided misleading information about alternative California routes.

Fearing a federal attack from the south, Apostle Amasa M. Lyman led an expedition in 1858 to identify a defensive site near Pyramid Canyon, though no battle materialized. They concluded that Eldorado Canyon was the furthest feasible point for navigation. Ultimately, the anticipated invasion never came, and tensions eased.

Lake Manix – Coyote Arm

The Coyote Arm of Lake Manix refers to a western extension of the ancient lake, reaching into what is now the Coyote Basin area. During the lake’s high stands, this arm would have been a shallow extension of the main body of water, influenced by the surrounding topography and hydrology.

As Lake Manix formed during the Pleistocene, its extent fluctuated with climate changes. At its peak, it covered over 90 square miles and was fed by the Mojave River. The Coyote Arm, like other sections of the lake, would have played a role in shaping local sediment deposition and ecosystems. When Lake Manix eventually breached at Afton Canyon, draining down the ancestral Mojave River path, the Coyote Arm would have dried up along with the rest of the lake, leaving behind alluvial deposits, clay beds, and evidence of past shorelines.

This area is now part of the Mojave Desert, with remnants of Lake Manix’s history visible in fossilized shorelines, lacustrine sediments, and scattered Pleistocene fossils.

Damn Yellow Flowers (DYFs) is a term affectionately (or begrudgingly) used by botanists, naturalists, and desert wanderers to describe the frustratingly abundant and often similar-looking yellow wildflowers that blanket arid regions like the Mojave Desert. These flowers, while beautiful, can be a nightmare to identify—kind of like trying to tell apart identical twins who insist they have wildly different personalities.

The Science Behind DYFs

Despite their casual nickname, DYFs encompass a wide range of plant species, predominantly from the Asteraceae (sunflower) family. This family includes some of the most common desert wildflowers, many of which share characteristics like bright yellow petals, composite flower structures, and a knack for popping up right where you least expect them.

Common DYFs of the Mojave Desert

Below are a few of the most frequently encountered DYFs in the Mojave Desert, along with their scientific and common names:

1. Desert Gold (Geraea canescens) – A tall, wiry-stemmed sunflower lookalike that thrives after rainy winters. It’s often the first to bloom during a superbloom, showing off like that one cousin who always arrives overdressed.
2. Desert Dandelion (Malacothrix glabrata) – A smaller, daintier yellow flower that resembles a garden dandelion but grows in sandy soils. It’s the floral equivalent of a minimalist, sticking to the basics but still catching your eye.
3. Golden Suncup (Camissonia brevipes) – A member of the evening primrose family, this plant has smaller yellow flowers that bloom near the ground. It thrives in disturbed soils, much like the houseplants you keep forgetting to water.
4. Brittlebush (Encelia farinosa) – One of the most easily recognizable DYFs, this shrub produces clusters of yellow daisy-like flowers on long stalks above silvery-green leaves. Imagine a desert plant trying its best to cosplay as a daisy bouquet.
5. Yellow Cups (Chylismia brevipes) – Similar to golden suncup but with more pronounced petals, this species tends to appear in sandy washes and along roadsides, proving that even wildflowers enjoy people-watching.
6. Goldfields (Lasthenia californica) – These tiny yellow blooms cover vast expanses of desert terrain, often blending together to create the illusion of a solid golden ground cover—kind of like nature’s way of rolling out the red carpet, but for bees.

Why So Many Yellow Flowers?

The dominance of yellow in desert wildflowers isn’t just a coincidence. Many desert plants have evolved yellow blooms because it is one of the most visible colors to pollinators, especially bees and butterflies. In an environment where survival depends on successful pollination, standing out is a strategic advantage—basically, these flowers are nature’s version of a flashy billboard.

The Struggles of Identifying DYFs

For amateur botanists and even seasoned professionals, distinguishing between different species of DYFs can be a daunting task. Many species exhibit only minor differences in petal shape, leaf texture, or stem height. Additionally, environmental factors such as soil composition and precipitation levels can influence plant morphology, making identification even trickier. It’s kind of like trying to pick the right brand of mustard—so many choices, all vaguely the same.

Appreciating DYFs Beyond the Frustration

While they may be difficult to differentiate, DYFs are an essential part of the desert ecosystem. They provide nectar and pollen for pollinators, contribute to soil stabilization, and play a role in the desert food chain. Whether viewed as a botanical headache or a seasonal spectacle, these flowers are an undeniable part of the Mojave Desert’s charm.

So the next time you find yourself cursing at a sea of damn yellow flowers, remember that each one has its own niche, history, and role in the desert’s delicate balance. Or just make up a name and move on—chances are, no one will correct you.