To give an example, when I started looking at twitter, I played with
it to see if I really could see a use for it... So I started taking
the idea that I wanted to make it a log of ideas for the projects I'm
working on that I could access from anywhere. Ultimately, this
experiment was an utter failure, because when I needed to catch one of
those ideas I couldn't get it into twitter fast enough. Here ended the
first flirt with twitter.
My second attempt came when twitter started offering command-line-like
options to integrate with all kinds of things... This sadly proved to
be my second failed attempt at making twitter useful, because I
discovered I was triple-entering everything. First I'd scribble madly
in meetings or taking mental notes in hallway converations to get
notes down, then twitter pieces that were critical to myself, and then
getting back to a base camp and collating a to-do list, a new project
list, and farming out pieces. What I discovered very quickly was that
I'd revert back to my written notes and memory to get the base camp
activities accomplished because I had to refer to them. Strike two for
twitter...
Now these activities that I went through are just an example of what a
process might be for twitter, different things apply to different
concepts and tools, however there are plenty of techniques for writing
such exercises to be generically helpful to multiple topics.
Like, 3 of those per chapter?
Sam
On Sep 10, 6:02 pm, "peter.fitzger...@gmail.com"
Maybe at the end of each chapter, have a kind of "Exercises" thing, to
try it out? For example:
1. Try sending 10 updates to Twitter using a combination of SMS and
instant messaging over the course of one day.
Like, 3 of those per chapter?
Sam
That any good?
On Sep 10, 7:44 pm, "Dan Davis" <danda...@dandavis.com> wrote: