Some unsolicited feedback for the Fields project from my time with the REST API project

Capturing advice I left for the sands of time.

  1. Set a clear mission statement for the project. This will give clarity to the problem you’re solving, what to say yes to, and what to say no to. You ideally want to avoid crises of faith late in the project.
  2. For your contributors, clarify involvement expectations. When most contributors are doing so in their “free” time (e.g. not getting paid directly for it), it’s really difficult to budget for unlimited development scope. A little bit of proper project management goes a long way. I feel like WP-API is a much more sustainable project with four contributing developers than two. I would encourage you to have at least three.
  3. Model your data before writing code. What is a field? What attributes should it have and why? What is a control? What attributes should it have and why? When you dive into development before appropriately modeling your application, you run into these implementation details one by one, and burn a lot of time (waiting to) discuss them.
  4. Focus on clearing blockers above all else. Because you’re working on an open source project with contributors across many timezones, average time to feedback will optimistically be 6 hours. More likely, it will be 24-48 hours. This slow feedback cycle can kill progress on pull requests. As a project maintainer, prioritize giving feedback, clearing blockers, and making decisions.

The next 11 days

A bit of travel coming up over the next 11 days:

  • Today I’m flying to NYC to meet a few new members of the Fusion team in person. Tomorrow we have a hack day on the theme of personalization.
  • Friday evening I’m taking the train to Philly for Saturday’s BCNI. I fly back to Portland Saturday evening.
  • Home on Sunday.
  • On Monday, I’m headed to Napa via SF for the VIP workshop. I’m bringing my running shoes.
  • Thursday, I fly to Las Vegas for Loopconf, where I’ll be until Saturday morning.

If our paths intersect, say hello!

On the gear front, I recently picked up a Patagonia Refugio 28L backpack. It passed the test with flying colors on an overnight to SF. One pocket for my laptop, another for clothing, and a third for cables, etc. I can’t underscore how exceedingly awesome it is. Clothing volume-wise, I think it’s going to max out at three night trips unless I pack my reusable undies.