Visual Studio Magazine Wants Your Dev Disasters

What's the worst programming mistake you've ever made?

We're in full-fledged football season now, and it's common to hear the refrain from announcers after a quarterback throws an interception: "I know he wishes he could have that one back." In other words: Yo, epic fail on that pass!

For an upcoming issue of Visual Studio Magazine, we're devoting our cover story to the software development version of that sentiment: What programming mistake do you wish you could have back? What was your biggest flub? What pass did you throw into triple coverage, that was returned for a pick-six?

OK, enough lame sports analogies. What I'm looking for is input from you on your worst moment as a software developer. Keep them as short as possible -- under 400 words, and fewer than that is better if you can manage it. Tell me what happened, and what you learned from it (but it's fine if there are no lessons learned -- it could just be funny, or vomit-inducing with no big takeaways.) If it *has* to be more than 400 words, send it in anyway -- if I can't fit it in print, I'll add it to our online version of the story.

It could be a disaster you caused, one you were called in to fix, or one which you only witnessed.

I'll need your tales of woe in to me no later than Oct. 8, three weeks from today. To ensure I see it and don't delete it accidentally, put "My Dev Disaster" in the Subject line of your email.

If you don't mind your picture accompanying your story, send along a good headshot as well. Send all materials in to me at [email protected] If you have questions about the article, don't hesitate to ask; but use the same Subject line, so I know what to do with it.

One thing to note is that you're free to change names/companies in your descriptions, if necessary. If you do so, please place the fictitious name or company in quote marks the first time you use it. That will ensure that readers understand these are pseudonyms, to protect the innocent (or, more likely, the guilty.)

And for Pete's Sake, watch those sneaky defensive ends dropping into zone coverage.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus


  • Death of the Dev Machine?

    Here's a takeaway from this week's Ignite 2020 event: An advanced Azure cloud portends the death of the traditional, high-powered dev machine packed with computing, memory and storage components.

  • COVID-19 Is Ignite 2020's Elephant in the Room: 'Frankly, It Sucks'

    As in all things of our new reality, there was no escaping the drastic changes in routine caused by the COVID-19 pandemic during Microsoft's big Ignite 2020 developer/IT pro conference, this week shifted to an online-only event after drawing tens of thousands of in-person attendees in years past.

  • Visual Studio 2019 v16.8 Preview Update Adds Codespaces

    To coincide with the Microsoft Ignite 2020 IT pro/developer event, the Visual Studio dev team shipped a new update, Visual Studio 2019 v16.8 Preview 3.1, with the main attraction being support for cloud-hosted Codespaces, now in a limited beta.

  • Speed Lines Graphic

    New for Blazor: Azure Static Web Apps Support

    With Blazor taking the .NET web development world by storm, one of the first announcements during Microsoft's Ignite 2020 developer/IT event was its new support in Azure Static Web Apps.

  • Entity Framework Core 5 RC1 Is Feature Complete, Ready for Production

    The first release candidate for Entity Framework 5 -- Microsoft's object-database mapper for .NET -- has shipped with a go live license, ready for production.

Upcoming Events