Need help understanding big projects

Question

0.00/5 (No votes)

See more:

Hi,

I just started work as a software developer after finishing uni. Ive never worked on large systems or really had to deal with legacy stuff, only ever worked on my code or from scratch.

Im trawling through all the code and millions of diffrent classes trying to figure out how they fit together and work as ive been given various small tasks to complete.

Basically looking for any tips people have for my situation, i need to understand the system quickly so i can start being useful.

Posted 6-Jun-14 4:32am

Carl Mailey

Add a Solution

3 solutions

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)

Debabrata_Das · Answer 1 · 2014-06-06T05:03:00

Hi Carl,
I believe all developers must have gone through this phase which you are currently facing. I would suggest few simple points which might be helpful:

DOs
1. "Book is our best friend" - Refresh your programming knowledge. Grab a book from library/store and start reading step by step.
2. Try implementing things you learn from book practically.
3. Once you gain more knowledge, you'll feel more confident.
4. Focus one thing at a time.
5. Have patience, everything will be alright. :)

DON'Ts
1. Mostly freshers get panic looking at errors. Don't panic, errors are born to be fixed.
2. Don't try so many things at a time.
3. Never give up, you'll get success.

I would love to provide more guidance if required though I'm not a good writer. :)

Wish you all the best. :)

- DD

Garth J Lancaster · Answer 2 · 2014-06-06T05:11:00

I would try to generate class diagrams - especially if they have assemblies, you can look here on CP for Marc Clifton's free tool and do it by reflection (or pay for a tool, eg Redgate) - or if they have a workspace/solution, get VS to generate class diags for you - then start making notes as you go - you may not need to do all you see straight up anyway, just 'around' the code you're being asked to change

Any 'decent' shop should have a guide to their code base, architecture diags etc - its just a matter of finding it/trawling through their repository

good luck
Garth

Peter Leow · Answer 3 · 2014-06-06T05:13:00

Solution 3

Adding to the advice by Debabrata, you may be able to get some useful tips from this article: 4 Things You Need To Know About a Career in IT[^]

Posted 6-Jun-14 5:13am

Peter Leow

Comments

Debabrata_Das 6-Jun-14 11:36am

Thank you Sir :)

Need help understanding big projects

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0