Perhaps the most Seattle thing I’ve done, in a year I’ve spent more time in Seattle than LA, is attempt to make First Contact with the Capitol Hill murder.

Seattle has an unusually high density of urban crows — the suburb of Bothell has a particularly huge co-roosting population, but they’re out in force across the greater metro area — and human residents are quite fond of them. Crows recognize and remember humans who treat them well (or badly!), and urban crows have a lower baseline fear of bipedal apes that makes them particularly amenable to friendly overtures. University of Washington biologist Carl Bergstrom has gone as far as to recommend befriending crows, and suggests starting with an offering of shelled unsalted peanuts.

So when I happened to see shelled unsalted peanuts on offer in a corner of the QFC produce section, I bought a bag. I spend most Seattle workdays on my laptop at the table in the apartment’s dining area, with my back to the sliding glass doors that let out onto the balcony. I laid out some peanuts on the little table on the balcony and, soon enough, heard visitors outside.

I’ve been in and out of town since that first visit, and so not able to keep the peanuts available continuously. It’s not clear how much the crows recognize or remember me through the balcony door; and so far I haven’t remarked any distinguishing features that let me identify individuals. They come singly or in groups of as many as four, and often there are others who swoop by to consider the peanuts.

They are still quite skittish if C or I are standing too close to the balcony doors, but they’re pretty bold when I’m seated at my laptop with my back turned. I do think they know that one or both of us are the source of the peanuts. It’s not uncommon, now, for a crow to land on the balcony while my back is turned and then call — maybe asking for a refill? A couple times crows have remained perched on the railing while I grab a handful of peanuts, flitted away to a nearby rooftop or tree just at the moment I open the balcony door to step out. From there, they’ve watched me lay the peanuts out on the table, go back inside, and shut the door before flying back down for more snacks.

So it’s a process, and I think we’re building rapport. I don’t have much more time in Seattle before I start the spring semester in LA, but I have a feeling that the next time I’m back in town, crows will be ready for me.

This has been, for fairly obvious reasons, a hard year. Most of the institutions that define what I do for a living have been weakened to the point of desperation, if not outright dismantled — some inviting the vandals in, some forcibly invaded and hollowed out. It was a year in which I tried to explain to students that most of the research projects on our campus were under threat, threw together a local pro-science satellite rally, squinted at the text of the US Code to no discernible effect, wrote plaintive op-eds for the newspaper I read back in high school, tried to plan for what I’d do if immigration enforcement agents demanded entry to my classroom, and pressed on with projects whose long-term future is uncertain at best.

And yet, by any objective measure, it’s been a very fortunate year. I ran the Boston Marathon, and had a pretty good time of it, even if it wasn’t a personal-best time. I hosted a collaborator for a guest seminar on campus, and we took a day to drive out to the desert and see wildflowers, including blooming Joshua trees. I landed a sabbatical semester for the fall, with plans that let me spend most of my time with C in Seattle, from June onwards. We road-tripped north through Yosemite and Crater Lake National Parks, both first-time visits for me, and then took a long week in New England and New York City. I spent most of another week in Georgia for the Evolution Meetings, where I gave a high-pressure plenary that seems to have gone over pretty well.

I saw one student-led project from writeup to submission, review, and acceptance for publication next year; as well as the publication of a pretty big discovery about Joshua tree physiology and an opinion article I’d been working on for a while. I spent a week in New Haven with a friend and collaborator at Yale, where I started building my first-ever analysis package for R, and we made major progress on another long-gestating project. While I was in-state I also drove up to the University of Connecticut to see a bunch of old friends and collaborators and give a seminar, which seems to have gone over pretty well. And I spent two gray, rainy weeks of Pacific Northwest December on a writing retreat at the Friday Harbor research station on San Juan Island, where I wrote a fair chunk of a new project proposal.

So, strictly speaking, it was a pretty good year, professionally and personally.

