Struggles of new college graduates in their first software development job

ABSTRACT

How do new college graduates experience their first software development jobs? In what ways are they prepared by their educational experiences, and in what ways do they struggle to be productive in their new positions? We report on a "fly-on-the-wall" observational study of eight recent college graduates in their first six months of a software development position at Microsoft Corporation. After a total of 85 hours of on-the-job observation, we report on the common abilities evidenced by new software developers including how to program, how to write design specifications, and evidence of persistence strategies for problem-solving. We also classify some of the common ways new software developers were observed getting stuck: communication, collaboration, technical, cognition, and orientation. We report on some common misconceptions of new developers which often frustrate them and hinder them in their jobs, and conclude with recommendations to align Computer Science curricula with the observed needs of new professional developers.

REFERENCES

• 1: Eric Brechner, Things they would not teach me of in college: what Microsoft developers learn later, Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, October 26-30, 2003, Anaheim, CA, USA [doi>10.1145/949344.949387]
• 2: Mark Guzdial , Allison Elliott Tew, Imagineering inauthentic legitimate peripheral participation: an instructional design approach for motivating computing education, Proceedings of the 2006 international workshop on Computing education research, September 09-10, 2006, Canterbury, United Kingdom [doi>10.1145/1151588.1151597]
• 3: Lave, J. and Wenger, E. (1991). Situated learning: Legitimate Peripheral Participation. Cambridge: Cambridge University Press.
• 4: Timothy C. Lethbridge, A Survey of the Relevance of Computer Science and Software Engineering Education, Proceedings of the 11th Conference on Software Engineering Education and Training, p.0056, February 22-25, 1998
• 5: National Research Council. (1999). How people learn: Brain, mind, experience, and school. Washington, D.C.: National Academy Press.
• 6: Perlow, L. (1999) The time famine: Toward a sociology of work time, Administrative Science Quarterly, 44(1), 57--81.
• 7: Dewayne E. Perry , Nancy Staudenmayer , Lawrence G. Votta, People, Organizations, and Process Improvement, IEEE Software, v.11 n.4, p.36-45, July 1994 [doi>10.1109/52.300082 ]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Productivity

General Terms:
Human Factors

Keywords:
computer science education, human aspects of software engineering, software development