Note that they were staying roughly 2 miles within the actual track, while having the bulk of the work being done by a combo of officers and newbs that they had just trained. That's high accuracy standards for celestial nav, not even counting that this is most of other people's first time doing this in anger.
Just going to second this. Good code reviews (not just typo nitpicking) can be a great way to simplify down code, and spread knowledge horizontally across the org. Not to mention catching bugs.
Unit test aren't a substitute because unit tests check that the success paths are good. That's a good start, but it's not the same as verifying all the possible ways code could go wrong in a complex system, and one of the cheapest ways to spot those problems is with people familiar with complex system looking at new code.
Code review give you the double benefit of building more people who understand the whole system, and having the code looked at by people who understand the whole system.
It was a bad disaster. I was scheduled to be there, but took a look at the NOAA rainfall map the night before and canceled my trip.
Calling it unthinkable is really overselling it though. Mountain towns and roads flood when it rains a lot. If you search past years google search results for Chimney Rock, it floods with 3" to 5" inches of rain. The town is just a few feet above water level - I've walked along the river.
> Mountain towns and roads flood when it rains a lot.
> Chimney Rock, it floods with 3" to 5" inches of rain.
This was no ordinary flood - Chimney Rock was basically wiped off the map. This isn't a "dry it out and replace the sheetrock" situation, most of the town is gone.
That's not to say building several feet above a mountain river is a smart idea (or any river, for that matter), but this level of destruction hasn't been seen since the 1916 flood.
I think they mean more literally historical, in the sense that like this is when people will remember becoming aware that inland mountain ranges are catastrophically vulnerable to hurricanes now.
> Meteorologist Ben Noll said that the level of moisture transported to western North Carolina is more than 1.5 times greater than any event in the historical record for the region.
This is a little more than "mountains flood when it rains" it seems.
Perhaps the only local event in the same ballpark as this one for the southern Mountains is the flood of July 1916, when a remnant tropical storm caused rivers to swell and inundate Asheville and other mountain towns. For more than a century, that event has loomed large as the area’s flood of record.
At the few river gauges in the region that observed both Helene and the 1916 storm, the crests since Helene have broken those long-standing records. The French Broad River and Swannanoa River – which collided at high speeds and high volumes in 1916 to overtake Biltmore Village – both saw new record crests during and after Helene.
The French Broad River in Asheville rose 1.5 feet above its previous highest crest, and downstream at Blantyre, the river surpassed its 1916 crest and was still rising when the gauge stopped reporting on Friday afternoon.
The Swannanoa River at Biltmore crested at 26.1 feet, more than five feet above its 1916 maximum and slightly above the apparent 26-foot crest in April 1791, making this effectively the worst flood along the river since North Carolina became a state.
And I agree that it will become more common with climate change.
Not sure what is going on, because I don’t see your quote. What I see is:
Perhaps the only comparable event, in which a storm struck the Gulf of Mexico coast and dropped incredible amounts of rainfall hundreds of miles away, came in 1969 with Hurricane Camille. After making landfall in extreme southeastern Louisiana, Camille tracked over Mississippi, Tennessee, Kentucky, and West Virginia before combining with a frontal boundary over Virginia and producing epic rains of up to 25 inches.
From the article, this might be rare but it has happened before:
> Perhaps the only comparable event, in which a storm struck the Gulf of Mexico coast and dropped incredible amounts of rainfall hundreds of miles away, came in 1969 with Hurricane Camille. After making landfall in extreme southeastern Louisiana, Camille tracked over Mississippi, Tennessee, Kentucky, and West Virginia before combining with a frontal boundary over Virginia and producing epic rains of up to 25 inches.
A couple of factors keep most hurricanes away from the mountains. There's a strong gulf stream current that tends to lead hurricanes up along the east coast, sometimes as far north as NYC. And also the Gulf of Mexico can draw hurricanes away. Hurricanes dump so much rain on land that they have to be constantly replenished by water sources, otherwise they'll peter out pretty quickly. Land also exhibits something like drag on hurricanes and tends to slow them down.
I bet there have been some hurricanes whose edges have grazed central NC, but the most intense weather (heavy, sideways rain, storm surges, and 200mph+ gusts) are experienced at the edge of the eye. It's rare that hurricanes are so big and intense that land far away from water experiences the worst of it.
Monads are just function chaining worshiped in the holy language of category theory.
You have an array of state, and you can call a method on it that returns a new array of state, that you can call a method on, that returns a new array of state, etc. And that concept of doing state -> function call -> state is the holy Monad.
A JS pleb would write instead:
burrito = (new Tortilla()).addMeat(Chicken).addMissionBurritoIngredients().holdThe(Cheese)
No one would be confused about what was going on, and it would be basically the same thing.
Yes. But perhaps a syntax around the type of the return object to match with the next function.
While it is just functions. To say, it's just functions all the way down, doesn't help you talk about them.
Could say that math is all functions, and having some language to discuss that subject is maybe more the purpose of the monad.
Kind of like if you were to say to a math student, just go study functions, no need for any school or language to describe what is happening.
But yes, category theory is a bit heavy handed to a programmer just needing to chain some functions.
Maybe the problem is such a vast gulf between the junior dev just needing to know how to chain some things, and the category mathematician that has never coded. Yet they are circling around the same subject.
Just a few months ago, Hezbollah exploded a rocket in soccer field with children playing, killing 12 children. Doesn't get much more "exploding devices in public spaces" than that.
Very debatable. The local population seem to be under the impression that it was an iron dome missile that fell on the sports ground. Partly because they claim it is a regular occurance (malfunctioning dome missiles and detritus falling in the area).
Ask yourself, why would the Druze population be a target? It's almost unthinkable that Hezbollah deliberately targeted those civilians.
Cancer (outside behavior related cancer like lung cancer) is on the rise.
In spite of better treatments, a twenty year old today is more likely from cancer while in their twenties than at any time before. Each younger age cohort has an increase risk of cancer, and at younger ages.
Cancer deaths overall are still going down though, as the smoking generation still alive goes out.
I agree that practice can be tremendously valuable in knowledge work, but at some point in the skill curve, once you have built up a the ability to accurately self-evaluate the value of practice goes down because the work itself is the practice.
Benjamin Franklin was referenced in the article, and there are far more examples in his life than just the writing exercises where he employed deliberate practice to improve his ability in an area. But he didn't continue these once we was rocking these skills at a world class skill level - instead he switched to practicing new skills he wanted to add.
But if you haven't tried doing so deliberate practice - I'd highly recommend it.
Programming is a fractal of tasks. There's big stuff like how you architect a program, then down to how you write functions, and then down even further into grit below that.
And one of the joys of programing is that at each level, there's not one right answer. But even with there being different things you can optimize for, there's also a ton of poor choices that could be made as well.
Practice lets you focus on one aspect at one level, and improves your ability there. If you were to practice writing a function focused on correctness, another time on readability, and lastly writing the function based on performance optimization, you would almost certainly be able to write a better function later. You've expanded your tools, you've learned new techniques, and you've consciously evaluated your work from different perspectives.
Agreed - this is very clearly someone wanting less workload, and the company wanting to keep them around. It's also not a rush. This gives four months for a smooth transition.
reply