ff4930
Junior Poster in Training
58 posts since Oct 2007
Reputation Points: 34
Solved Threads: 3
In my case I get my assignments from my supervisor. It's either a change in an existing program, or e.g. creating a new interface from scratch. In the first instance, you can change a lot of small things in a day. The latter will require more in depth study and communications with suppliers and such.
I work with four other colleagues and the source of all applications is in CVS. This enables multiple programmers to work concurrently on the same project.
pritaeas
Posting Expert
5,445 posts since Jul 2006
Reputation Points: 653
Solved Threads: 871
Haven't you been to work experience yet ?
When I went to work experience, We (me and another friend) ended up getting a placement at Juiced Games for 2 weeks. That gave me a big experience of what programming can be like in a job. To be totally honest, it was a very relaxed environment, the only thing you had to watch out for is something called sprints. A sprint is a deadline to complete a task, and if you fall behind then I guess you have a problem. We also got to see a few of the programmers at work, and it looks like a lot of fun. Every 30-60 mins they would compile their new project and test for bugs. Some programmers would be developing the game itself, while others would be producing tools for the Artists to use.
I hope this answers abit of your question :)
William Hemsworth
Posting Virtuoso
1,591 posts since Mar 2008
Reputation Points: 1,429
Solved Threads: 129
Your professor may have last compiled a "massive project" in 1970. :)
My workstation compiles and jars a Java project of 869 source files in ~20 seconds. Incremental background compiles while editing are near enough real-time.
Ezzaral
Posting Genius
15,985 posts since May 2007
Reputation Points: 3,250
Solved Threads: 847
Oh, and what about the Metaprogram compiles for languages that support templates?
Would that not be longer if there are a lot of template algorithms used? >_>
I am kidding a bit:)
Obviously I can't speak for many platforms that I've never used and "massive project" could encompass many builds that do perhaps take a long time ("long time" not really being quantified either).
The statement did remind me however of a co-worker's story of some training class he had to take years ago in which the "instructor" (using the term loosely, since he pretty much just read the Powerpoint slides to them) told them that it was more efficient to have all of their code read by someone else (yes, read, line by line) before compiling it - and no, he was not referring to logical code reviews. When they asked him to clarify that a little, since most of the people in the class were sure he couldn't really mean what he was implying, he said syntax errors could waste a lot of compile time that could be avoided by carefully checking the code first. :-/
Ezzaral
Posting Genius
15,985 posts since May 2007
Reputation Points: 3,250
Solved Threads: 847
Except you didn't say how long compile times can be for massive projects! O_O
I recall my professors saying that compiling can take a very long time... so it's best to get things right the first time X_X
It took them 10+ minutes to compile the average of about 10 millions lines of C++ code that goes into one of their games. ;)
William Hemsworth
Posting Virtuoso
1,591 posts since Mar 2008
Reputation Points: 1,429
Solved Threads: 129