wmtc
we move to canada
1.08.2025
memories of my niece eva
1.06.2025
eva
Eva Kaminker Andres, November 28, 1985 - January 5, 2025
One of the very best people it has been my privilege to know and to love.
Rest in peace, beautiful soul. We will miss you forever.
1.02.2025
what not to do in a job interview
As a library manager, I regularly hire new library workers in entry-level positions -- library assistants who work on a casual, on-call basis. When permanent positions open up, casuals are internal applicants, awarded positions based on seniority. In other words, once someone is a casual, there is no interview process to becoming permanent -- so we need to be very selective about who we hire for casual work.
We get quite a few applicants who crack the threshold for an interview. Most jobs in our region are either strenuous, outdoors, physical labour, or professional work that requires an advanced degree. Our work is neither of those, which makes it attractive to many people. In addition, many people believe a library would make a nice work environment. It does -- but usually not in the ways that they imagine.
There's a lot wrong with the interview process. Does it actually yield the best library employee? Sometimes, but not always. Are we hiring the best potential worker, or the best interviewer? Despite that, this is the system we're stuck with for now.
In my old library system, there was a huge amount of internal movement, and I interviewed almost continuously for two and a half years. I learned that interviewing is a skill that can be studied, practiced, and improved. I also learned that the supposedly objective system, based on numerical scoring, is in reality very subjective.
I wish everyone could learn good interviewing skills. There are resources to help, but you'd have to know that you needed it. However, I can easily draw up a short list of what not to do.
- Don't say negative things about yourself. If this is a habit of yours, learn to keep it in check.
- Don't give one-word answers.
- Don't say "you know what I mean" instead of explaining something, even if it's difficult to explain.
- Try not to use jargon from another field.
- Try really, really hard not to babble. Try even harder not to rant.
- If you are asked, "Why did you apply for this position?", do not say, "Because I needed work," or "Because I couldn't find anything else," and especially not "Because it seems like an easy job."
- Don't make ageist, racist, or other bigoted comments! Obviously the people who do this don't realize they are doing it. So here's an easier way to think of it: don't bring up the age or ethnic background of anyone in any story. There is no way to do this and come off sounding good. From the interviewer's point of view, we're grateful to hear these comments. The interviewee has now disqualified themself, ensuring that we won't have to deal with their misguided attitudes on the job.
1.01.2025
what i'm reading: 2024 wrap-up
For more on why I'm now using a reading plan (what most people call a reading challenge), scroll down on this post.
Here's what I read in 2024.
At least five current (within three years) nonfiction ✅
I loved all the current nonfictions, and most of the older nonfictions, I read this year.
Prequel: An American Fight Against Fascism, Rachel Maddow (review)
Doppelganger: A Trip into the Mirror World, Naomi Klein (review)
How the Word Is Passed: A Reckoning with the History of Slavery Across America, Clint Smith (review)
Ducks, Kate Beaton
I Heard Her Call My Name: A Memoir of Transition, Lucy Sante
Path Lit by Lightning: The Life of Jim Thorpe, David Maraniss (review)
The Turnaway Study: Ten Years, a Thousand Women, and the Consequences of Having -- or Being Denied -- an Abortion, Diana Greene Foster
At least five older nonfiction from my Books Universe ✅
Operation Paperclip: The Secret Intelligence Program that Brought Nazi Scientists to America (2014), Annie Jacobsen (review)
The Red Parts: Autobiography of a Trial (2007), Maggie Nelson (review)
Bob Dylan: Behind the Shades Revisited (2001), Clinton Heylin
War Against War: The American Fight for Peace 1914-1918 (2017), Michael Kazin
Wolf: A True Story of Survival and Obsession in the West (2017), Nate Blakeslee (review)
Utopia Drive: A Road Trip Through America’s Most Radical Idea (2016), Erik Reece
Illness as Metaphor (1978); AIDS and its Metaphors (1988), Susan Sontag
Vanishing New York: How a Great City Lost Its Soul, Jeremiah Moss
How to Kill a City: Gentrification, Inequality, and the Fight for the Neighborhood, P.E. Moskowitz
Gentrification of the Mind: Witness to a Lost Imagination, Sarah Schulman (combined review)
At least ten fiction ✅, including at least two from authors I have not previously read and have been curious about. This year's new: Ursula Le Guin, Elena Ferrante, Kevin Wilson, James Ellroy. ✅
Advance one long-term goal ✅
Down and Out in Paris and London, George Orwell (Goal: read everything Orwell published)
Read one massive book in installments ✅
Visions of Jazz, Gary Giddins (still reading!)
Also read
Several children's graphic novels
A small sampling of legal thrillers and spy thrillers by famous authors, none of which I liked
Reports (or summaries of reports) published by: the Canadian Centre for Policy Alternatives, Dying With Dignity Canada, BC Health Coalition, Amnesty International, Canadians for Justice and Peace in the Middle East, Athena Coalition (Amazon workers), RAVEN (Indigenous environmental action), and SAFE Supporting Abortions for Everyone
A large (digital) pile of feature-length articles and opinion pieces from The Atlantic, The New York Times, Vox, and other more occasional sources, which I save and track through Chrome's Reading List feature
12.31.2024
12.27.2024
why i'm not letter-writing this year, part 2: the sad tale of the lost comments
In my previous post, I mentioned that I'm not participating in Write for Rights this year, for the first time in more than 15 years. This decision propelled me to introduce Write for Rights as a library program, which spreads the word, generates lots of letters, and helps me justify (to myself) not writing.
The real reason behind this decision: I have three consecutive days off from work, and I had slated them for restoring The Lost Comments. And once again, my plans for The Lost Comments have come to naught.* * * *
The lost comments
In 2020, a series of unfortunate events led to the disappearance of thousands of comments from this blog.
Allan believes (insists) that this is his fault. He is definitely not responsible, as the trouble began with a very stupid, careless error on my part. But really, despite whatever errors we both made, the whole mess exists because Blogger's backup and restore system is a piece of crap. In fact, it is not really a backup system at all.
I won't recount the steps that led to this disaster. Suffice to say that in February 2020, all the comments on wmtc from July 2006 to February 2020 disappeared. These dates include peak wmtc, when -- in the golden age of the blogosphere -- a community of up to 50 or more commenters regularly posted their thoughts on this blog. Lively, fun, and interesting discussions often took place in comment threads.
The May 2019 file
I have a Blogger export (.xml) file from May 2019, that, if properly restored, would reduce the comment gap from more than 13 years to nine months -- nine months when comments weren't even that active.
However, the May 2019 Blogger .xml file is corrupted and will not upload. I've created various test blogs, and can import other .xml files, but not that one. And -- an important note -- none of the .xml files have ever imported comments. None. Ever.
An additional issue
After the February 2020 disaster, Allan was able to restore all the deleted posts, but their URLs had changed. This means internal links no longer work, except for posts on the "greatest hits" page, which I manually fixed. It also means that The Lost Comments now had no associated post to be attached to. The text of those posts still exists -- but the posts themselves, with their unique URLs, no longer exist. So the comments couldn't be restored to their original posts, regardless of Blogger's backup capabilities.
No help
Blogger's Help Community has been useless. Several people made some semblance of trying to help, but their answers made it clear that they hadn't read my post and weren't willing to engage on any but the most superficial level. I realize that the problem may not be fixable -- but no one came anywhere close to even trying.
My obsession
Since the comments disappeared in February 2020, I've been periodically obsessed with trying to restore them. I have a post in drafts titled "the lost comments of wmtc: making peace with blogger". There is only that title. I never wrote the post because I never made peace with it.
I now export/backup wmtc more regularly than I used to, and I periodically try to import the May 2019 .xml. I know that's supposed to be the definition of insanity, but it is also the definition of hope.
The plan
Earlier this year, I decided I would copy/paste the comments from the May 2019 file into the appropriate posts. I created a gmail account for this purpose, and I identified December 25-27 as The Comment Project. I don't celebrate Christmas, and three consecutive days off seemed like the perfect opportunity -- perfect enough that I gave up this year's W4R.
My plan was to copy all the comments on a post, open a new comment, paste in the original comments as one long comment, and submit. This seemed totally doable.
Until I opened the .xml file.
I had assumed that comments would appear after each post -- post, comments, post, comments, and so on. Bzzzt. The .xml file contains, in this order: the blog template, all the posts, all the comments.
Comments are not identified according to the post they were associated with, nor with the date of that post, but by the dates of the comments themselves. So if people were coming back to a thread and posting over several days, which is very typical, those comments would be spread out over several dates, and have no identifier to show which post they belonged with.
This may seem obvious to people who regularly work with .xml files, but it was news to me. Very, very unwelcome news.
I tried anyway
Call it tenacity, or stubbornness, or compulsion, it doesn't much matter. I have trouble giving up.
Allan and I copied the entire .xml file into a Word file: 17,490 pages.
Allan then deleted the template and the posts, shrinking the file to just over 7,500 pages. (Allan had to do this, as my computer would have frozen and crashed.)
He then did some fancy find-and-replacing to make the blocks of comments easier to see.
But here's the thing.
When this was a simple copy/paste job, I was willing to slog through it. But now there is decision-making involved. Reading, thinking, and decision-making. I simply do not have the bandwidth. The spoons. The energy.
Like most people who work full-time, my time outside work is limited, and I always feel that I don't have enough time to do the things I want to do. In addition, I have chronic illness that demands I manage my rest and energy levels. Do I want to use hours, days, weeks of my precious free time trying to determine what comments go where and pasting them in? No. I do not.
Still, I can't let go
Despite the realization that I don't want to devote the necessary time to it, I still mourn the loss of those comments, and I'm still considering chipping away at this project.
12.26.2024
things i heard at the library, an occasional series # 42: why i'm not letter-writing this year, part 1 #w4r2024
This is the first time in 16 years that I am not spending Christmas and Boxing Day writing letters. This time of year, I normally participate in Write for Rights, Amnesty International's global human rights letter-writing event. I decided to give myself the year off, for two reasons -- one positive, one not so much.
I've tried many times to organize a group for Write for Rights, but never found enough interest to get it off the ground. This changed with the amazing team now working at the Port Hardy Library. We are offering our customers the opportunity to participate in Write for Rights for an entire month, beginning on December 10, International Human Rights Day.
I reached out to Amnesty Canada, and they sent a great package of swag -- t-shirts, buttons, bandanas, pens, water bottles. Our team created a beautiful display, featuring petitions for each case, and a box for letters.
For every letter they write, customers receive one entry to a draw for a prize package. We do the mailing, and I'm paying the postage as my donation.
The prize package includes a copy of Letters to a Prisoner, a beautiful, wordless picture book about what Write for Rights is all about, which Amnesty sent us.
This program has shown me something about Write for Rights that I had forgotten: many people don't know these issues exist. Many people do, of course. Some folks, after seeing our Facebook posts, have come in specifically to write letters. But for many people, the cases are beyond eye-opening -- they are staggering. They didn't know that peaceful activists are targetted, jailed, tortured, and even killed, or their families threatened or killed, for standing up for their communities.
As people scan through this year's cases, I hear quiet gasps, or expressions of shock and horror. I see people brush away tears.
This program is very labour-intensive for library staff. Multiple times each day, we explain what Write for Rights is, what the cases are, what we are inviting them to do. I've been so impressed with our staff's willingness and energy for doing this. It's a powerful reminder of the role public libraries play in education.
As always, I am grateful to the good people at Amnesty whose Hefrculean efforts make Write for Rights happen.
Stay tuned for the second and unhappy reason I am not letter-writing this year.