Developer's Toolkit

Blog archive

It’s a Wonder We Get Any Work Done

It was with some trepidation that I started a new ASP.NET project in Visual Studio 2005. I had already spent three hours earlier that morning cleansing errant viruses and tracking cookies off of my system, and now I was going to start IIS and open a port through my firewall and router to the outside world.

But I had been meaning to investigate development using Microsoft Virtual Earth since I sat in on a lunchtime session on the topic at TechEd in June. And I convinced colleaguePatrick Meader that an article on the technology would be a great contribution to Visual Studio magazine. So I pressed on, making remarkable progress and writing a couple of simple map applications in less than a day.

I suspect I'm like most people when it comes to system protection. I have a subscription to a comprehensive virus checker, and I mostly curse it for getting in the way. For example, my McAfee seems to either block or take an inordinate amount of time scanning outgoing mail, so I have to turn off that particular feature to send any mail. But mostly I deal with the hassles, including much too frequent upgrade and special deal pop-ups, because I have a vague sense that it is good for me.

I use Windows XP Firewall, and also depend on my router to deflect any attack based on my IP address. I don't visit questionable sites and don't (voluntarily) download software that I don't know. In other words, I'm not particularly attentive, but I don't do stupid things.

Yet still I had to spend several hours cleaning my system. Of course, by working on a Virtual Earth application using the Virtual Earth Map Control and ASP.NET, I had to turn on IIS and open a port to the Internet. I regret to say that by the end of the day I once again started getting suspicious messages from McAfee, indicating still more viruses and tracking cookies. These messages will almost certainly lead to another round of cleaning over the weekend.

Enterprise developers often have to operate under a lot of restrictions. In some cases, they cannot even be local system administrators for their own development systems. In all cases, they have to perform regular virus scans and comply with enterprise and IT restrictions on Internet access.

These restrictions make it difficult to write services applications such as the type that Virtual Earth enables with ease. You have to be as diligent at keeping your system clean and satisfying corporate mandates as you do at writing quality code.

Some developers are able to approach system security with the same mindset that they do writing code, and it becomes a part of the normal work routine. Even then, it is a drain on software development productivity.

I don't code enough to have that approach. For me, and I'm sure for others, it is just a time-consuming chore undertaking only when necessary. But the cost of both illegitimate and technically-legal-but-shady intrusions (like Microsoft's Genuine Windows Advantage) take an enormous toll on our ability to do our jobs.

Posted by Peter Varhol on 08/26/2006


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube