Stepping into someone elses shoes

Question

0.00/5 (No votes)

See more:

I have a new job, and have been given the assignment of adding an option to our code. The code has been rewritten in VB.NET, and I am told I have all the files necessary to do my job.

My problem is getting the code to compile, we have run into missing libraries, classes that we cannot find and many other issues to boot.

Our strategy is to get a working model to compile then take it from there, and we have copied the working files from the server.

My gut tells me this is simply an issue of letting Studio know where everything is.

What is the best approach for tackling this task? Is there a standard used when developing with Studio?

Thanks much for any help you can give.

Posted 1-May-12 8:25am

jonsey29847

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-05-01T08:39:00

Technically, there is no such problem at all; and there is nothing to discuss. I feel that the problem is the organization of development in the teem you recently joined. Do they have development documentation? Do they use Revision Control System? Do they have distinct procedures for submitting the code? Do they have one-click or automated build? Regular build cycle? Testing cycle?

Anyway, check it with this well-know thing known as Joel Test, after Joel Spolsky:
http://www.joelonsoftware.com/articles/fog0000000043.html[^].

Something tells me that your currect organization is not even close. I hate to tell you that, but it's better to be ready in advance — get ready for big troubles.

[EDIT]

You can try to change how things are done in the company if you have guts and experience, but technical and how to influence people, but I'm afraid the first thing to consider before it's too late: look for alternative employment.

Sorry for you,

—SA