It was also a year punctuated with wonderful experiences in the natural world. When we pulled over to photograph the view on the way out of Yosemite Valley, I spotted a new-to-me lupine with spectacular yellow and pink flowers on the roadside bank. During our New England trip, C booked a spur-of-the-moment cruise out of Bar Harbor to see puffins on a nearby rookery island; when we got back to dry land we rented e-bikes and rode into Acadia National Park, and we caught a brief glimpse of beavers at work on a lodge.

Later in the summer, on the return leg of a hike to Snow Lake in the Alpine Lakes Wilderness, we turned onto a spur trail for a view over the lake, only to realize there was a collared pika watching us from atop a boulder just a couple yards away. On an October trip to Vancouver, C took me to a spot he remembered in the heart of Stanley Park, where so many tourists have offered birdseed to the chickadees that you can stand by the trail, hand outstretched, and the birds will fly down and alight on your palm to see if you’ve brought them snacks.

So many of these moments were that much better because I got to share them with C. Shuttling between LA and Seattle hasn’t always been ideal, and truly the best benefit of my sabbatical is how much of it we got to spend in the same location, taking adventures where inspiration struck rather than having to plan around interstate travel.

We hiked to mountain lakes, and foraged for blackberries in a Seattle city park — which I baked into pie the same day. We joined friends for movie nights and dinners, in board game cafes and at neighborhood bars. We planned for grocery trips and coordinated workday schedules and watched increasingly obscure iterations of The Traitors.

Lots of other folks made it a good year, many in ways that don’t leave much photographic evidence. The Los Angeles Frontrunners’ regular group runs define much of my social week in SoCal, and the extended time in Seattle has let me settle in with that city’s Frontrunners, too.

There were some nice moments of connection with family, which I don’t get in LA — I have cousins in Seattle, and my more immediate family on the east coast, and we checked in with all of them.

The east coast trip for sabbatical work also included a lot of quality time with friends from multiple stages of a scientific career that has taken me between different states and even into another country. Extended time with a current friend and collaborator in New Haven, and the UConn visit included the first time in years seeing folks I’ve known since my first year of graduate school.

There were moments of broader community connection, too. Over months walking through Capitol Hill I got to feel like I knew a neighborhood on foot, and established some regular stops where baristas or cashiers got to know me. C and I joined the local iteration of historic nationwide protests against our thuggish government, and a month later I watched Seattle elect an experienced, serious progressive for Mayor, alongside a city council that will, maybe, help make progress happen.

This experience of 2025 reflects, really, a lot of privilege and a lot of very good luck. As I look forward to the new year it feels incredibly fragile, and I can see the weak points, where breaks are most likely — the precarity of research funding for my lab; the challenges of dear, personal relationships that cross state lines; the mounting obstacles to teaching students how to find scientific fact and reasoning in a sea of online slop; the looming threat of new and greater violence and vandalism from the people with the most power in this country.

Many of these weak points, though, are also where I draw the most strength. I’m grounded in my scientific work and my classroom engagement with students. I take strength from the people I can call on to go for a run or get on a phone call. I find some relief in the focused challenge of chasing a bird with my camera — a brown creeper that circled a tree trunk just out of reach for long minutes, or a belted kingfisher that taunted me from one end of Friday Harbor’s marina to the other.

And I find perspective in numinous visions of mountains on the horizon — Mount Roosevelt rising over Snow Lake, or Mount Baker resolving into view as the San Juan Islands ferry sails clear of the clouds on the way into Anacortes.

Any one of these moments seems too brief to matter, as light as a chickadee perched on my fingers, flitting away as quickly as it landed. This year, though, they added up to what I needed. I have real hope — I have to hope — that there will be more in 2026.

Well, here’s the funny thing: If I’d been a reviewer on that paper, I’d have said that statement in the abstract was an error. I’d probably also have said that it was a dangerous one.

I suspected right away that this description of the survey results was incomplete, at best. Indeed, the text of the C&EN article has a distinctly different spin than the headline or the paper’s abstract: “When asked if they felt they were forced to modify their manuscript with text they thought to be incorrect, 22% of survey respondents said yes.” Authors making a change they thought to be incorrect is not actually the same as introducing an error! It may simply reflect peer reviewers disagreeing with an author’s interpretation of results in the paper under review, and the editor siding with the reviewers in that agreement.

