For the benefit of my coworkers and future coworkers, this is how I work. This is descriptive of me, not prescriptive to you; treat it as a set of FYIs, not requirements. Use or ignore at your discretion, and share your own guide with me!
Meetings
Because of my schedule I'm not a fan of morning meetings, especially recurring ones. I can do one-offs when needed.
I like meetings with well-defined outputs ("At the end of this meeting, we will have decided…"). They help me prepare and keep the meeting on-task.
If the meeting output is arrived at quickly, I would rather end the meeting early than use all time available.
I prefer asynchrony over ad hoc, ad hoc over scheduled:
┌───────┐
│ Start │
└───────┘
│
Need for communication
│
▼
┌────────────┐
Presentation │ Message │
┌───or demo───────────│(e.g. Slack)│─────────────────────┐
│ └────────────┘ Lots of back-and-forth
│ │ │
│ │ │
│ │ │
│ Explanation │ │
│ difficult in text──┘ │
│ │ │
│ │ │
│ │ │
│ ▼ ▼
│ ┌─────────────┐ ┌─────────┐
│ │ Recording │ Lots of back-and-forth │ Ad hoc │
└─>│ (e.g. Loom) │─────────────────────────────────>│ meeting │
└─────────────┘ └─────────┘
│
│
Not online at
the same time
│
│
▼
┌───────────┐
│ Scheduled │
│ meeting │
└───────────┘
│
│
All above happen
consistently on a
recurring basis
│
│
▼
┌───────────┐
│ Scheduled │
│ recurring │
│ meeting │
└───────────┘
Schedule
My body demands a lot of sleep. By default I do not use alarms and let my body wake itself when it's ready. After my morning routine, the bell curve for my coming online has a median around 9:30AM pacific, with a ~45 min standard deviation.
Inspiration strikes me randomly—sometimes during a workday, but also sometimes on a Sunday, or at 4 AM, or for 16 hours straight. I'm very productive during these random bursts, but having a habit of overworking leads me to burnout.
To counterbalance, I shorten my standard workday a bit and the math roughly works out. If you see emails or commits from me with unhealthy-feeling timestamps, keep in mind my default workday is at ~70% capacity.
My Promises to You
- I will respond to you.
- I will respond to you within one business day.
- I promise to put my ego in the back seat to learning.
- I promise to be receptive and thankful when you give me a piece of feedback.
- I promise to share the whys behind any feedback I give (whether personal, professional, or code).
- I promise to be supportive and (if you want) helpful when you tell me about something that makes you feel uncomfortable.
My Weaknesses
- I am weak to heat. My mood and productivity negatively coorelate with the temperature outside.
- Social interaction costs me brainpower so I am better at problem-solving when I have time alone to digest.
- I don't handle interruptions well, regardless of duration.12 Notifications for my Slack are often off while I am in flow. (If it's urgent, use the on-call flow.)
- I go rogue. Sometimes I'm so passionate about fixing or building something that I'll do it without tracking it because the overhead—or its emotional burden— is bigger than the job itself. I'll still run it by people before shipping.
Communication
1. I would rather align on vision than work in lock-step.
Coordination is slow. As long as we share a common vision, I trust you to make two-way door decisions in motion without blocking on consensus. I ask that you trust me to do the same. We can continue to share progress in nonblocking ways.3
2. I love when information has a home.
I'm forgetful. I can more easily (re)gain context for an issue when discussion is concentrated in one place, like comments on the relevant ticket or pull request. I will leave breadcrumbs in these places for posterity if I feel things are missing.
3. I focus on customer problems.
Even if a solution "feels right" be prepared for me to ask what customer problem it solves.
4. Don't say hello.
This page is in the form of Abby Falik's user guide and inspired by Dina Levitan's user guide.
