It sucks working outside of regular hours but in development that's usually what happens.
I work as a contractor and you often end up working 10 - 12 hour days or weekends, however I am well compensated so I can't complain (I also don't have a family of my own so at this moment it doesn't really bother me). If I am not compensated however, I simply work a regular 8 hour day.
My advice would be to write the program, keeping track of the hours you spend on it. If they refuse to compensate you for your time or consider a raise look for work elsewhere.
For development I would strongly advice that you consider C#, it's a lot like VB but considerably more powerful (just Google around or ask). It might also be worth your while to take a look at SQL as you will often need to interact with a database.
Oh, and whatever you do, do not build a program that deletes itself, it may seem like a good idea but in the long run it will only hurt your career.
I work as a contractor and you often end up working 10 - 12 hour days or weekends, however I am well compensated so I can't complain (I also don't have a family of my own so at this moment it doesn't really bother me). If I am not compensated however, I simply work a regular 8 hour day.
My advice would be to write the program, keeping track of the hours you spend on it. If they refuse to compensate you for your time or consider a raise look for work elsewhere.
For development I would strongly advice that you consider C#, it's a lot like VB but considerably more powerful (just Google around or ask). It might also be worth your while to take a look at SQL as you will often need to interact with a database.
Oh, and whatever you do, do not build a program that deletes itself, it may seem like a good idea but in the long run it will only hurt your career.