This is the degree to which authors can be “forced” to make changes they don’t like to a paper — when expert reviewers ask for a change and the editor who oversees the review process decides that the paper will only be accepted with that change made. Authors are free to take their paper to another journal if they feel strongly enough about the disagreement, though this is not the path of least resistance. It’s a pain to start review over from scratch at a new journal, and if you want to publish sooner, your quickest route is to try to do what reviewers ask even if you’d rather not.

Does Bordignon’s paper have a softening from its abstract to its actual text that parallels the C&EN shift from “errors” to “changes they thought to be incorrect”? I have, unfortunately, no subscription access to Accountability in Research. Fortunately, Bordignon followed best practices and provided supporting materials on Zenodo that include the survey questions. The relevant one is Q13: “During the peer-review process of your own papers, have you ever made changes to your manuscript that you thought were incorrect (i.e. introducing an error), but you did them in response to pressure from reviewers?”

That is indeed more complex than the interpretation in the paper’s abstract. There’s a difference between “changes … you thought were incorrect” and “introducing an error,” despite the parenthetical offering the latter as an example of the former. Speaking as an author of peer-reviewed papers, “introducing an error” would certainly be a change I “thought was incorrect.” But! I have absolutely had reviewers ask me to make changes I considered incorrect, and made them — because the reviewers and I disagreed on a point where there isn’t a clear factual answer.

Many such questions arise in the design and execution of a scientific project and the interpretation of its results. Reviewers have asked me for changes to things like figure design, or the use of specialized terminology, or how I communicate the strength of confidence in a statistical test result — or even what conclusions I could legitimately draw from the data. I have strong opinions about writing and figure design, and I know all too well they’re not universal; but there may also be ambiguities in choosing methods and statistical tests. Some examples, off the top of my head:

• Using frequentist versus Bayesian methods — Yes, there are specific cases where this choice can change your risks of a false positive; but in many situations, frequentist methods and their Bayesian equivalents will give the same qualitative answer, and which you trust more is down to personal preference.
• Modeling a process via detailed simulation versus a more abstract analytic model — Here again, there are pros and cons to each choice. A simulation can give you granular control of complex details; an analytic model can give you an elegant description of relationships between the variables that are most important. (Many papers present simulations and analytic models of the same process for precisely this reason.)
• Displaying variation in treatment groups — There are many, many options for comparing the central tendency and variation of measurements organized by treatments. Which you choose depends on your sense of what will optimize clarity, emphasize between-group differences, or even specifically indicate when groups would differ significantly in a standard t-test. For the most part, though, there are no truly wrong choices, so long as the resulting figure isn’t actually deceptive.
• Selecting “candidate loci” from a genome-scan for association with a trait or environment — In genome-wide association studies testing thousands or millions of loci, even after you raise the threshold of “significance” to account for multiple testing, you may have many, many more loci associated with the trait or environment of interest than you can investigate individually. You can triangulate with other data or analyses to narrow the list, but how you choose a subset for further study is simply a judgement call.

The whole point of peer review is that there will be questions like this, on which reviewers and I may disagree even if we’re all experts in a narrowly defined field. If an editor feels reviewers’ opinions are better aligned with the consensus of our field, I can either accept that judgement or find a venue where I think I’m more likely to find agreement with my own way of thinking. However this is the real value that I get from peer review, as an author: Even when I’m sure I’m in the right, I may actually be wrong! Peer reviewers are there to tell me when I’m at risk of being wrong.

(Does peer review always accomplish this? Of course not. We’re all fallible humans muddling through a terrifying and unknowable universe. But the goal is that multiple of us are more effective at the muddling than any one of us alone.)

So anyway, Bordignon asked research chemists a question that encompasses both “did peer review force you to say something false in a paper” and “did peer review require you to change a paper in a way you didn’t like but couldn’t defend to an editor” — then foregrounded only the former, much more alarming version of that question in reporting that 22% of her survey participants said “yes.” I think I’ve spent enough text explaining why I think that choice in itself is an error. Why is it a dangerous error?

