Starting a long game from scratch on every mistake is from an era was when content was incredibly expensive. Forced repetition, especially of the early part of the game, is a cheap gimmick.
once the wind dies down and the humidity rises, a fire becomes much less dangerous. The problem with these recent fires is when you have like sustained 50 mph gusts and 5% humidity. When I first moved here in 89, I never heard of a fire crossing a freeway (though no doubt it happened sometimes) because the conditions weren't typically so bad. Now it is commonplace.
> When I first moved here in 89, I never heard of a fire crossing a freeway (though no doubt it happened sometimes) because the conditions weren't typically so bad
The Laguna fire in 1970 crossed over I8. [1] (Be sure to watch the video at the bottom of the article, it's really interesting.) I know you acknowledge that it probably happened, but the reason is didn't happen more was due to the location of those fires, not characteristics of those fires. Most wildfires don't happen near freeways, so the data will show that fires jump freeways more frequently now. That may be true, but there are also a lot more freeways now. Interstate highways didn't even exist before 1956 and freeways were also rare at that time, so comparing freeway-jumping between then and now isn't really saying much about fire intensity.
Almost all of California's largest fires have had human causes.[3] There is a tendency to blame climate for wildfires increasing, but the real reason is that there are just a lot more people in the state. More structures, more people, more irresponsibility at scale. There is also a lot more misguided policy. For example, bans on cutting trees, reduction of logging activity and various other policies designed to "protect" the environment but fail to acknowledge unintended consequences. (To be clear, I'm not advocating mass logging, but bad policy is definitely contributing to fires.) [4]
> The problem with these recent fires is when you have like sustained 50 mph gusts and 5% humidity
Probably hammering metal on metal (hammer and stake) created small and hot metal splinters – like sparks, but not glowing red – and this was enough to start the fire.
You often see road signs in dry states advising motorists pulling trailers to double check their chains to make sure they don't cause sparks that start roadside wildfires.
It's more about the chains dragging and getting super hot. You won't be creating sparks on a non-paved surface. Vegetation won't be growing on a paved surface.
that's not the 'fishy af' part. what's a bit fishy is the comedy of errors afterwards. only slightly though. it's entirely plausible. had he also tried unsuccessfully to urinate on the fire, then maybe i'd be doubtful.
In all of the zillion times that the same stuff happened without the accompanying errors you never heard about it.
If you look at major aviation or industrial disasters a great many of of them involve two or more unlikely to fail components failing at once. It's not reasonable to look at it after the fact and say "look, a coverup! those two systems wouldn't likely have failed at once!"
I think my first experience with an optical mouse was on a Data General unix workstation around 1990 or so. It needed a special pad; the pad was metal and had a grid pattern on it. The mouse was somewhat less responsive than ball mice at the time.
Pennymac | Software Engineer | Westlake Village, CA | Full-time | ONSITE
PennyMac (http://pennymacusa.com) is a leading national mortgage lender and servicer. Our Capital Markets Technology group is looking for local, on-site developers to help develop and support our pricing and related systems. We are a small team of dedicated developers who are always looking for better ways to do things.
Qualifications
- Know dynamic programming languages (e.g. Ruby, Python, JS)
- Know SQL databases (e.g. Postgres)
- Know data structures and how to use them appropriately
- Understand containerization
- Good communication skills
- Know software development methodologies (e.g. Extreme Programming)
- Be able to work directly with business users
- Love open-source software like we do
- Write high quality code AND tests -- we’re big on code reviews and automated testing
Our technology stack includes:
- Ruby/Rails
- Front end awesomeness with Netzke* and ExtJS, also some Javascript/React
- PostgreSQL
- Python (for some backend services)
- AWS
E-mail arman.bostani@pnmac.com if you are interested.
I've used noise cancelling headphones for thousands of hours by now, luckily no issues. My latest pair is Sony 1000xm3. I love them so much, it would be a huge bummer if I was afffected by the pain issue and had to give them up.
Depends on the fractal. I occasionally make HD animations (using Ultra Fractal), and those run about 1 hour PER FRAME. A short clip takes several months, just to render. (search for jockc on youtube if interested)
