Sounds like my case. Increasing couldn't get wear contacts any more without problems, hated all of the problems of glasses, was scared of the surgery... and it was just nothing. Seriously, how can instantly improved vision not be at the top of your to-do list?
How do you manage routing, especially across multiple identically numbered private networks?
Even if you make the assumption that the IoT has the bandwidth, range and routing capability for meshing, it seems ripe for many kinds of abuse. Greedy traffic handling (dumping incoming, flooding outgoing), MITM, etc.
I am not a virologist or an epidemiologist (nor do I play one on TV) but I always seem to remember the risk of a larger pandemic from Ebola or other similar severe hemorrhagic fevers was reduced due to the nature of these illnesses having a rapid onset and severity which limits the ability of infected people to be ambulatory and infect other people.
What I wonder and maybe worry about is a long-term low-grade outbreak leading to mutations which increase the amount of time the infected might be able to spread the illness. I don't know how likely this is, but it seems kind of a scary idea.
The agile way, quick and dirty. Find the code for whatever task you're supposed to do and change it. You do not try to place it on some grand master blueprint like in waterfall. Nor do you, according to agile, need that blueprint to add a new feature. If your code change breaks anything then tests will fail. Now you've got regressions, that's a task if you need one. Don't build any extra abstractions. Don't make your code overly generic. Go back and add those only as they become clearly needed and necessary. The general sentiment is that we don't know what tomorrow will bring, so fix it for today and if we need to redo it later we'll do just that.
You ask for the big picture, agile's answer is that there is none. The whole code base is alive and trying to keep on top of everything else that's happening is too much wasted time. You just keep the bits and pieces you work on working as you make changes. If the architecture becomes a problem then we'll make that a refactoring task to solve that particular issue, but it's never a full review. If agile was to create driving directions they'd go something like "Take the road going closest to the direction you want to go. If it becomes rough, carry on as it's probably better to get through that go back. If you really hit a dead end, make the smallest possible backtrack that lets you get around it."
How did Bruce Wayne get away with unlicensed nuclear reactor under his house and where did he get fuel?
From the corner drug store. Duh.
Any Nexus branded device running Cyanogenmod. Or any non-Nexus device that CM supports (there are literally dozens)
MUCH more importantly, though, ads are draining your BANDWIDTH. It's important, because it's also a simple demonstrable harm. If you pay $30 per month for your internet bandwidth, and the ads use up half of it (conservative estimate)
In which universe do you live where ads on a webpage total up to half of the bandwidth to deliver said webpage?
Because Google purposely don't allow you to block the ads in android (*)
They don't make it easy but they don't make it all that difficult either. Buy a Nexus, Developer Edition, or one of the multitude of carrier branded phones that are rootable. Install one of the multitude of ad blocking apps that are available, AdFree being my personal favorite. Problem solved.
That's not what everything I've read about the disaster has said. The mountain has gone through cycles - whenever it collapses, the river gets moved away, and the slides stop for a time, but eventually it wears away the footings enough that it falls again. They'd even tried to prevent landslides there by manually shoring up the base back in the 1960s, but it just flowed over their reinforcements.
The waterlogging of the soil is also a necessary factor too, mind you - not saying otherwise.
I had paperbark birch seeds, which are also pretty water tolerant (though not as much as river birch), but none sprouted - ironically I think the seeds were too wet when I stratified them (same with my maples). Isn't river birch (B. nigra) a warm-weather birch species? I've got some cuttings of random local birches from a neighbor but I have no clue whether any of them are water tolerant enough to take swampy ground. Also birches don't usually get that tall so I don't know how expansive of a root system they'll put down. The abundant local species B. nana (dwarf birch) grows (nay, volunteers) readily here almost anywhere that sheep don't graze, but it's just a shrub, I doubt it'd do the trick (though it's probably better than just grass). It can take wet soil, although not totally swampy conditions.
For the wetter areas I also have about a dozen or so western redcedar seedlings - they're not as swamp-tolerant as dawn redwood and western recedar, but they're still reportedly quite tolerant of wet or even waterlogged soils, and they should be more cold/wind hardy than those two (wind is actually the big issue, it doesn't really get that cold here). I've also got a number of other pacific northwest trees with varying degrees of standing water tolerance. Oh, and a species or two of tasmanian mountain eucalyptus (don't remember which ones) that tolerate fairly swampy ground and should at least stand a fighting chance against our winds.
Basically, I'm just going to plant a ton of stuff and see what survives.
One plus is that where the ground is persistently wet and at landslide risk, it is slowly flowing water, it's not standing. It's constantly replaced by fresh, cold ground-filtered water, so there's probably not as much risk of root rot as might be common otherwise. But there's still the oxygen issue. That and the damned sheep, but I'm working to fix that issue once and for all...
Are trees supposed to eliminate the river at the bottom that's been eating away at the foundation of the slope?
The 'pedia says that it's an ancient delta of glacial sand that was subsequently exposed to a lot of water flow, washing out the silt and clay, leaving just the loose sand and gravel with nothing to cement it together.
I cannot conceive that anybody will require multiplications at the rate of 40,000 or even 4,000 per hour ... -- F. H. Wales (1936)