In short, it’s dangerous because endangering public trust in the scientific process — of which peer review is a critical part — has higher stakes than at any point in my scientific career. The Trump Administration is framing an ongoing assault on research funding and academic freedom as campaign for “gold-standard” science, which is not so much “spin” in the old political sense as an outright lie: placing political apparatchiks in positions to decide what research is funded and how its results are reported. The Secretary of Health and Human Services — who has no business remaining in that role — is using his national platform and institutional power to tell people that science isn’t trustworthy. The Environmental Protection Agency is revising the actual evidence out of its evidence-based understanding that climate change poses a threat to human health.

Work that undermines the credibility of peer review is ammunition for these ascendant campaigns against public health and environmental protection. That’s not to say no one should criticize scientific processes or publishing — there’s plenty of that to be done, and self-critique is how science gets better. But now, more than ever, ensuring such criticisms rest on a rock-solid foundation of evidence is a matter of life and death. Claiming that peer reviewers have made as many as 1 in 5 scientists add errors to their work doesn’t rise to the standard we desperately need at this moment.

I am not a fan of large-language model chatbots. I’m enough of a hater, in fact, that I don’t like calling ChatGPT and its LLM-powered kin “AI” — they are a particular class of products of a particular form of machine learning, which guess the correct response to a query as informed by associations between words and phrases in vast volumes of training text. One of the most painful lessons of the last couple of years, I think, is that what I’ve just described turns out not to be anywhere as close to “intelligence” as it appears.

I digress; the distinction is important, but it’s not exactly my point. My point is that it recently dawned on me that the LLM chatbots are the latest iteration of a now multi-decade process of big tech companies trying to fit the whole Internet into a box that they own and control.

The first version of this was search — Google and its less successful competitors wanting to be the one website you went to before you went to any other website, so you would see the ads they’d placed alongside their search results. This seemed like a good bargain, since Google was very good at indexing and ranking the rest of the Internet to help find the external sites most relevant for any given query.

Then came social media, mostly Facebook and original-flavor Twitter. Social networks initially gave you links to other websites, selected by people who you knew personally, or who you followed for their expertise or taste (broadly defined, in both cases). This meant you could learn about things to read or watch on other websites, rather than just finding the things you searched for. It was, like search, initially a pretty good bargain for some ads in the sidebars or even mixed directly into the posts from people you’d chosen to follow.

The original bargain of both search and social sites — ads, alongside links to other things of interest — broke down because both Google and Facebook could show more ads to people who stayed on their platform instead of following links to other sites. So search sites built in “summaries” on frequently-searched topics, up to and including just straight-up showing you information pulled from external sites on the search results page. Social networks tried to get people to publish directly on their platforms (I’m old enough to remember when Facebook was recruiting news organizations to publish articles as Facebook posts), and eventually down-ranked or outright hid external links in favor of posts within the platform (the platform formerly known as Twitter is now infamous for this).

None of this is news to the kind of Extremely Online people who may have read this far, inasmuch as we’ve all watched it happen. It’s paradigmatic enshittification: build something valuable, then make it difficult to leave, and extract as much money as possible from the fact that you’ve drawn a big online audience into the walled garden of your search engine or your social network.

What does it have to do with LLM chatbots? It’s this: they are, or aspire to be, the ultimate walled garden.

The models behind LLM chatbots are trained on as much freely-available text as OpenAI and their peers can obtain. “Training” a LLM summarizes that huge corpus of texts into associations among words and phrases, so the chatbot has a basis to choose a likely-to-be-correct response to any given text input. In other words, the model is an attempt to reduce the training corpus into a single thing that you interact with through their chatbot interface. ChatGPT provides dutiful caveats about checking results with external sources, but the idea of these things is very much that their chatbot can give you all of the information you’d otherwise find in an extended search over the open web. The goal is that you never have to leave the platform.

