SiBurning
1000+ Head-Fier
- Joined
- May 18, 2005
- Posts
- 1,389
- Likes
- 39
Quote:
My previous job required a lot of VB. It drove me batty. It was okay for some things. Did a little craplet to cut up an image file: you open a multi-image TIF, move the images down into a separate pane, sort them, save that pane as a new TIF, and start a new pane to save some more images. All the real work was done by a commercial library. For other things it just doesn't cut it. I hear VB.net is a different beast altogether, and that you can use a proper debugger with it instead of just hanging the runtime environment just when you need the debugger. :: Let someone else try it.
There's a lot more I want to say. It took me three hours and 20 rewrites last night to realize it's best left unsaid. Not one to be particularly wise, I'll make three points. (1) In general, most people don't want to put in the time to learn anything thoroughly, and that's a big problem in engineering and science, not to mention civics and a lot of other things. (2) This is a problem that ultimately needs to be solved by the profession. There was a movement a dozen or so years ago to extend the Professional Engineer's license to software. I think that's appropriate for certain types of software. (3) I'm into DIY electronics, and think everyone should do some programming. I only get a little hot under the collar when it comes to professionals that think the half assed job they do is perfectly normal--doesn't all software crash all the time? Off the soapbox.
Originally Posted by jefemeister Chicken and Egg |
My previous job required a lot of VB. It drove me batty. It was okay for some things. Did a little craplet to cut up an image file: you open a multi-image TIF, move the images down into a separate pane, sort them, save that pane as a new TIF, and start a new pane to save some more images. All the real work was done by a commercial library. For other things it just doesn't cut it. I hear VB.net is a different beast altogether, and that you can use a proper debugger with it instead of just hanging the runtime environment just when you need the debugger. :: Let someone else try it.
There's a lot more I want to say. It took me three hours and 20 rewrites last night to realize it's best left unsaid. Not one to be particularly wise, I'll make three points. (1) In general, most people don't want to put in the time to learn anything thoroughly, and that's a big problem in engineering and science, not to mention civics and a lot of other things. (2) This is a problem that ultimately needs to be solved by the profession. There was a movement a dozen or so years ago to extend the Professional Engineer's license to software. I think that's appropriate for certain types of software. (3) I'm into DIY electronics, and think everyone should do some programming. I only get a little hot under the collar when it comes to professionals that think the half assed job they do is perfectly normal--doesn't all software crash all the time? Off the soapbox.