---
title: "MSDN magazine has gone too far (into the future)"
url: "https://osherove.com/blog/2004/5/7/msdn-magazine-has-gone-too-far-into-the-future.md"
canonical: "https://osherove.com/blog/2004/5/7/msdn-magazine-has-gone-too-far-into-the-future.html"
published: "2004-05-07T19:41:00"
updated: "2004-05-07T19:41:00"
tags: [".Net Original"]
author: "Roy Osherove"
description: "This is truly annoying. here's the MSDN magazine's current and future covers: um.. excuse me? Is there any particular reason I should be reading MSDN magazine if I wanted to learn something about a technology I am using…"
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 magazine has gone too far (into the future)

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

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

This is truly annoying. here's the MSDN magazine's current and future covers:

![May 2004](https://osherove.com/img/wb/3c75e1f7_msdn.microsoft.com_msdnmag_images_covers_May04cover.gif) ![June 2004](https://osherove.com/img/wb/602a5eac_msdn.microsoft.com_msdnmag_images_covers_June04cover.gif)

um.. excuse me? Is there any particular reason I should be reading MSDN magazine if I wanted to learn something about a technology I am using **today**? what's all this “future revealed“ thing? we get enough of this on the web. I shouldn't be paying money to read about stuff I can't even use today. or at least not for half of the magazine articles on it!

Please bring MSDN magazine back into the real world. I sure hope the next issue isn't about solving problems in longhorn applications.

## More in .Net Original

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

- 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)

- May 7, 2004

    ### [Code readability and communication](https://osherove.com/blog/2004/5/7/code-readability-and-communication.html)

- May 7, 2004

    ### [My favorite Tech-Ed quote, and what you need to know about FABRIQ](https://osherove.com/blog/2004/5/7/my-favorite-tech-ed-quote-and-what-you-need-to-know-about-fa.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/