Clockwise is okay automated calendar wrangling

The main thing I remember about having an EA for a year was the way my calendar became less a miserable time-sink with the stink of guilt and more a magical, ever-updating guidepost for the day.

The EA and I established a few ground rules: At least 30 minutes for lunch, please never move a 1:1 with one of my direct reports, and please herd things toward the morning where possible. Those understandings in place, it just became my job to go where I was supposed to be.

It has been a few years, and I still feel that loss pretty acutely. Putting together a meeting can take a lot of time, and there’s a tendency to just pick the time everyone’s available, which means that your meetings are creeping earlier and earlier, or people are just helping themselves to half your lunch.

The other problem you end up with is that you have all these extraneous 30 minute blocks that you delude yourself into believing can be productive time. But by the time your last meeting ran over, you’ve sent out notes on the meeting or followed up on something that came out of it, and get a glass of water, you’re just in time to start your next meeting. So the “real work” gets pushed into lunch, or after normal work hours, or in little slices here and there, and then it’s not really quality work because it feels like it’s “extra.”

I’ve tried, a few times, to go straighten out my calendar by consolidating as much time as possible for focused work, but that is laborious and sort of fragile: I invariably book over an odd monthly 1:1 because I didn’t check the time far enough ahead, or don’t notice the other person has a can’t-miss every other week.

I’ve also tried a few iOS apps meant to help with the problem of calendar fragmentation, but they weren’t super smart and were tied into the Apple ecosystem in a way that made me suspicious of them because I am suspicious of how well Apple’s Google Calendar integration works and mistrustful of it working well enough to turn my back on it.

Recently, though, I was trying to find time with a colleague and she said “feel free to book into my focus times … I have an app that puts them there for me,” and that’s how I learned about Clockwise, which is, at root, automated defragmentation of your Google Calendar. After three weeks, I’m a pretty happy user and I’m willing to recommend it to other people, even if just to find some fatal flaw I have not yet found.

The core concept behind Clockwise is that fragmented calendars kill productivity because they don’t allow for uninterrupted deep focus. Clockwise at its most basic is just a tool that goes out once a day, looks ahead at your calendar, and tries to find ways to consolidate all those 30-minute blocks into a longer, more meaningful chunk of focus time. When everything lines up, it shifts calendar items around then protects the focus time it has found for you.

I would be pretty happy with it if all it did was moving meetings around behind the scenes, but there are ways to imbue it with a little more intelligence:

  • You can tell it your meeting hours by day. Since the R&D org I work in has a “no meeting Friday afternoon” policy, I can tell it not to book anything after 12 on Fridays.
  • You can tell it the time range in which you’d like lunch to fall, how long lunch can be, and the shortest acceptable amount of time lunch can fall back to. For instance, I have it set up to consider 11a to 1:30p to be acceptable lunch times, that I don’t mind going as long as 45 minutes, and am also fine if it’s as short as half an hour.
  • You can tell it which meetings are okay to put on “Autopilot,” and which are not. That’s great for two reasons: I prefer to keep 1:1s with my directs or mentees relatively sacred, because I want people to feel like that time is truly their time for them. Second, people have to plan to do work for some meetings, and it can feel disruptive to plan out your work in anticipation of meeting at one time, only to have it shift.
  • You can feed it a few other parameters, such as when you prefer to have focus time (morning, afternoon), how much you’re okay with it moving a given meeting, and whether it should hold travel time.

In addition to those extra smarts, it can do things like color code your meeting types (1:1s, team meetings, one-offs, external attendees), and you can connect your personal calendar to it so that you don’t have to do double-entry for personal appointments: It just blocks them as “busy” so that the time is protected, as is your privacy.

It also shows you the occasional bit of data: How much focus time it found for you, which meetings it moved and why, and who else in your org is using it. One thing I appreciate about it is that it seems to think in terms of finding focus time for other people, too. So the notice I just got telling me that it had moved a meeting explained that it was looking for focus time for me, and also found a time more convenient for the other person, too.

Some caveats and attendant best practices

There’s a certain kind of corporate citizen who is pretty good at optimizing their own life, is blithely indifferent to the suffering that may cause for others, and can even become tetchy or hostile if you do anything that breaks whatever brittle life hack they’ve discovered. Clockwise could be terrible in the hands of these people, and could, worse, sort of paint you to be that kind of person without you even realizing it. During my three weeks of use, I’ve thought about a few ways to use it and how to establish norms around it if a group of people are using it:

  1. It will offer to book all your time for you if you let it, but it will also ask for a max amount of focus time. I do not ask it to book every spare minute so I can balance my need for interrupted “flow” time with other peoples’ need to talk to me outside scheduled meetings. If your goal is a more networked, less hierarchical organization, you should make it easier to communicate outside of a rigid meeting framework, not harder.

  2. You can tell it which meetings can be on “Autopilot” and which should not be. As I mentioned earlier, there are certain kinds of meetings where, if you’re the person with the power, you should consider signifying the importance of that time by not giving it over to a robot to manage. Some people, in my experience, also look to the weekly 1:1 with their manager or mentor like an oasis; or they gauge their emotional energy for dealing with some frustration or setback by how long it’ll be until they can get some help from their manager without going outside the 1:1 cadence.

  3. It’s good to communicate to people that those focus blocks are important to you, but not necessarily inviolate. For my department’s “No meeting Friday afternoons,” for instance, I put this message in my calendar:

“The R&D organization observes a ‘no meeting Friday’ on Friday afternoons. We get that folks from other groups might need to schedule during that time, so please do check in via email or Slack if you need to book into this time.”

Clockwise doesn’t have a way to add a message to focus time events, which is unfortunate because I’d like to be able to just set that norm/expectation automatically. I guess I’ll go find the feature request form. In the mean time, Clockwise does allow you to toggle whether those focus blocks are marked as “busy/unavailable” or “free to book.” Once a group had adequate norms around what “focus time” means to each other, that toggle might be enough.

Final words

At our last 1:1, my boss asked “how’s your battery?” As I thought about my answer, something that kept popping into my head was that recently I’d felt like I’d been getting a lot more done, and so my battery felt pretty good. Like, definitely tired at the end of the day, and definitely going pretty fast on some stuff, but there’s the kind of tired you can get from just knocking stuff down and the tired you can get from feeling like there’s a lot of heat loss, and I reported I was definitely feeling the former.

As I thought about why, I realized it was because for the past several weeks, Clockwise had been finding me these two hour blocks and I was taking advantage of them. Most of them. The first one it found, I actually decided to take a breather and went to the lounge chair I keep in the corner of my office and I fell asleep. After that, I’ve gotten better at just doing a lap around the house, making a cup of tea or grabbing some water, reading the headlines or triaging mail while I waited for the tea to steep, and then spinning up for a good 45-minute block before taking a midpoint break for a few minutes.

The kind of work I was doing in those protected spaces felt better, too. I needed to review some work from someone doing that kind of work for the first time, and I felt more patient and able to just share notes and feedback instead of battling myself over whether to just do it. When I got stopped because I needed to ask a question or do some research, I was able to ask more thoughtful questions. When asked for thoughts, even outside of that focus time, it was easier to slow down and answer them because, I think, having those uninterrupted blocks has an effect on your overall rhythm and cadence. Maybe it’s just knowing that by having a two hour block coming up, you don’t have to ruthlessly optimize every second of your day.

So … several weeks of Clockwise use has been a good experience for me. I definitely recommend it for individual use provided people follow some of those best practices I mentioned, or at least agree to norms around it.

I also see people around me beginning to use it, and see that it has some team-based functionality I haven’t even tapped. The individual use experience has been so good, I’d love to experiment with it managing the meetings of a defined group.

Sealed in

Coffee walks

Evening walk


10 PRINT “Classic Computer Games, No BASIC Required”

Awesome. My first “programming” in high school was editing Super Star Trek to get more photons. I had only a tape drive at home for my VIC20 & no tapes at school, so I couldn’t bring it home to play unless I retyped it.

Fujifilm recently updated the X100V to make it work with its X-Webcam software.. I’d been using X-Webcam on and off with my old X-T2, but had some reliability issues, causing it to drop out in the middle of Zoom meetings so I gave up on it.

WIth the X100V, it’s a simple USB-C connection, the X100V itself has a webcam setting specific to the software, and the camera doesn’t seem to power off or time out, even over long calls. When you do shut down Zoom or whatever it’s acting as an input source to, the camera does go to sleep after however long your power timeout is, so you have to reach up and press the shutter release to get it to wake back up for your next call, but that’s a 5 second process and the payoff is way higher video quality and a nice array of settings: Fujifilm’s film simulations along with shadow/highlight tone, saturation, and sharpness. I’m kind of a Classic Chrome/neutral tones kinda person.

I need to go find an Arca mount for my desktop camera stand to make it easier to grab the X100V for actual, you know, picture-taking.


Years ago there was a Mac mail client called Mailsmith that was all about plain text email. It was mutt’s spiritual cousin, but with a GUI. This morning I am wishing it had survived to become an iOS client. There are none, apparently, that can reliably send plaintext mail.

I don’t want to be too dewey-eyed about poor Mailsmith, though. It was for most of its life just a POP3 client, and if I had one point of huge contention with Mac orthodoxy back then, it was the whole “POP3 is enough for anyone” thing. It took Apple realizing POP would make email a misery for all of its iPhone mail users and sensibly embracing IMAP before that orthodoxy could be broken.

