@tofu said:
Just to clarify, the issue with my resume wasn't one
of LOC/day. It was an issue of, "how big was the last project you
worked on?" Using LOC to answer the "how big" question seemed
reasonable to me. I wouldn't think of using LOC to answer the
"how productive are you" question. It's just that when I tried to
use it to say, "hey look at how big this project is" my supervisor
responded with, "you've got nothing to brag about, it took you a too
long to write it."
I just wanted to see if anyone here would
have a similar reaction, because I wouldn't want to have that on my
resume and turn a lot of people off. You know, there are a lot of
stupid little things that you can have on your resume that just scream,
"I'm an idiot!" Things like, "skilled with all versions of
MicroSoft Office" Would you hire a programmer who would waste
space saying something like that?
So anyway, that's what I was asking.
How big a project seems will depend on a person's experience. For
example, I would think a 15KLOC program is small. The SLOC count
of the systems I have worked on is 200K - 1.5M. Now these are two
different things and it is comparing apples and oranges. The
systems I have worked on have been around for years and many people
have come before me to work on them and many people will come after I
am long gone. On the other hand it sounds like the design and
development of the 15KLOC program was mostly your responsiblity and
there is a big difference in the experience gained in both of these
situations.
For a resume, I would think that what experienced you gained and what
skills you have picked up would be of more importance than the size of
the project.