Contributor profile
Michael Deem
Michael Deem is the editorial lead for Maryland Wilderness. His role on the site goes beyond page review. He sets the practical standard for how species pages, public-land guides, outing pages, and wildlife conflict-prevention pages should read when the goal is to help Maryland readers make better decisions before, during, and after time outside.
That standard is shaped by a decade of wildlife damage control experience, a private-applicator background beginning in 2007, and practical entomology knowledge that sharpens how he reads insects, food sources, habitat edges, plant pressure, structure conditions, and seasonal wildlife-use patterns. On Maryland Wilderness, that experience shows up in the way pages explain sign, timing, attractants, access points, realistic outing choices, and the difference between a passing encounter and a repeat problem that needs a stronger response.
His Maryland work also keeps the site from flattening everything into one answer. A raccoon at a chimney, bats in a ridge vent, geese holding on a shoreline lawn, deer pressure in a planting bed, insects driving bird activity at a marsh edge, and a lower-Bay outing shaped by wind are all different questions. The site is edited so those questions stay distinct, stay useful, and stay grounded in what Maryland actually looks like on the ground.
Where that authority matters most on the site
Wildlife conflict prevention
Structure use, attractants, denning seasons, cleanup, and first-step prevention all need practical judgment that separates a minor site issue from a pattern likely to repeat.
Outing realism
Public-land and visit pages are edited for the kind of day a place truly supports, not just for attractive descriptions. Weather, pace, distance, visibility, and repeat value all matter.
Field interpretation
Species and habitat pages are reviewed so they explain why an animal is there, what sign matters first, and what seasonal cues change the answer.
Insects and attractants
Entomology knowledge strengthens pages where insect pressure, food availability, nesting, plant stress, or seasonal hatch activity changes how wildlife uses a site.
What readers should expect from that experience
Readers should expect Maryland pages that are less generic, less repetitive, and more willing to distinguish between similar-looking situations. A prevention page should not read like a species profile. A public-land page should not read like a destination list with scenery pasted on top. A field-note page should sharpen observation instead of recycling the same summary language. Editorial lead work matters most when it preserves those differences and protects usefulness page by page.
Readers should also expect clear limits. Maryland Wilderness publishes public guidance. It is built to help readers understand common wildlife situations, choose better outings, and change site conditions before a nuisance pattern grows. It does not replace agency direction, emergency response, or property-specific consulting. When a page points toward official or licensed help, that is part of the editorial standard, not a retreat from usefulness.