VB's runtime system and IDE can mask that. Sit two people down. The first is a reaonably intelligent person who has been trained in VB, the other is a gifted programmer who has to work with vim, the language of your choice, and a GUI toolkit. Give them a common business data entry problem to solve, and they both end up with something that works in a reasonable time. Task them with creating a program which finds economically optimal air travel itineraries using various data sources and meeting certain user defined criteria, and the first guy is out of his depth.
I happen to be in the second category. However, I am currently writing some code for a consulting gig I have in C#. One problem I'm having is that I have to "change the way I think" in order to work the "Microsoft Way". For example, when writing code in Visual Studio, it really wants you to declare your variable, implement the method that uses the variable, and then you can write the code that calls the method.
However, I usually work exactly the other way around. I write the highlevel code first, and the rest is just trivial details. MS makes it easy to do the trivial stuff.
There are other examples like this one. I'm not going to get into the productivity hit I take when I'm not using vim...
My point is that it is quite possible for a "trained VB" person to be more productive when doing
VB-like tasks than someone like me.
Well, for me:
- Seen every episode, I think, but not sure.
- Didn't see the movie when it came out, so I'm going to buy the DVD, so
- It might be good to brush up on the episodes first
Re:Currently Reading - My own review
on
OpenGL Distilled
·
· Score: 1
I'm currently reading this book also. I'm not so crazy about it. I have a good understanding of computer graphics, but no knowledge of OpenGL.
It seems like its trying to be all things to all people, and delivers to noone. Here's an example from page 6, talking about fragments: "OpenGL implementations that support multisampling, however, store fragments in subpixel locations." And then we move on to Rasterization. What is multisampling and subpixel location storage? How do I know if my implementation supports it? Why was it important for the author to state this?
If I'm already supposed to know these details, then why should I get this book? Why not just use a reference?
This is my sentiment exactly. As a consultant myself, you definitely have to "push back" a bit to make it clear you are two companies mutually working together.
I have signed "mutual NDAs" before which state "both parties agree...", and then you both sign it. And there is none of the language you cited.
When I consult, we decide on the deliverables and the rate, and that's it. I often will have more than one gig going at once, so the NDA you are faced with would be a show stopper.
Signing the NDA would probably have no material effect. Its just something the lawyers do to minimize the company's risk. However, it does show a lack of respect for you. And that's probably the real issue. Sounds like they just want a part time employee.
Slashdot Mirror
VB's runtime system and IDE can mask that. Sit two people down. The first is a reaonably intelligent person who has been trained in VB, the other is a gifted programmer who has to work with vim, the language of your choice, and a GUI toolkit. Give them a common business data entry problem to solve, and they both end up with something that works in a reasonable time. Task them with creating a program which finds economically optimal air travel itineraries using various data sources and meeting certain user defined criteria, and the first guy is out of his depth.
I happen to be in the second category. However, I am currently writing some code for a consulting gig I have in C#. One problem I'm having is that I have to "change the way I think" in order to work the "Microsoft Way". For example, when writing code in Visual Studio, it really wants you to declare your variable, implement the method that uses the variable, and then you can write the code that calls the method.
However, I usually work exactly the other way around. I write the highlevel code first, and the rest is just trivial details. MS makes it easy to do the trivial stuff.
There are other examples like this one. I'm not going to get into the productivity hit I take when I'm not using vim...
My point is that it is quite possible for a "trained VB" person to be more productive when doing VB-like tasks than someone like me.
Well, for me: - Seen every episode, I think, but not sure. - Didn't see the movie when it came out, so I'm going to buy the DVD, so - It might be good to brush up on the episodes first
I'm currently reading this book also. I'm not so crazy about it. I have a good understanding of computer graphics, but no knowledge of OpenGL. It seems like its trying to be all things to all people, and delivers to noone. Here's an example from page 6, talking about fragments: "OpenGL implementations that support multisampling, however, store fragments in subpixel locations." And then we move on to Rasterization. What is multisampling and subpixel location storage? How do I know if my implementation supports it? Why was it important for the author to state this? If I'm already supposed to know these details, then why should I get this book? Why not just use a reference?
This is my sentiment exactly. As a consultant myself, you definitely have to "push back" a bit to make it clear you are two companies mutually working together.
I have signed "mutual NDAs" before which state "both parties agree...", and then you both sign it.
And there is none of the language you cited.
When I consult, we decide on the deliverables and the rate, and that's it. I often will have more than one gig going at once, so the NDA you are faced with would be a show stopper.
Signing the NDA would probably have no material effect. Its just something the lawyers do to minimize the company's risk. However, it does show a lack of respect for you. And that's probably the real issue. Sounds like they just want a part time employee.