aaron: philip is only twittering his hackystat hacking.
austen: im not sure what we are supposed to twitter
aaron: haha. everything.
aaron: i think thats more interesting. thoughts.
aaron: not tasks.
aaron: like what was the PMD error
aaron: i think the task is interesting. too
aaron: but.. to me what is more useful is knowledge
austen: its hard to type out stuff so short tho and without noticing the context switch
aaron: ah.. there is the problem.
aaron: sharing knowledge is hard.
aaron: sharing tasks is easy
aaron: sharing knowledge is more useful.
aaron: this is going on my blog.
i just just read an article in IEEE software tittled, celebrating peopleware's 20th anniversary. one of the comments in that article is kind of related to our chat above.
[peopleware] tells stories-vignettes such as the tale of the furniture police. we need to do more of this in universities, and pass on the wisdom of the panelist and peopleware by telling more stories in our cs classes.
i like the idea of knowing what is going on (project proprioception ). that sort of thing can definitely improve how a teams functions. but, the vignettes of knowledge makes me a better hacker. in addition to project proprioception, i want to gather as many 10 second vignettes from of twitter, blogs, shared items, etc as i can. i want to know what was that PMD error and did philip learn anything useful from solving that problem. i think that could be the overall goal of our collaboration investigation.
sharing is awesome. blogging is sharing to some degree. i like the 10 second knowledge thing as much things as you can fit in your day. --aaron via twitter
so, i want to share how i share stuff. i think it would be cool if we all tried to do this.
anyway, the point is that; (1) i would love to read more of the hackystat developers blogs. but, no one is blogging that much. (2) i would love to read what you find to be interesting. maybe i can learn something too; in the 10 second style that i like. (3) i would love to see cool webpages that you find (via google share). (4) the moral of the story, is that we can go way beyond twitter in our quest of collaboration and sharing.
here is a cool idea; hackystat goals! for example, a state goal that coverage needs to be higher than 95% for project foo (its currently 55%). all the effort that i will do until the goal is met is to accomplish that goal (maybe mylyn can help with that task identification). or another example, could be get rid of all codeissues. these goals adds context.
goals gives context to what you are doing. i see something in between jira issues, mylyn, twitter to accomplish that. austen has been thinking about this as well. comment sdt or even context sdt would be awesome. hackystat goals is a way to do provide context. and i want context to be able to learn, in addition to knowing what is going on.
i'm liking this whole movement towards hackystat as a hacking collaboration tool. i have no idea what that means; but it seems useful and cool. the best thing about working on hackystat itself is the developer interaction and learning together. hackystat should make that easier (or funner) for us. put together twitter and active time. woah... thats cool.
hackystat generated twitter messages
i'm not sure this encompasses philip's project proprioception idea. its probably an extension. anyway. it would be cool if hackystat analyzed the sensor data (via stream analysis, data mining, rules, etc) and sent twitter messages. for example:
at some point, james won't even know what he is doing. and hackystat can say, "woah, james. congratulations, you actually did TDD for a week."
wow, so this also ties into developer expertise.
the basic idea is that anyone can do metric reporting. see atlassian's clover page . metrics allow us to measure and manage. thats good and can even be great! but, what's more interesting to me as a hacker is getting better. and how do i get better? i get better by acquiring vignettes of knowledge. a system that makes that easier to do would be awesome.
i think it would be awesome for people to provide insights into their thoughts as they hack. here is how we can start to learn how to do that: