Perhaps you don't need reliable TCP/IP communications in your SW development, or else you would KNOW that Win2K's TCP/IP stack is light years ahead of NT's. There are many other features that you would NEED as a SW developer (depending on the platform your SW runs on at the customer sites). Perhaps there are other reasons you don't want to switch to Win2K?
I've done them all as well. Win2K is much more stable than NT.
As I said before, I don't wish to spend the BIG BUCKS just because the "new one" has been released. NT works just fine for the work I do; and, my NT is operated "stand alone" with no network. I prefer to work that way ... I don't need no stinking network. I develop embedded equipment. If those require networking, it is done compactly without any code bloat.