I think Mailsmith tried to do IMAP in the end, but it read between the lines like there was no money in email clients, and no money in untangling innards too wrapped around the relatively straightforward “just download all the mail and don’t worry about other clients hitting the same inbox” charms of POP at its simplest.

I don’t want to care about all that, but do, and I really, really wish there was at least a magic button to press in that just preserved attribution marks and made replies plain text.

Perhaps the most meaningful Apple silicon benchmark of all: I can leave the Paperclip game running overnight and not come back to a throttled page error message.

“Trained to respect bossing and bossiness”

“Working class people who haven’t been to college rarely confront each other by calling each other out. They banter, they joke, they express anger in that egalitarian style that implies they’re ready for an argument. Generally, they don’t correct, because they don’t like bosses and don’t want to be one.

“Middle class people, however, are trained to respect bossing and bossiness, so the result is a version of anti-oppression work that reinforces class roles. That version doesn’t question the effectiveness of ‘calling out’; it comes from being socialized to play the economic role of the middle class: managing, correcting, sorting people into acceptable and unacceptable.”

– “Break out of your class bubble, get training and win!

This crystallizes a lot for me, both in terms of my approach when I have facilitated anti-oppression training and in terms of my reaction to “calling out.”

I was just relating a story to a friend about a time I knew I’d hit a limit and decided to just pull over and sleep. I was driving from Ft. Bragg to Indianapolis right after some kind of field problem that had kept me in motion for several days and nights straight, but headed to a President’s Day party I didn’t want to miss. I guess that was … 25 years ago. Almost half a lifetime ago.

Trek to Shun Fat

We were going to take a walk to Woodstock today, but the sidewalks are in terrible shape and the side streets are still covered with inches and inches of slush and snow. We got to the point where we could either walk the remaining 35 or 40 blocks to Woodstock or just do eight or nine blocks to Shun Fat. We opted for the place with the better snacks and closer walk. We still had to walk in the street, following ruts left in the snow to make it easier.

Shun Fat is great. It replaced one of Portland’s most down-in-the-mouth Fred Meyers. At the old Freddy, you were advised to check your bottle of Tide before purchasing it: It took me two times before I realized people were buying the Tide, taking it home, emptying it out, filling it back up with water, and “returning” it. Shun Fat is just a well-stocked, predominantly Asian market with businesses going in around the core store that are making it a viable, closer alternative to Fubonn.

Anyhow, it was a good walk. Hip flexors were definitely flexed and our snow cleats came in handy. Al has YakTrax and I have IceTrekkers. Both work great and are pretty easy to get on and off in a few seconds once you have the hang of it.

Wow, late to You’re Wrong About, and I love it so much.

The chocolate mushroom latte at Bella’s is pretty amazing.

Smokes in a tree

Out in the cold

82nd Bar & Grill

Springwater and Luther Natural Area

I have started and never finished a few 365 projects, and considered trying again this year, but decided I feel about those sort of the way I feel about New Year resolutions or other things that could be “good for me” but end up becoming a burden as the sense of obligation mounts. I also don’t need to be “forced” to take a lot of pictures. I take a lot of pictures already. Some days, though, I don’t want to take one because I am not feeling inspired.

I thought briefly about doing a “52” project, committing to just a picture a week, too, but that’s not a challenge; that’s just what I do.

I would, however, like to stretch a little, break habits, come at things with fresh eyes. So I’ve landed on something simple, which is to just pick an idea each week and pursue it. Maybe it’s a shooting theme – night, dawn, architecture, lights. Maybe it’s a constraint – a particular lens, some editorial constraint, monochrome. My goal will just be to produce a collection reflecting the idea.

So, this past week, I decided to make it “just light.”

Over the past year or so I’ve put a lot of effort into making presets and playing with color in my images. Though I haven’t set out to rigorously A/B test any of it, I do have one preset that gives my images a particular character, and really, really works for people. I’ve learned a lot about editing in general, and I’ve let myself explore a lot.

I don’t have a real problem with that. I firmly believe that darkroom work is just part of the process of making a good image. It may be delightful to get exactly what you want out of the camera, but it’s beyond okay to explore everything that raw image can be.

At the same time, and especially where color is concerned, I’ve found myself sometimes getting lost in the edits. I lose track of what my camera does, and sometimes I think my presets are a little heavy-handed with color. So my inaugural “idea week” is “Just Light.” I set a few constraints for myself:

  • I shot with my Q2’s “Natural” preset. If I were shooting with a Fujifilm camera, that’d probably be the Astia preset. The JPEGs out of the Q2 aren’t spectacular, so I did give myself a bump on the color setting in camera.
  • In post, I let myself work with contrast, highlight/shadow tone, clarity, texture, and vignette. I didn’t touch vibrance, saturation, or any color controls.
  • I didn’t touch any presets or film simulations in post.