The version of this that we had when I worked on Erebus (2009-2017) was more fun.
It had a section about crossing crevasses with combinations of sleds and snomobiles and tracked vehicles, crevasse rescue etc. In the middle of otherwise serious text it said "to recover from this situation, you might elect to [something], or possibly [something else]. Either way, a change of underwear is recommended."
When I was there, McMurdo had strict limits on how much booze you could buy at the store, but no limits on how much you could drink at the bars, and there were limits on what you could order for your field camp but it was quite high -- 2.5 beers / day plus spirits on top of that if I remember correctly.
Reading the post about how a lot of tech breaks because of the slow internet https://brr.fyi/posts/engineering-for-slow-internet makes me think "Kids these days" (stupid kid coders who can't take into consideration slow or latency-filled connections) and want to take a bat into the "open space" where these dumb devs are siting around...
Am a young dev but it shocks me how few of my fellow developers actually consider tech from the ground up.
Most just say 'x has y, we can use that', even when x does a thousand other things and we only want y.
They completely skip the design phase of Y because they have X.
If you design something with actual minimal requirements, ignoring frameworks and language choices, you may end up using X to do Y, but youll at least know what your system should be doing under the hood.
The thought of designing something from scratch seems to be an alien concept these days.
Shameless plug: People into this sort of thing might be into my partner's book coming out in April. It's a beautifully written blend of science writing (penguin biology), memoir, and terrifying asides from the heroic age of Antarctic exploration. Her accounts of the wackiness of living and working out of McMurdo are really fun to read, and include all the orientation and training for which this manual was written (though she was there in 2003). And the history stuff is just hair raising.
One of my favourite lines: "There are many ways to die in Antarctica."
(That's the Canadian publisher link, but it's coming out at the same time in the US, UK, Germany, Australia, and Russia as well, and is on all the major book things as preorder).
I was down there recently on a helicopter-based expedition and they set up a forward base of operations with a few days of emergency rations in case of unexpected weather that prevents you from returning to ship. I asked them what happens if the blizzard lasts more than a couple of days. Someone somewhere has a recipe book for penguins.
Oh man if you had any idea how much work goes into waste sorting & disposal there. In McMurdo every trash station has trash cans for ~10 different categories. I was always calling up the waste department to ask about classification. We would get bored and argue about the classification of juice boxes for "fun". I worked on Erebus and all of our pee & poop got helicoptered out in buckets. Food waste was shipped all the way back to CA and had to be kept frozen the whole way.
I bet that helicopter pilot was some ex-Navy F-14 pilot who liked to buzz the tower and risked his taxpayer-owned jet to save his wingman after an encounter with MiG 28s.
I remember going to a talk on Antarctica where someone said that other nationalities would go and salvage stuff from the trash heap outside the US base at McMurdo. This was some years ago. I assume things have improved since then?
For waste management, x-org server/windows tiling, either for USAP risk aversion or wing aircraft GIS systems that are programmed in UNIX, are the long-leverage hold of -CTU static-build boundaries.
The version of this that we had when I worked on Erebus (2009-2017) was more fun.
It had a section about crossing crevasses with combinations of sleds and snomobiles and tracked vehicles, crevasse rescue etc. In the middle of otherwise serious text it said "to recover from this situation, you might elect to [something], or possibly [something else]. Either way, a change of underwear is recommended."
If people want I can try to dig it up.
EDIT: found it. p244. https://www.eol.ucar.edu/sites/default/files/files_live/priv... It's really interesting to compare these and see how USAP's risk posture has changed. No more adventures allowed.
Reminds me of this terrifying photo:
https://www.reddit.com/r/HistoryPorn/comments/rjy851/tucker_...
So wait.. does that mean they no longer recommend a change of underwear in such cases?
Essential reading for field operations is §3.2f Field-Camp Liquor Rations.
Also, fwiw, it's the 6th edition dated February 2001 (per Acknowledgments).
When I was there, McMurdo had strict limits on how much booze you could buy at the store, but no limits on how much you could drink at the bars, and there were limits on what you could order for your field camp but it was quite high -- 2.5 beers / day plus spirits on top of that if I remember correctly.
I like how the very first pages for this one are related to emergency procedures. Gotta put the critical stuff front and center!
Good UX for emergency situations is underrated.
p244. Thanks.
Oops! Fixed, thanks.
Related: a cool blog from a year or two ago from a participant in this program: https://brr.fyi
I read every word on this site, last time it was posted.
The footage of the Rodriguez well (and TNT explosions), in 320x480 glory, are a time capsule of human ingenuity.
Another fun blog from Funranium Labs: https://www.funraniumlabs.com/category/antarctica/
Reading the post about how a lot of tech breaks because of the slow internet https://brr.fyi/posts/engineering-for-slow-internet makes me think "Kids these days" (stupid kid coders who can't take into consideration slow or latency-filled connections) and want to take a bat into the "open space" where these dumb devs are siting around...
Am a young dev but it shocks me how few of my fellow developers actually consider tech from the ground up.
Most just say 'x has y, we can use that', even when x does a thousand other things and we only want y.
They completely skip the design phase of Y because they have X.
If you design something with actual minimal requirements, ignoring frameworks and language choices, you may end up using X to do Y, but youll at least know what your system should be doing under the hood.
The thought of designing something from scratch seems to be an alien concept these days.
Shameless plug: People into this sort of thing might be into my partner's book coming out in April. It's a beautifully written blend of science writing (penguin biology), memoir, and terrifying asides from the heroic age of Antarctic exploration. Her accounts of the wackiness of living and working out of McMurdo are really fun to read, and include all the orientation and training for which this manual was written (though she was there in 2003). And the history stuff is just hair raising.
One of my favourite lines: "There are many ways to die in Antarctica."
https://www.penguinrandomhouse.ca/books/796661/where-the-ear...
(That's the Canadian publisher link, but it's coming out at the same time in the US, UK, Germany, Australia, and Russia as well, and is on all the major book things as preorder).
I was down there recently on a helicopter-based expedition and they set up a forward base of operations with a few days of emergency rations in case of unexpected weather that prevents you from returning to ship. I asked them what happens if the blizzard lasts more than a couple of days. Someone somewhere has a recipe book for penguins.
I assume it tastes like… chicken?
No, penguins are pretty disgusting.
And also have some rather disgusting personal habits:
https://threadreaderapp.com/thread/1667192081373184000.html
Do NOT let strange dogs into the base.
Especially if Norwegians are shooting at it from a helicopter.
I feel there is a back story here.
I believe it's a reference to John Carpenter's "The Thing"
Ok, thanks - it went over my head.
Definitely worth a watch.
Yes, I have seen it. But a long time ago. It is a great film.
I find it neat that even in a climate as hostile as the Antarctic humans still make an effort to recycle.
> Field Camp Hut Etiquette
> Sort and pack all trash and recycled materials and take them back to McMurdo Station for proper disposal.
Oh man if you had any idea how much work goes into waste sorting & disposal there. In McMurdo every trash station has trash cans for ~10 different categories. I was always calling up the waste department to ask about classification. We would get bored and argue about the classification of juice boxes for "fun". I worked on Erebus and all of our pee & poop got helicoptered out in buckets. Food waste was shipped all the way back to CA and had to be kept frozen the whole way.
Very fun insight, thanks for sharing your story!
I assume things like Starlink have made the station a lot less "boring", which might depreciate some of the "off-grid" novelty of being there.
Juice boxes are cardboard, plastic and alumunium glued together and a hassle to recylce. But heck, their inventors (Tetrapak) are billionaires!
I bet that helicopter pilot was some ex-Navy F-14 pilot who liked to buzz the tower and risked his taxpayer-owned jet to save his wingman after an encounter with MiG 28s.
I remember going to a talk on Antarctica where someone said that other nationalities would go and salvage stuff from the trash heap outside the US base at McMurdo. This was some years ago. I assume things have improved since then?
I have no idea, never been there. I was referencing Maverick from Top Gun being threatened with flying a cargo plane full of rubber dog shit.
Sorry, posted to the wrong child thread.
That “orange” bag has seen better days.
For waste management, x-org server/windows tiling, either for USAP risk aversion or wing aircraft GIS systems that are programmed in UNIX, are the long-leverage hold of -CTU static-build boundaries.