back at it

I'm working again. It's Deere, which I didn't see coming and but then like of course it is, it's the place where people know what my work looks like. No grand return either, no team, no design system. Contract work, small pieces. Landing pages. And a run of sessions training stakeholders on some new documentation system they're rolling out for department portals, which mostly means teaching people who liked the old thing to stop emailing Word files at each other.

Two years ago I was shipping a component library used across the company, and now I'm building landing pages and running screen-share trainings. There's a part of me that's bitter about that and I wrote it in my head plenty of times this month. But I am in no place to be ungrateful for a job back in this industry, it's work, it's boring work done well, but the checks clear, the two-year gap on the resume has an end date and I'm not doing DoorDash and UberEats anymore. Thank you Matt.

The trainings surprised me. It turns out two years of explaining myself in interviews made me better at explaining things in general. I watch someone go from hostile to comfortable with a tool in forty five minutes and it scratches something the code never quite did. It's not something I have really any interest in pursuing though. I want to write code. Well, I want to pay my bills.

Small entry for a small chapter. But it's the first one in in a long time I didn't have to talk myself into writing. I need to be writing more.