Biingling? Sounds like a panda's name.

>I've done lots of Bingling the past couple of years as I've been learning about web development. Yes, I've made plenty of mistakes. It's part of the process. But I'm much more self-sufficient than I was two years go.
>
>Knowing the hierarchy in C# is not that big a deal. Once you've got the DLL it's in, it's not difficult to find. And you can specify the namespace in the program so you don't need to type it out every time. The namespace/DLL stuff was a hangup for me at first, but Visual Studio has gotten much better at telling you where something is. It doesn't always do that, but it's improving.
>
>
>>True, that about force. I remember there were some languages where I had to force myself - let's see, the PDP-11 command language (sort of interesting, but hated it), Hayes codes for modems, ESC/P, the HP printer language, GwBasic (which was just plain fugly compared to GfA or even Spectrum or Spectrum Beta dialects), OPL for Psion and a few oddballs more. Even Cobol didn't require force - it was curiosity that led me into learning. I guess trying to learn Cobol now would require forcing myself, just like C# would. They're both too verbose - in Cobol you had to do all the work for the compiler (define all the variables and buffers, what with data types and lengths); in dot net you need to know the hierarchy of anything you want to use, and there's too much of it. Intellisense will get you the next name in the sausage, but you still need to know where the sausage needs to start. And you may be using a piece of abandonware at that.