Napoleon planned his Russian campaign extensively: he had supply hubs set up all over the Duchy of Warsaw, with feeder routers from Prussia keeping them full.
What he didn't anticipate was how bad the roads in Russia would be and how long the Russian army would retreat along them. You can't resupply an army that is marching on a narrow dirt road through a forest because it's blocking its own supply lines.
A year ago I started sending postcards to my 91 year old father because he has difficulties with modern forms of communication. They do still exist but you have to search for them.
He liked to be able to reason about programs without running them.
He preferred simpler languages because they contain less irrelevant noise which got in the way of that.
"Kinda hard to find where Dijkstra praised something (except Algol 60)."
Hamilton Richards, who was one of Dijkstra's colleagues at the University of Texas, told me in an email that Dijkstra was impressed by the work of Richard Bird on functional programming.
Interesting. Bird-Meertens formalism? That was directly influenced by APL. In the broader scope — algebra of programs — Dijkstra heavily disliked Backus’ FP.
If the transients occur immediately following the nuclear explosions but not before them, then the correlation together with the earth shadow deficit suggests that the transients are caused by reflective debris produced by the nuclear explosions. I don't know how feasible it would be for this debris to survive the explosion and be blasted above the atmosphere to glint in the sunlight at night, but there is the case of the missing manhole cover from one of the Operation Plumbbob tests: https://en.wikipedia.org/wiki/Operation_Plumbbob#Missing_ste...
Yes, that is how Facebook, Yahoo and many other companies started out. But they rewrote their code when it became to big to be maintainable. The problem with shoddy code is not necessarily that it doesn't work but that it becomes impossible to change.
