---
title: "MSDN mag, this is why I lament"
url: "https://osherove.com/blog/2004/5/9/msdn-mag-this-is-why-i-lament.md"
canonical: "https://osherove.com/blog/2004/5/9/msdn-mag-this-is-why-i-lament.html"
published: "2004-05-09T17:52:00"
updated: "2004-05-09T17:52:00"
tags: [".Net Original"]
author: "Roy Osherove"
description: "Some people think I was wrong in saying that MSDN has gone too far hyping up future content. There's a time a place to say \"Get ready for this because it replaces something you've had to reinvent by yourself up until…"
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/"
---

# MSDN mag, this is why I lament

By Roy Osherove May 9, 2004 In [.Net Original](https://osherove.com/blog/category/net-original)

**Historical article** · Originally published May 9, 2004; technical details may be outdated.

[Some people](http://ea.3leaf.com/2004/05/msdn_mag_why_la.html) think I was wrong in saying that [MSDN has gone too far](http://weblogs.asp.net/rosherove/archive/2004/05/08/128174.aspx) hyping up future content.

There's a time a place to say "Get ready for this because it replaces something you've had to reinvent by yourself up until today". The time may be now, but the place should be limited to a \*logical\* section of the content. There are still lots of problems to solve with today's tools. Frankly, when I'm fighting some hard debugging problem the last thing I need is someone telling me "_You know, in Whidbey this is easier!"_ instead of showing me how to fix it today.

Yes, I'd like to know about the future. No, I don't want to know \*only\* about the future. I have problems \*today\*, I am missing knowledge \*today\*. It looks as if MSDN mag is turning into a huge hype machine on the backs of the \*important\* information.

## More in .Net Original

[All posts in .Net Original](https://osherove.com/blog/category/net-original)

- May 17, 2004

    ### [Announcing: Israel Agile Development mailing list](https://osherove.com/blog/2004/5/17/announcing-israel-agile-development-mailing-list.html)

- May 17, 2004

    ### [Test Driven Development Workshop this Wednesday](https://osherove.com/blog/2004/5/17/test-driven-development-workshop-this-wednesday.html)

- May 7, 2004

    ### [Notice: TDD workshop at Magen rescheduled to next week](https://osherove.com/blog/2004/5/7/notice-tdd-workshop-at-magen-rescheduled-to-next-week.html)

- May 7, 2004

    ### [Test Driven Development and Microsoft](https://osherove.com/blog/2004/5/7/test-driven-development-and-microsoft.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/