A couple of months back, I told you the story about my early involvement in the birth of coComment. A few weeks, ago, Nicolas asked me if I would like to be part of the team, and I happily accepted.
My role, broadly, falls in the category of evangelism and communication (external and internal), and it’s in part what I was doing after the launch, before school and computer problems took over: read what is said about coComment in the blogosphere, comment and react when it’s needed or helpful, be active in the forums, bring back to the team feedback and ideas (found out there or somewhere deep in my mind) — in short, be a fussy but enthusiastic and vocal user.
Being part of the team now, I’ll be posting in the coComment Team Blog, which I have to say really needs to be more active. I will also be facilitating internal communication between the various team members.
My hope in taking up this job is to help make coComment into a tool which addresses users’ needs. I think it’s a great tool, and has a lot of potential. As I tell my clients, blogging and being an active player in the blogosphere takes up time. The dev team can’t spend all their time developing stuff and do the communication as well. That’s where I come in.
Working for coComment has a feel of adventure for me. First of all, I’m actually going to be paid to do what I like doing (be a pain in the neck and throw ideas all over the place). Second, this is the first time for me that work and blogosphere collide. My previous jobs have had nothing to do with the blogosphere, and I’ve never blogged much about my work.
I’m going to experience what it is to be caught between the desire to be transparent, and the fact that in business you cannot always say everything. I’ll probably have more to say about this in the coming weeks!