The value in this, from the perspective of the chatbot purveyors, is not (yet) to sell your attention to ads on the chatbot page or (yikes) somehow folded into the responses. Their business model so far is that you’ll pay to chat with the bot. Which means the fundamental function of the model is to compress the open Internet into a box small enough that it can be sold back to you. Whatever other pie-in-the-sky visions the chatbot makers have for the technology — or wish to sell to investors — this is what the product is right now.

On the one hand, this is antithetical to the reasons I want to use the Internet, as a researcher. I don’t want my sources of information filtered through an algorithm I can’t parse or control — the LLM training — and summarized by the unreliable narrator of a chatbot, any more than I would write a review article using only notes taken by a student assistant. I want to be able to read the actual sources, dig up the earlier works they cite, and root around in the supporting data if I’m so inclined. (But, it occurs to me, this may not seem like such an obvious shortcoming to corporate executives who experience “research” mostly as briefings and memos assembled by their assistants?)

On the other hand, even if the LLM behind a chatbot could perfectly communicate the contents of the training corpus, it would still be an attempt to put that training corpus — the training corpus they scraped from the open Internet — in a box and sell it back to you. After watching the rise and demise of previous attempts to build walls around the garden of the Internet, I don’t know why I’d ever accept that bargain.

We spent this June more on the road than otherwise. C drove down from Seattle over Memorial Day weekend, and after I spent a workweek packing for an extended stay on Puget Sound, we road-tripped north. We only had a three-day weekend, but we strung together some sightseeing stops along the way.

We had an overnight stay in Yosemite National Park, where I finally saw the Yosemite Valley — and not one but two new-to-my-camera lupine species, and a very cooperative nuthatch, the headline image for this post.

From Yosemite we drove north, and detoured for Crater Lake, which I’ve never seen at all. There were still multiple feet of snow at the summit visitor center; we crunched over it for photos, perused the gift shop, bought a couple coffees, and drove on.

The weekend after arriving in Seattle, we flew cross-country to Boston. C had wedding invitation from an old college friend — a lovely ceremony on a farm-turned-event-venue in rural New Hampshire. From there we drove our rental car toward Bar Harbor, where we’d booked a bed and breakfast for most of the week. We detoured en route to take the cog railway up Mount Washington, a precipitous trip up to a summit where the winds were so strong we could barely stand upright for a photo at the top.

Arriving in Bar Harbor that night, we parked at the bed and breakfast and didn’t get into the car again until we left three days later. We could walk from town right into Acadia National Park, and over our time there we hiked from the B&B to the summit of Cadillac Mountain and back, took a boat tour past lighthouses to a seabird rookery full of Atlantic puffins, and rented electric bikes to ride almost the entire length of the wide graveled carriage roads that wind through the National Park.

From Bar Harbor, we drove back to Boston, dropped the rental car, and took the train to New York. Over two nights there, we caught a couple of shows — Cabaret on the Friday, a transcendently silly adaptation of The Pirates of Penzance on Saturday — and then flew back to Seattle. I had three working days in town before flying back east for the Evolution meetings, and got back from that jaunt just in time for Seattle Pride, on the final weekend of the month.

It was a good month of travel; it’s good to finally be home.

I have a new op-ed at LNC|LancasterOnline, making the case for the “curiosity-driven” science that the National Science Foundation has supported through much of my adult life — and which is under dire threat from cuts proposed by the Trump Administration and the budget bill under consideration in Congress right now. In it, I discuss some of the possible long-term applications of my lab’s research on Joshua trees, which seem at first like they might be too weird to tell us anything helpful in daily life:

Joshua trees’ pollination by a single species of moths serves as an informative contrast to plant and pollinator interactions that play out in more common, more complicated situations, such as pollination of fruit and nut trees by wild insects and domestic honeybees. By studying Joshua trees’ simplified system, my graduate mentor learned how cooperative relationships like pollination stay cooperative, with two different species trading resources and services, even when they have incentives to cheat.

My lab has also studied how weather influences Joshua trees’ very sporadic annual flowering. Most years, they either flower prolifically, or not at all — and until recently we didn’t know what made the difference between bloom or bust. For that project, we developed software to use machine learning models trained with easy-to-collect data, which may work well for many other species of plants. That could be helpful in agriculture, or in planning to protect rare plant species, or even in understanding how the environment limits where different species can live.

But — and this is the important part — work with Joshua trees and hundreds of other peculiar creatures in distant habitats is important even if it doesn’t pan out into applied discoveries.

Of course, none of these applications of Joshua tree research may pan out. For every Thermus aquaticus [the hot-spring bacterium whose chance discovery enabled modern genetic research] there are hundreds of scientific projects that end in nothing more than a peer-reviewed research article and some fond memories of fieldwork. But we need those hundreds of curiosity-driven studies to find that one lucky, world-changing discovery.

This column is a new iteration of the connection I made with my old hometown newspaper thanks to the Science Homecoming campaign, and anticipates the McClintock Letters initiative rolling out later this month. Go read the whole thing, and — please — call your congresspeople to ask that they preserve funding for NSF’s support of curiosity-driven science.

Monday, I ran the 129th Boston Marathon. It’s something like 15 and a half years after my first marathon, and it’s taken me that entire time to get to Boston.

I ran my first marathon back in October 2009, in Portland. I’d tried a spring half marathon and survived it, and found a simple enough training plan to work my way up to a 26.2 mile (42km) distance, running through the rolling Palouse hills beyond the University of Idaho campus in Moscow, Idaho. Portland went well enough that I signed up for another the next year, and another the year after that.

For most of a decade I did about one marathon a year, with the exception of a possibly over-ambitious 2012. I trained to survive the distance but not really to manage my pace, and generally didn’t come close to hitting the time I’d need to qualify for an entry to Boston — sort of a universal benchmark for marathon performance. Boston is an old race, and a big one, and its organizers ration space on the race course by setting a minimum performance standard to apply for a registration. The closest I came was 3:14:30 on the 2015 Twin Cities Marathon, 9 and a half minutes too long for my age bracket.

Then I moved to LA, and started running with the Los Angeles Frontrunners. Social workouts are a huge improvement over solo, it turns out, and they come with a lot of peer pressure — the Frontrunners have many veterans of Boston, and conversation at group runs usually turns to upcoming race plans. I started choosing my annual marathons with an eye to course speed — net downhills, comfortable running surfaces — and training for speed and strength and pacing in a systematic way.

I ran the lovely gentle downhill course of the 2023 Mountains 2 [sic] Beach Marathon from Oxnard to Ventura, California, in 31 whole seconds less than the Boston threshold; and then that wasn’t enough to win a registration. A “Boston qualifying” time lets you apply to register, but then if more people apply than the race can accommodate, the organizers set a lower cutoff threshold for registration. In 2023 I needed to be about five minutes faster for that second cut.

I came back around the next June, for the Light at the End of the Tunnel Marathon, on a rails-to-trails path through Snoqualmie Pass above Seattle, Washington — green and cool in the shadow of the Cascades, and a nice gentle downhill grade. That, and my training, got me to 3:02:21, fast enough to survive the second-round cut when I applied for Boston in the fall.

Training up for a marathon run in late April was going to be challenging anyway — who wants to start workout runs in December? — and between the natural and political disasters of this spring, I did not turn in the my best preparatory performance, by a fairly long shot.

The Boston course, through a series of small New England towns to downtown Boston, turns out to be very pretty but sort of brutal. It starts with a long descent that makes an over-fast start feel like no effort, then transitions to gentle but relentless rolling hills cresting to a big climb at “Heartbreak Hill” around mile 21. And it’s all on pavement; I trained on much tougher topology in Griffith Park in Los Angeles, but almost all of it nice soft trails. So by the top of that last big climb my legs were dead and I didn’t have much left to give. I walked a fair chunk of the home stretch — though I did manage to save enough effort for a jog on the final mile, and my finish time was far from my worst-ever. (Though also, this was the first event in a while where I’ve been in the slower 50% of my age bracket!)

