Skip to main content

Communication manifesto

Draft! Not yet implemented.

Please leave comments with your feedback.

Historically my responses to inquiries has ebbed and flowed. Sometimes my inbox would pileup for a month before many people would get responses. This manifesto is my contract to the world to improve my communication response time. Before contacting me I suggest you read this manifesto and a couple of essays about email.

Here is my commitment to response time going forward:

Short form:
- @Twitter*, SMS, @GitHub, IM, etc.
- Response within 24 hours.
- Must be less then 250 characters.
- Preferred method of contact.

Long form:
- Email, @Facebook, snail mail etc.
- Response within 48 hours.
- Generally longer then 250 characters.
- Keep it short and to the point.

- Phone calls, voicemail, @skype voice, etc
- Callback within 24 hours.
- You must leave a voicemail.
- I don't like phones so you should consider the above options first.

What if I miss my deadline? If it is important ping me immediately after the time lapses else restart the clock and wait one more cycle before pinging me. Maintain the same method of contact so important information stays organized and does not get misplaced. Feel free to also remind me of this communication commitment to you.

And finally ... my contact information page. :)

*Twitter is my preferred form of communication because of it's brevity and easy access.


  1. I think the long-form response time should actually be longer. It would encourage people to use the short-form.

    And what category does this comment or google group messages fall under?

  2. @Greg: Good point. I should increase long form some.

    Blog comments are short form and Google Group messages are almost always emails for me so long form.


Post a Comment

Popular posts from this blog

A month of Flutter: a look back

Originally published on . This is it. 31 blog posts in 31 days. Writing  a month of flutter  has been a ton of work but also lots of fun and a good learning experience. I really appreciate how supportive and and positive everyone as been. Publishing experience For the series I've been posting on ,  DEV ,  my personal blog , and  Medium . After publishing to these sites, I would put the Bendyworks link on  Twitter ,  Reddit , and the  Flutter Study Group Slack . Posting to DEV was easy as they use Markdown just like the Bendworks blog. DEV also has built in support for a  series of posts  so it's easy to read the entire series. I did have to manually upload any embedded images. DEV also has a number of  liquid tags  for embedding things like GitHub issues that I didn't make as much use of as I should have. Blogger is rich text so it was easy to copy/paste the rendered posts. This would hotlink all the images though so I had to rem

Sync is currently experiencing problems

Update : I now recommend you install Google Chrome  and  disable  the built in Browser as it supports encrypting all synced data. After picking up a gorgeous  Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly." In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with".  Hit "disconnect your Google Account" to temporarily disable syncing from your browser. Visit the Google Dashboard and "Stop sync and delete data from Google". I waite

A month of Flutter: the real hero animation

Originally published on . For the last post before the month's wrap up tomorrow, I wanted to do something more fun: use a  hero animation between the home page list and the individual post page. When I first implemented the  Hero  animation it never worked going back from a  PostPage  to the  HomePage . The reason was that  HomePage  would get rerendered and that would  generate new fake posts . So I moved the fake data generation up a level to  MyApp  and pass it into  HomePage . This is more realistic as going to the  HomePage  shouldn't request the  Post s every time. HomePage ( title: 'Birb' , posts: _loadPosts ( context ), ) The  PostPage  implementation is a simple  StatelessWidget  that takes  Post  and renders a  PostItem . This will become more complex as things like comments and likes are implemented but works for now. class PostPage extends StatelessWidget { const PostPage ({ Key key , @required this