A former president of Microsoft’s Windows Division, Steven Sinofsky, recently took a nostalgic trip down memory lane, reflecting on the coding practices that defined Microsoft during the 1980s. In a surprising twist during a discussion about modern software’s demands on RAM and resources, Sinofsky shared that from 1980 to 1990, “every Microsoft engineer got a stopwatch,” emphasizing the importance of efficiency in that era. He humorously noted that “Extras were in the supply room,” highlighting the resource-conscious culture that prevailed at the time.
Sinofsky elaborated on the significance of these stopwatches, which were utilized for a wide array of tasks, including “scroll speed, boot, exit, save, compilation, and print.” His reflections paint a vivid picture of a time when managing resources—such as clock time, disk space, and RAM—was paramount in software engineering. He stated, “From 1980-2000, half of software engineering was managing resource usage,” a testament to the rigorous standards that shaped core products like MS-DOS, Windows, Word, Excel, and Office.
Do people prefer ‘whizzy spinning’ things to raw speed?
In a light-hearted anecdote, Sinofsky recounted an instance involving a colleague, Plummer, who humorously lamented the absence of a free stopwatch in 1993. Although Plummer’s request fell outside the promotional period, he recalled Microsoft’s response, which deemed a stopwatch “too expensive.” Reflecting on this decades later, Plummer remarked, “While I clearly resent it enough to bring it up 30+ years later, it went a long way toward setting the fiscal accountability I brought to my career.”
Microsoft’s new performance pledge
Sinofsky’s reflections come at a pivotal moment for Microsoft, particularly regarding its Windows operating system, which has faced mounting criticism for its declining focus and performance. Users have expressed frustration over the OS’s resource consumption and the increasing integration of AI features that some feel detract from core functionality. In response to this growing discontent, Microsoft’s management recently acknowledged the situation in a detailed blog post, outlining a commitment to improve performance, reduce overhead, and enhance reliability across essential services such as Explorer and Windows Update.
The company has pledged to be more intentional about resource utilization and the integration of features like Copilot. As Microsoft embarks on this renewed efficiency initiative, the tech community watches closely, eager to see if these promises translate into tangible improvements. One can only wonder if, as part of these plans, developers might once again be offered free stopwatches to keep the spirit of efficiency alive.