I’m happy I did it, though. The course was lined with cheering crowds truly the whole way, a level of community support I’ve hardly ever seen. (Maybe in the Twin Cities?) And Boston is convenient for family — Mom and Dad drove up from Lancaster County, and my brother and sister-in-law drove in from the suburbs with my nephews, and of course C flew out to almost literally catch me at the finish.

Once you’re in shape to run the distance, running a marathon is mostly about pace management, knowing what effort you can give and metering it out. That’s more or less what I’ve ended up doing with my preparation for Boston 2025; the result is far from my best marathon performance, good enough as a race experience. The real work, and the accomplishment, was getting to the start line.

For all the good that seems to have done.

Anyway the Smitten Kitchen Purple Plum Torte is perfect for a last-minute dessert because its ingredient list is so simple, you can run it down almost in your head and compare against what you know you have back in the kitchen at home. You’ll just have to make a detour on the way back from brunch to pick up some plums.

Oh, well, and eggs. Dammit.

The second step, then, is making the detour for groceries, and discovering that the pan-Asian grocery midway between brunch and your apartment has not one but two types of plums in the produce section, so you buy some red ones and some golden ones. They don’t have to be perfectly ripe, or even perfectly presentable. They’ll bake into colorful mush surrounded by juice-soaked cake. Pick out a pound or so of each color.

Grit your teeth and add a half dozen organic eggs, priced at fully $1.50 an egg, to your basket. Then carry on home.

When you get home, preheat the oven to 350°F.

Wash the plums and pit them, maybe cut them into quarters. It’s some nice manual work to do while you compose the five bullet points you have to email in on Monday morning, describing what you did at work last week to someone who doesn’t have the inclination or clearance or to actually understand what you do for work.

Pile the washed, pitted plums in a strainer in the sink, and leave them there for the time being.

Next, make the batter. Soften a stick of butter in the microwave, because who has time to wait for butter to soften to room temperature? Put a cup of sugar In a midsize mixing bowl and beat in the softened butter with a fork, until it’s well combined — nominally it should be fluffy, but it’s okay if you don’t have that kind of forearm stamina.

Beat in $3.00 worth of eggs, one at a time.

Mix in a cup of flour — all-purpose unbleached is just fine — and a teaspoon of baking powder. No, wait, soda. Check the recipe again. Okay, yes, right, it’s baking powder. Stir until you don’t see any dry material, scraping down the sides of the bowl.

Grease a pie tin, or a round cake pan, or a tart pan with a reasonably deep rim, or a springform pan. Pour in the batter, and spread it around to more or less even depth. It’ll rise as it bakes, but you can set it on a cookie sheet in the oven to catch any drips.

Retrieve your plums from the sink, and plop them into the batter. Alternate the colors for a pretty pattern. Discover that you haven’t spaced them correctly and shuffle them to get a nice red-gold arrangement. Don’t worry too much about moving the batter around, it’ll all resettle as it bakes anyway.

Make sure you catch any inventory stickers still attached to the plums. Squint at the fine print on one of them to find the origin statement. Apparently we import plums from Chile? Guess you’d better enjoy them while we still do that. Eat a couple slices that didn’t fit in the pan, you’re better off with too many plums for the torte than not enough.

Dust the plums and batter with cinnamon and some more sugar. Don’t skimp.

Put the whole shebang into the oven on a cookie sheet. There’s gonna be a few drips, those plums are juicy.

Bake for 50 minutes, and try not to doomscroll while you wait. At least read some long-form hard news, not another thirty pages of commentary. The New Yorker has a piece about all the scientific research that’s being canceled, and another about the firing of US Forest Service staff who protect nature and fight wildfires, and an analysis about the legality of deportation for political speech, and an interview about all the lifesaving international aid that is no longer saving lives. Think for a bit about what the opposite of saving lives would have to be.

