Take the typical recent Computer Science graduate with a BS degree in Computer Science. If I were to ask her/him, the day he/she graduates, what is the largest program he/she has written, what would I get an an answer?
I am thinking the way to measure the size of a program is lines of code not because that is a particular good measure but is easy to compute and objective.
You would get a wide variety of answers, partly dependent on whether there was a Project Course as part of the curriculum.
It might range from a few hundred lines of code (a few pages printed), to a few thousand, produced in a project course.
Of course, a project course might be a team effort, so the individual contribution could also vary widely. Some students, unfortunately, just take over a project and do it all, leaving teammates unsatisfied. Some others, also unfortunately, do little to contribute.
In the compiler course I taught for several years, there was a lot of programming, but also a lot of scaffolding. Similar in the "capstone project" course.
But the data structures course had shorter, but very intense programs, and they were no less important for their smaller size. The object is insight, not bulk.
And some of those large projects begin with professor-provided scaffolding to give a structure to the project.
I think you need to live with the fact that there isn't really a very common answer to such a question. You need to discus, perhaps, the nature of the code they have written, not its "size".
