Retention of Midway was important, but, more importantly, the Japanese were unable to accomplish any of their desired goals: to gain a necessary bastion to protect their Far Eastern frontier or to destroy the remaining U.S. fleet in a massive surface engagement. The U.S. loss of Midway could have spelled the loss of Pearl Harbor and the Hawaiian Islands. If Japan had taken them, the United States may well have been forced to sue for peace. Even without a Japanese invasion, the key position that Midway represented could well have slowed or stopped U.S. offensive moves for some time to come. It is for this reason that Midway, and not Guadalcanal (launched 7 August 1942, the first offensive of the United States against the Japanese), is included in this work. A U.S. loss at Guadalcanal in late 1942 to early 1943 would have forced a longer war and attacks at other locations. A U.S. loss at Midway, however, may have precluded any U.S. offensive into the Pacific.
> a.) they seem more representative of what most war is like
Yes, that's true. I'd highly recommend With The Old Breed. It's sort of the inverse of 100 Decisive Battles: a single soldier put his pen to paper and recorded everything he remembered about the Okinawa conflict, from start to finish.
> Similarly, it'd be interesting to read war histories that focus on logistics and technological development.
I agree! Does anyone know of something like this?
If you liked this sort of thing, you'll love that book. It usually stuffs you full of numbers, like this article. But mostly it just tells the stories really well. It has several detailed accounts of Napoleon's battles, including the reversal at Moscow and the final stand at Waterloo. It goes up through the Iraq war.
With the Old Breed: https://www.amazon.com/Old-Breed-At-Peleliu-Okinawa/dp/08914...
I can't help but mention this one, even though it's not at all what you were asking for. It's just worth reading. It's unrelated to logistics, but it walks you through the terrifying perspective of a single foot soldier.
I have a lot of good stories saved up that I’d love to share. Google corporate didn’t much care for my blogging, and even though they never outright forbade it, I received a lot of indirect pressure from various VPs. So eventually I stopped. Sad.
But that’s not where my mind’s at today. Those stories will have to wait for my book.
I can completely relate with this. I used to work at S2 games on Dota 2, and at Matasano as a pentester. Both cases led to a lot of interesting stories, and I have often thought of writing a book collecting these into a single work from the perspective of a programmer, simply putting thoughts to paper.
There is a book, With the Old Breed https://www.amazon.com/Old-Breed-At-Peleliu-Okinawa/dp/08914...
It's the perspective of a WW2 solider, and simply chronicles events one after another with very little personal flair. Simply a linear sequence of events. The end result is fascinating, and works like this seem rarely published.
My question is, how can I do this without ruining my career prospects? Is that a valid concern?
All of my stories are generally positive, and I don't think any of them would cause drama. I just want to reminisce about the good times, and collate the perspective of fellow devs and pentesters.
Obviously, sharing specific details that were covered under NDA is out. That's not what this is about. But I do want to be careful not to gain a reputation as someone who will reveal company secrets if you hire me.
Any tips? It's a scary prospect, but it seems worth doing.
Fresh book recommendations delivered straight to your inbox every Thursday.