--- title: "The Tech-Ed Israel Blog needs some *buzz*" url: "https://osherove.com/blog/2006/3/29/the-tech-ed-israel-blog-needs-some-buzz.md" canonical: "https://osherove.com/blog/2006/3/29/the-tech-ed-israel-blog-needs-some-buzz.html" published: "2006-03-29T14:25:00" updated: "2006-03-29T14:25:00" tags: ["Community"] author: "Roy Osherove" description: "Tech-Ed Israel has a blog . Its run mostly by Lior Tzoref, and tries to put a face on the whole organization of Tech-Ed. Personally, I like the idea. But there are several facets that should be implemented before…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # The Tech-Ed Israel Blog needs some \*buzz\* By Roy Osherove March 29, 2006 In [Community](https://osherove.com/blog/category/community) **Historical article** · Originally published March 29, 2006; technical details may be outdated. [Tech-Ed Israel has a blog](http://www.microsoft.com/israel/teched/blog/default.aspx). Its run mostly by Lior Tzoref, and tries to put a face on the whole organization of Tech-Ed. Personally, I like the idea. But there are several facets that should be implemented before Microsoft Israel can take advantage of the full power of community (and actually make it worth while opening a blog like that) 1. **Add the ability to write comments on posts**. A blog, the way I see it, is a written conversation. It's almost pointless to have only one side being heard while the other just sits there and reads it. Especially when it's from a "marketing" type of source. Marketing is much more trusted in the eyes of the reader if there is at least the \*impression\* or listening back to the reader. But with no comments, we are left with only the simple option of sending an email. I sent an email saying exactly the comments issue. I got back an answer that the blog is just fine the way it is or something similar, but thanks for the concern. Funny thing is that they really do take to heart the email the get, so a comment on the blog post seems like just what they would want! 2. **Update it more during the week**.  If people don't seen anything interesting, they will stop reading it. 3. **Do something that only the blog readers can get to**. Content-specific postings and benefits go long way to making a blog popular. It's also a good way to promote viral marketing.. ## More in Community [All posts in Community](https://osherove.com/blog/category/community) - Apr 6, 2006 ### [Port 25: Microsoft Open Source Software Lab's "Channel 9"?](https://osherove.com/blog/2006/4/6/port-25-microsoft-open-source-software-labs-quotchannel-9quo.html) - Apr 2, 2006 ### [Upgrading weblogs.asp.net from a slow and painful death](https://osherove.com/blog/2006/4/2/upgrading-weblogsaspnet-from-a-slow-and-painful-death.html) - Mar 29, 2006 ### [New Israeli MVPs Announced](https://osherove.com/blog/2006/3/29/new-israeli-mvps-announced.html) - Mar 24, 2006 ### [Why Word Verification Isn't The Answer](https://osherove.com/blog/2006/3/24/why-word-verification-isnt-the-answer.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/