My experience with Microsoft products is that they are typically as "helpful" as a three-year-old working on the car with you: occasionally they really do help, but most of the time their well meaning efforts are just in the way. For instance, they seem terrified that if they do not fill in a default name for every form, field, file, project, button, slider, and so forth, that the user will be come completely disoriented, freeze up, and be unable to continue. But because there is always a default, you can easily miss the fact that you have not chosen the names, and windup working with "Button1," "Slider1," "Form1," and "WindowsProject1." And, I would suggest, these are examples of names that you would never, ever want to give to your buttons, sliders, forms, and projects! If there is a manual of horrible naming out there, certainly naming a button "Button1" is in it. (You want to name it after what pressing it causes, e.g., "CalculateTaxButton".) In some cases, such as a button or slider, these can be very easy to change, but with a Visual Studio project things are not nearly so simple.
Take place in human diners, and show one omelette after another being cooked and devoured.
Declares LewRockwell.com : "All of this means that while the government has been artificially propping up the economy and 'stimu...
Is shaping up nicely .
The language won't die, but that doesn't mean the programmers won't ! Funny quote: '"Just because a language is 50...