Back to Thoughts & Perspectives

Every time Ellicott City floods, we act as though it is a surprise. It is not. The streets there were built on slopes that funnel water straight down toward the Patapsco River, and when the rain comes, gravity does exactly what gravity does. The flooding is not a freak event. It is the predictable result of building a town as if water had no opinion about where it goes.

My students put it more bluntly than I would have dared: there is a lack of worry about the laws of gravity, right up until the moment gravity asserts itself. They are right, and the problem is far bigger than one historic town. Baltimore and Annapolis face the same reckoning, driven by the same combination of heavier rainfall, aging infrastructure, and rising seas. The uncomfortable truth underneath all of it is this: our infrastructure was built to handle the weather we used to have. It cannot handle the weather we are getting now.

That single sentence should reorganize how we think about flooding. We tend to treat each flood as a disaster to recover from, then rebuild exactly what was there before and wait for the next one. That is not resilience. That is a very expensive loop. The storms are getting stronger, the shorelines are eroding, and the impermeable surfaces we keep pouring, the parking lots, the roads, the roofs, send more runoff with nowhere to go. Building back the same way is a decision to flood again on schedule.

So what do we do? I want to resist the temptation to name a single silver bullet, because the honest answer is that different places need different tools. In Baltimore, the work is largely about upgrading the hard infrastructure: expanding stormwater drainage capacity and adding flood barriers and tide gates where the risk is highest. In Annapolis, the smarter move runs the other direction, toward living shorelines built from wetlands, bay grasses, and oyster reefs.

This is the part that I think deserves more attention than it gets, because it is counterintuitive. We instinctively reach for concrete, for the surge barrier, for the wall. But concrete can intensify the force of erosion, deflecting wave energy rather than absorbing it. Native vegetation does the opposite: it soaks up wave energy, slows the water down, and stabilizes the shore before the damage is done. Sometimes the most advanced solution is the one that works with the land instead of against it.

And here is where I will push against the reflex to treat this as the government's problem alone. The biggest, hardest interventions, the drainage upgrades, the tide gates, the underground, are genuinely expensive, slow, and vulnerable to being stalled by budget fights and bureaucracy. Their feasibility is real but limited, and if we wait only on them, we will be waiting a long time. The community-scale tools, by contrast, are remarkably feasible right now. Rain gardens and permeable pavement can be added to ordinary homes with low-cost materials and a weekend of yard work or built in during ordinary construction. They will not stop a hundred-year flood single-handedly. But they reduce the everyday runoff, ease the strain on aging systems, and extend the life of the infrastructure we already have, all without waiting for a single piece of legislation to pass.

That is the case for doing both, and for not letting the difficulty of the big projects become an excuse to do nothing while we wait. Phased investment and a durable, long-term policy commitment are what turn these ideas from a wish list into a working system. The government does the heavy infrastructure. Communities do the green infrastructure at the scale of their own streets and yards. Neither alone is enough; together they are a real answer.

The flooding will keep coming. The only question is whether we keep rebuilding for a climate that no longer exists, or finally start building for the one we actually live in. Ellicott City has been telling us the answer for years. We should listen before the next storm makes the argument for us.

This commentary draws on field research and proposals developed by undergraduate students in Towson University's MTRO 101 class. The opinions expressed are the author's.