-
By background, Mike and I are both technical folks. We went to the same school, graduated from the same program. While we both speak conversational English (as opposed to off-puting tech), neither of us has great expertise in marketing. Opinions? Yes. Expertise? Not so much. We have known for years that we would eventually need help in sharing Rustici Software’s products and abilities with the world. We just knew that finding the right person would be a magnitude more difficult than finding the right developer.
So, what did we do? We punted. We just kept finding great developers, handing over our development responsibilities to them, and taking on more of the marketing work ourselves.
-
STAR Standards Chief Architect David Carver recently wrote a post about the W3C's use of a public issue tracker. A few people have "retweeted" the post and sent it my way via email. In the post, David gives kudos to the W3C for providing a publicly accessible issue tracker. I think the reason the post has some resonance is that at least a few readers recognize that the post is not so much about the use of about a particular feedback technology as it is about behavioral change within standards organizations and new ways of working. Actually, "new ways of working" isn't quite the right description. Between the lines, I think the post really is about bringing well-established and contemporary software development best practices to the work of standards organizations. If you read through David's other posts regarding the application of agile methodologies to standards development, they very much fit into this same theme.