I do a tiny bit of consulting to help a long-standing client with prototyping and data analysis. It lets them take advantage of the experience I’d built up with their tools and platform, and I get to keep my technical skills and professional network going.

Before we went on our trip, I was averaging about two hours a week, after A-‘s in bed. A- tends to nurse frequently at night, probably to make up for distractions during the day, and we’re okay with this. Sometimes I might be able to do an hour or two of uninterrupted work, and sometimes I clock in and out as I get interrupted by nursing. Fortunately, I built a pretty handy time tracking interface, so it takes only a few taps on my phone.

Because of my limited availability, I try to pick tasks that don’t require a lot of coordination with other people, that can bear with interruptions, and that aren’t risky when done with a fuzzy brain. So, no meetings, no big chunks of new things to learn, and no messing with write access to production data if I can help it. Despite this limited availability, I was able to prototype a few add-ons they wanted, yay!

IA- has been a bit more clingy lately (might be because of teething) so I’m not sure how much time I’ll have in the next little while. I’d like to have the brainspace to learn and build new things so that I can help out my main client, since he has moved up in terms of his role, but that can probably wait. In the meantime, we get decent ROI if I focus on quick answers and prototypes.

t’s important to me to manage expectations well and to turn over as much as I can. This means not committing to more than I can work on, and keeping people up to date on timelines and risks; making sure the team has access to my code and can take things over if they need to; and building in small steps so that I can deliver something of value as soon as possible. It’s fun to break an idea down into the minimum viable product, the intermediate steps to get there, and the incremental enhancements that would make it even better.

I’ve thought about expanding my available work time, but I chose not to. This is the last month and a half of W-‘s parental leave, but I’d rather spend the time enjoying parenting A- with him than squeezing in more computer things. He’s awesome with A- – better than I am. I’ve sometimes asked him to take care of her while I handled high-priority things that needed focused time (such as doing my business tax paperwork!), but I don’t want to commit more of that time than I need to.

At the moment, I’m not particularly keen on getting a babysitter after W- returns to work. I know the math could work out and that the socialization might even be an awesome thing for A-, but I’m curious about the things I might learn from going through this experience myself. I like the fun of problem-solving and the validation of helping a great team, but I can get that later, too. I also don’t quite trust my ability to pick a good person and build the kind of long-term relationship that would be good for A-, so there’s that too. In the meantime, I can learn from A- as she learns, and I can try to shape her world. We’ve got a rare opportunity to do this in a flexible way, and I want to take advantage of that.

So, how do I want consulting to fit into my life? I think the current arrangement is pretty good. I prioritize my self-care, A-, W-, and the general upkeep of the household; then my journal and Emacs News, since both are time-based; then more discretionary things, like consulting or personal coding. The clients seem happy. They’re not slowed down by me or kept hanging, and they get good value considering the time and money involved. I might be able to do more work if A-‘s sleep solidifies, but I’m in no rush. It might be that I’ll have limited work availability until she’s old enough for playdates or school, and that’s fine too.

I’ll think about this again after we settle into new routines, when W-‘s back at work. It’ll be interesting to see how things change.