I speculated a bit about this sort of thing earlier this week. How might urban design change?
One of the most pressing questions that urban planners will face is the apparent tension between densification – the push towards cities becoming more concentrated, which is seen as essential to improving environmental sustainability – and disaggregation, the separating out of populations, which is one of the key tools currently being used to hold back infection transmission.
Some colleagues in the geo community are working on this project to map health care resources by region and facility. All of the code and work is in the open on GitHub.
A technical piece describing the goals for Facebook’s rewrite of the Messenger app. Interesting to see them avoiding their own React Native for this, and doing things in native iOS/Android.
A humorous post, but has a point. There’s pressure to add new tools that don’t do much but add moving parts and complexity. There’s nothing wrong with Kubernetes, but there’s a place for it (and your small team probably doesn’t need it).
The more you buy in to Kubernetes, the harder it is to do normal development: you need all the different concepts (Pod, Deployment, Service, etc.) to run your code. So you need to spin up a complete K8s system just to test anything, via a VM or nested Docker containers.
And since your application is much harder to run locally, development is harder, leading to a variety of solutions, from staging environments, to proxying a local process into the cluster (I wrote a tool for this a few years ago), to proxying a remote process onto your local machine…
Yesterday evening I attended a community meeting in our neighborhood on the tidal resiliency plan the City of St. Pete is putting together to combat the periodic street flooding we get during high tidal or rainfall events.
The city planning folks in attendance were showing maps of the neighborhood and projected areas of high water during these events. The crux of the issue in Shore Acres is that during spring tides, water from the bay pushes back up the storm drain pipes and comes out the streetside storm drains in some of the lower intersections in the neighborhood. Parts of Shore Acres are like a bowl — the inside actually lower than the outer rim. With such low elevation all around, even a couple inches of difference can mean water covering the entire roadway or a homeowner’s yard.
Streets around our house can get bad:
This graphic makes it look worse than it usually is. Even in high tide + high rainfall combo events, it isn’t this extreme. This is a projection of 30+ year storm events. It does definitely get wet out there, though.
With all of the studies and survey work they’ve done the past few years, the group presented a host of projected improvements that could be done to alleviate the problem — including bioswales, roadway elevation, force mains, pump stations, and even some aquatic plants (grasses, mangroves) out on the sand flats to reduce wave action.
Near our house would be a little bit of everything, if most of the plan goes through. I’m sure they’ll only end up doing a small fraction of the most critical improvements. The full scope of proposed options looks expensive. Most importantly, near the worst of the flooding on our route out of the neighborhood, they’ve proposed a pump station and force main to be installed in a piece of public land in the intersection:
This would be a major overhaul to a decades-old problem of street flooding in Shore Acres. A long overdue bunch of improvements to keep everyone safe and able to get out of the neighborhood if needed.
The City’s overview map of the area really shows why this is a problem. The entire neighborhood was once an estuarine marsh that was essentially converted into manmade “islands”.
