Today's TLA is MWP
Microsoft Wizard Programming
Why does Microsoft have a wizard for setting up a simple command line program? This is by far one of the worst ideas for development. I mean it is a very strict and communist approach to programming. It tries to solve the Makefile problem, but I would rather deal with Make than trying to setup the Microsoft Visual C++ projects again. I mean both tools try to solve the same problem. If I have to say one thing about computers it is that computers are stupid. I don't care what anyone will say, but if you don't put a library correctly your program will not work. This is why we have tools like Make and VC++. They ensure the proper definition of paths for a program. Rules of thumb with regards to libraries.
1) Don't mispell libraries (Be aware of upper and lower case i.e. Alib,ALib)
2) Double check the full path before you copy and paste anywhere. It takes 2 seconds to check the directory. But it could take an hour trying to find where you misspelled some file path. It's the measure 4x but cut once approach.
3) Check your syntax and Google for your errors.
These are just some tips for programming. It annoys me that Windows uses a wizard approach, because you can't change your mind. So what if I originally created a .exe project and I wanted to change it into DLL, ActiveX, or some MFC application. Well you might as well create a new project, because it sucks trying to manually do it. This really annoys the heck out of me, why is there so many boilerplate strings everywhere just for a simple Hello World app for Win32 applications. I really hate the fact that I can't change my mind in the middle of programming. And with programming change is central to everything that we do.
Enjoy,
Jonathan
Microsoft Wizard Programming
Why does Microsoft have a wizard for setting up a simple command line program? This is by far one of the worst ideas for development. I mean it is a very strict and communist approach to programming. It tries to solve the Makefile problem, but I would rather deal with Make than trying to setup the Microsoft Visual C++ projects again. I mean both tools try to solve the same problem. If I have to say one thing about computers it is that computers are stupid. I don't care what anyone will say, but if you don't put a library correctly your program will not work. This is why we have tools like Make and VC++. They ensure the proper definition of paths for a program. Rules of thumb with regards to libraries.
1) Don't mispell libraries (Be aware of upper and lower case i.e. Alib,ALib)
2) Double check the full path before you copy and paste anywhere. It takes 2 seconds to check the directory. But it could take an hour trying to find where you misspelled some file path. It's the measure 4x but cut once approach.
3) Check your syntax and Google for your errors.
These are just some tips for programming. It annoys me that Windows uses a wizard approach, because you can't change your mind. So what if I originally created a .exe project and I wanted to change it into DLL, ActiveX, or some MFC application. Well you might as well create a new project, because it sucks trying to manually do it. This really annoys the heck out of me, why is there so many boilerplate strings everywhere just for a simple Hello World app for Win32 applications. I really hate the fact that I can't change my mind in the middle of programming. And with programming change is central to everything that we do.
Enjoy,
Jonathan
0 Comments:
Post a Comment
<< Home