Tuesday, October 31, 2023
Threaten Me, Will You?
Sunday, October 29, 2023
Can't Vouch for the Veracity, but it's Interesting
UPDATES BELOW.
Stumbled across this on the YouTubes yesterday:
I had hoped he's spend more time on the early history of "the Site" coming here, rather than slipping into the salaciousness surrounding the SL-1 accident. I've read a lot about what happened there, and though this guy criticizes the investigators for not delving into the reasons why this happened -- he admits we'll never know, since the three guys died. Speculation does nothing, particularly this far removed from the event.
Also, he glosses over a lot of detail. It's helpful to add that the SL-1 was a US Army project. He could also have gone into the "anything goes" of the early Atomic Era, but the accident is the thing that people tend to want to focus on the most.
The comments on YouTube devolve into the "Mormon town, ew gross." To that I say: Whatever. I'm sure the local Mormon snobbery you experienced exists, but I'm also sure you're exaggerating its impact and are just echo chambering the haters rather than seeing it extensively from personal experience. Crossing cultures is a two-way street, and many of those critics seem to forget that.
UPDATES.
Chapter 16 of Susan Stacy's "Proving the Principle," one of the references cited in the linked video, contains this information, concerning the aftermath of the SL-1 accident:
"For low-power critical facilities, including the ones at the [National Reactor Testing Station] NRTS, the [Atomic Energy Commission] AEC ordered that all operating and shut-down procedures be written in detail. Joen Hensheid, supervisor of the ETR Critical Facility, recalled:
The SL-1 accident was a big watershed point. Up until then, our detailed procedures weren't much, but we were able to get a lot done in a short amount of time. After SL-1, the reactor [I worked with] was shut down, and we had many, many reviews of procedures. Some reactors at the Site went two years before starting up again. There were committees, and everyone was reviewing procedures and developing formalized sign-offs. It turned into a totally new way of doing business with reactors. Procedural documents that originally had been two pages long were expanded into thick books, and all activity became rigidly prescribed . . . those years of committee meetings with no experiments were hard on everyone."
That says a lot. Yes, there was regret that the "go-go" era was over, but there were clearly many lessons learned from SL-1, but it seems the only thing people want to discuss in connection with the accident is the possible love triangle angle, which can't be substantiated. Leaving the soul-searching out does the average YouTube documentarian looking foolish, going after only the salacious or enthralling. Sure, committee meetings are boring. But the result is worth mentioning.
Wednesday, October 25, 2023
Forget the Fifth of November, Just Remember to SLOW DOWN when You Edit
Letting someone else look at your work is kinda scary.
But gather around and let your teacher tell a true story about how having others evaluate your work can be a benefit to you.
This was me, a few weeks ago. Invisible to management until a mistake was noticed in my work.
Why was the mistake there? Two reasons:
1. I assumed the people I was working with had scrubbed this particular document for errors like this.
2. I did not scrub this particular document myself to detect errors like this.
I'm being vague because I can't discuss the nature of the work, but suffice it to say: Mistakes were made. I did not detect them -- and detecting is part of my job -- and the errors were detected by someone higher up in the chain.
I have since re-evaluated my work process with these particular documents and implemented a stragegy to help me detect these errors before the higher-ups have a chance to spot them. It means more work, but it also means infinitely less work and increased trust further in the document review process.
I neglected to check someone else's work properly, and it cost me a weekend of anxiety and two long weeks of work following that to make things right.
So, the lesson here is twofold:
1. When you peer review someone else's work, be sincere in your efforts.
2. When you get feedback, be sincere in accepting that your writing isn't perfect.
Here's a quick lesson on what's called "Levels of Edit," something I'd forgotten as I worked (or didn't work) on the document in question.
Levels of Edit means you read a document more than once -- each time focusing on a particular attribute of writing. That does mean more work on the surface, but it also means your likelihood of catching errors goes up significantly as you go through the various levels.
Here are some typical Levels of Edit to consider:
Spelling/grammar. Just looking to see if there are typos, misused words, awkward sentences and such.
Flow. Are the transitions between ideas okay? Does what your reading make sense, or are there gaps that the writer needs to fill to help you understand better?
Citations/APA. Does the author tell us where each quote or paraphrasing comes from? Are references included, as well as the works cited page?
As usual, Purdue OWL has some pretty helpful suggestions on the levels of edit to consider.
But wait -- won't I save time if I do all this editing at the same time?
Maybe.
Or maybe you'll miss important stuff if you don't take a more methodical approach.
I have more than 25 years of professional writing experience, and yet I still screwed up on something pretty fundamental because I was trying to do all levels of editing at the same time.
My advice to myself now: Slow down. Remember the fundamentals. And avoid future, high-profile screw ups. They're not pretty.
And if Dilbert isn't enough, consider the wisdom of John Kenneth Galbraith, economist and diplomat:
Tuesday, October 24, 2023
The Green Crabgrass, by O. Henry
It's not as maudlin as O. Henry's "The Last Leaf," but the Green Crabgrass I can view through my study window is what keeps me going as winter threatens its first appearance this week.
The Facebook thread for this features gloomy weather and 19th centrury Russian novelists.
I love O. Henry's story, by the way.
Monday, October 23, 2023
Friday, October 20, 2023
Sorry, Dogs, the Knotholes are Gone
Younger Me might be chagrined to hear this, but I'm at my happiest when I'm building something.
So our neighbors to the north sold their house. Given that they took their big dogs with them, we thought this would be the perfect time to replace the fence along that property line, at least through their backyard.
So that's what I did today.
I had to do some trimming to let this cedar trunk poke through. I'm not sure I did enough of a gap, but we'll see. Had to do the same thing along the bottom as the roots are protruding. You can see in the picture that the tree is so close to the fence I had to secure the slats from this side rather than the other. Not necessarily happy about that, but it is what it is.
The next bit of fence along the sideyard is going to take some work, as I have four posts that have to be replaced because the current posts are leaning heavily toward the north. I'm not sure I'm excited to dig that many postholes this close to winter. It's also hard to think any concrete I pour to hold the posts in place won't freeze rather than cure. So that'll be for next year.
Much to the chagrin of our dogs, this means the knotholes they barked at when the dogs next door were barking are gone. I'm sure they'll still go to that part of the fenceline to bark. Old habits die hard.Wednesday, October 18, 2023
What Arguing on Social Media Sounds Like
Jim Lovell's reaction here is to point out that the arguing will only serve to rile people up, not doing a thing to solve the current problem we all face together: Trying to stay alive.
As a corollary, I thought this was interesting: Substitute "GamerGate" for whatever problem or demon or institution being argued over, and I think the logic displayed here applies.
Monday, October 16, 2023
Pumpkin Walk Prep
Tuesday, October 10, 2023
I Love it When Newspapers Record History
UPDATE: I've now been told this is a fake. Which is a shame. But it was still fun to read.
Found this on Facebook today, and it's a treasure.
It's the movie prop that keeps on giving. A lot of work went into it -- for something that was onscreen for about a second (okay about five seconds), in an era where very few people had the option to stop, rewind, and freeze frame.
It goes on to quote Consolidated Edison technician Brian Holmes, so this guy has a name:
And lest you think they left anything out, behold the story's final paragraph:
At press time, representatives from the firm were meeting with New York Mayor Lenny Cloch to discuss the growing spectral plague, despite fierce protests from Agent Peck. The talks have reportedly not proceeded beyond an animated debate over whether or not Peck has a p****.
Monday, October 9, 2023
Doubt Your Doubts
Friday, October 6, 2023
Stop Claiming, Start Explaining
Help me understand something here.
I've seen a few posts similar to this one, with random people who are spiritualists or spiritualist-adjacent promising people financial blessings, or a new house, or a new car, or a new whatever, simply by "Claim[ing] it now."
They contain the typical "Get-rich-by-wishing-it" tropes of photoshooped piles of money, bros with watches, even more photoshooped money, and the like.
Here's what I don't understand: Many of them, like this one, features ramen noodles, specifically this chicken ramen packet.
Why, I ask.
I've asked that on a few of the posts (do not recommend; your feed becomes flooded with similar posts) and no one has answered the question. They're too busy "claiming it," or so it seems.
I'm used to culture leaving me behind, but there are times the culture needs to pause for a moment and explain itself.