Check the torte by sliding a knife into the cake that bubbles up around the plums. If the knife is more or less clean, it’s done, you can take it out of the oven. There are indeed a few drips on the cookie sheet. The torte is not exactly pretty but it’s golden brown and sparkling with almost-caramelized sugar, and it smells lovely.

Let the cake sit out to cool the rest of the afternoon, then wrap it in foil to bring with you to the dinner party. Pick up a quart of good vanilla ice cream on the way.

Enjoy dinner with your friends. Find out how they’re holding up. Compare notes on your calls to Congress, and whether you’ve heard about upcoming protests that might get some attention. Wonder how much worse things will get.

Clear the dinner dishes and slice the torte. It won’t come out of the pan neatly, but you can spoon piles of baked plum and plum-soaked cake onto dessert plates. Add a scoop or two of ice cream on the side.

Discover, together, how the plums and cake have baked together. They’re probably a bit tart, especially if the plums weren’t quite ripe. But some tartness should go well with the sugar-crusted cake and the ice cream.

As you finish and clear the table, make sure to make plans to do this again soon.

Cross-posted from The Molecular Ecologist.

Here’s a new one for my publications list: the Op-Ed pages of my hometown newspaper. I’ve spent the last weeks calling my congressional reps, and hassling other people to do the same, over the Trump administration’s vandalism of research funding (alongside its vandalism of just about every other function of the federal government), but it’s hardly felt like enough. One new option presented when I happened across Science Homecoming, a project to recruit scientists to speak out in support of federal research agencies in the newspapers of towns where they grew up. As Science Homecoming points out, local newspapers continue to have a huge audience across the country, and that’s an opportunity to reach people where they live, with stories that show how the current crisis impacts their local communities.

So I looked up the opinion section editor at LNP/LancasterOnline, the modern incarnation of the paper my parents have subscribed to since I was old enough to read it, which serves central Pennsylvania. I emailed her a pitch that I’d put together following Science Homecoming’s suggestions, and she wrote back to ask for a full column almost immediately. (The topic was already very much on the editorial staff’s radar.) A bit more than a week later, my column is online and in print, alongside a parallel piece from two geoscientists with local roots, on the front page of the Sunday Perspectives section.

I wrote it as a sort of thumbnail science memoir, recalling how I first got excited about studying the natural world thanks to a high school biology teacher who took the class outside to learn the names of common wildflowers. Federal research funding made it possible for me to follow that dream, but today’s budding botanists won’t have the same opportunities I did if the Trump administration’s policies stand:

My journey from Manheim to the Mojave, inspired by Mr. Longenecker’s wildflower walks, was really made possible by the U.S. National Science Foundation. Grants from that federal agency supported research experiences I had as an undergraduate student, as well as the work I did to earn a Ph.D. at the University of Idaho, and then postdoctoral research at the University of Minnesota before I ended up at California State University Northridge. The biggest single source of support for my own lab has been a National Science Foundation grant, and my research plans for the next five years and beyond are laid out in project proposals I’ve been working to submit.

Now, however, the National Science Foundation and the National Institutes of Health — the bigger federal agency that funds biomedical research — are under unprecedented threat from funding freezes and cuts imposed by the Trump administration.

I’ll send you to LancasterOnline to read the whole thing. And, fellow scientists and technical professionals, let me encourage you to take up the Science Homecoming banner — it’s one more way to get the word out about everything that’s at stake right now.

Occurred to me this morning that I haven’t done a retrospective of the past year’s Flickr photostream as I did last year for plants, and birds, and mammals, and landmarks — and while I’m not going to manage that for 2024, at this point, I can and should still post my favorites. I’m getting a bit more comfortable with the camera, and the processing options in Adobe Lightroom, and I think I got some mighty nice results.

These are presented mostly in chronological order, with the exception of the spectacular action shot leading things off, which is from a Thanksgiving weekend hike. They’re not quite (just) the best-of-the-best; I suspect that list would mostly be birds, given the extra challenge of getting good shots. But they do hopscotch through a year with a LOT of travel (Munich and Montreal!) and visits to many beautiful natural landscapes. For many, many more photos, go directly to Flickr.