It is unimaginably hard to […] stay conscious and alive in the adult
world day in and day out. – David Foster Wallace, This is
Water At the heart of my management philosophy lies a simple belief:
people are working as hard as they can. It’s a lazy assumption to assume people are lazy. Especially when
burnout and overwork are so common. And that’s why 1-on-1s are so crucial for engineering
managers. Once a week, you get to reconnect with each person on
your team. But it’s all too easy to have another pointless
meeting. So, here is my kludged-together process to generate valuable 1-on-1s.
I’ve honed it over time as a new(ish) engineering manager. I hope it
will be helpful for both engineering managers and individual
contributors. I follow the GitLab handbook rule: No
agenda; no attend…a. When meetings lack an up-front agenda, I wonder whether anyone
thought about the meeting at all. It’s a meeting smell. It warns me:
this meeting is about to waste my time. So, for my 1-on-1s, I use a simple agenda formula—Purpose,
Outcome, Process (POP): I have a printable
checklist for 1-on-1s. Everyone has access. I buy tons of cheap
three-prong, twin-pocket file folders—every person on my team gets
one. Every workday, I review my calendar and print off a copy of my
checklist for each of my 1-on-1s. During the meeting, I take notes at the bottom of the checklist. And after the meeting, those notes go into that person’s folder. I highlight any TODOs I take during the meeting and
add them to my handy dandy Ugmonk Analog. 🎒 All my 1-on-1 gear: If a 1-on-1 is never awkward—if the discussion is never
challenging—you may be avoiding tough topics. So, I built a thing that forces me into the danger zone. I braved far too many “awesome 1-on-1 questions”-type listicles and
distilled their wisdom into a small web tool. It
gives me a linkable question to share during my 1-on-1s. Toward the end of the meeting, I’ll often share a question from the
list. Some of the best ideas, initiatives, and experiments we’ve tried as a
team come from these questions. Doorknob comments are tantalizing tidbits dropped right as you’re
about to end the meeting—when your hand’s on the doorknob to leave (or
hovering above the “end call” button). It’s easy to glide right over these comments unless you’re watching
for them. Parting volleys like, “I guess I’ll get back to it—if I could ever
get my MR reviewed,” or “I sure wish we’d kill that project.” These comments may seem like passing thoughts, but it’s possible your
direct reports spent the whole meeting amping themselves up to say
something important. And it’s your job in 1-on-1s to listen and
learn. It’d be a shame to lose these insights in the shuffle from one
meeting to the next. Reasonable people have a lot of reasonable-sounding objections to
1-on-1s. The solution here is to get curious. What could make this 1-on-1
better? Of course, asking that question is a surefire way to make a 1-on-1
even more unbearable. So, instead, I turn to my favorite awkward
question: what project are you most proud of? If you listen to the answer, it often cuts right to what a person
values. If they’re proud of their big solo rewrite, maybe they want more
independence and challenge. If they’re proud of the small tweak they
made that saved 100s of hours of toil, maybe they’re searching for more
impact. Of course, you have to be genuinely curious—you have to dig into
these answers to learn anything. And that’s the only secret of successful 1-on-1s: if you want
your direct report to care, you have to care. If you want to have interesting 1-on-1s: get interested. To see posts by date, check out the archives
💼 My basic agenda for 1-on-1s
📓 My note-taking and TODO system for 1-on-1s
😬 To talk about hard topics, lean into awkward questions
🚪 Watch out for doorknob comments
⚖️ 1-on-1 objections
To see posts by date, check out the archives
All I need in this life of sin is my AlphaSmart 3000.

When I decided to develop a daily writing habit, I bought a toy keyboard.
It did not go well.
To begin with, I knew I wanted two things:
- To avoid my computer – The urge to check email, sleep-destroying blue light, the siren song of Reddit: all reasons to avoid computers when possible.
- To type instead of write – I can tap out my thoughts on a keyboard much faster than I can scribble them in a notebook.
Enter the AlphaSmart3000—a pleasingly luddite word processor from the early aughts.
Everyone from writers at the New Yorker to the hardware tinkerers at Hackaday gushed praise for the AlphaSmart.
So, when I found one for ~$30 on eBay, I snatched it up.
I thought I was going to love it. But I’ve never used it like I’d dreamed.
🌈✨The Dream✨🌈

Everything I like about this device harkens back to the bygone era when manufacturers designed new tech to last, not become e-waste.
Replaceable batteries with a long battery life
The AlphaSmart3000 boasts 700 hours of battery life on three AAs.
Replacable batteries in 2023: 🤯
Instead of AAs, my AlphaSmart3000 came with a rechargeable NiMH battery pack. But I’ve never had to recharge it. The little battery bar insists it’s fully charged, even after nearly a year of typing on it (albeit intermittently).
Future-proof upload interface
The Alphasmart3000 can double as a keyboard—you can plug it in (via USB-A) and type on it.
This is also how it transfers files—it types them out on your computer.
It’s slow, but I’m impressed with the elegance of the solution. The AlphaSmart will continue to work as long as there are USB keyboards.
🤬The reality
It’s a feature; not a bug
Almost everything I could complain about is arguably a feature.
No virtual writing assistant prodding you about adverb use. No way to sync to the cloud. No ChatGPT.
Even the four-line screen is a feature—it keeps you focused on the few sentences you’re currently wrestling with.
But I have some legitimate gripes.
The keyboard is terrible
Despite appearances, the keyboard is a trying experience. The feeling of little rubber domes popping down, stuck keys: it’s brutal.
LazyDog—a tilde.club member and AlphaSmart enthusiast—created a mechanical keyboard mod kit for the AlphaSmart3000. But I’m hesitant to put in that kind of time.
I miss Vim 😩

The shortcuts and macros for the AlphaSmart would be familiar to anyone who remembers Microsoft Word. But, as a Vim user, my brain is totally broken.
I’ll be the first one to admit: this one is petty.
😭Why I never use it
Whenever I fantasize about how to improve this device, I realize I’m building an eink laptop.
When I’m writing: I want to use Vim. I want to render Markdown and see how it looks in a browser. I want to look up bookmarked references.
I thought I wanted distraction-free writing, but what I actually want is for computers to be better.
In 2012, I was among the first in line to buy a Raspberry Pi. In 2016, I shelled out for the PocketC.H.I.P. And now I’m gearing up for my MNT Pocket Reform. It’d be easy to say: I’m a sucker for open hardware (and that’s true). But I’d also say: I hate the existing hardware hegemony.
I’m ready for what’s next: where is my eink laptop already?
To see posts by date, check out the archives