MS-DOS's Relationship with CP/M
Tim Paterson (QDOS/86-DOS) (1981)In 1980, Seattle Computer Products needed an OS for 8086 boards. CP/M-86 wasn't ready. Tim Paterson wrote QDOS—Quick and Dirty Operating System—explicitly modeled on CP/M but rewritten for 8086. Not the primary wife; the concubine. QDOS knew its place: provide CP/M-like functionality until real CP/M-86 arrived. Then Microsoft bought it, renamed it MS-DOS, licensed it to IBM. Suddenly the secondary option became standard. Thunder above, Lake below—the eldest son leads, youngest daughter follows. MS-DOS always followed CP/M's footsteps, conventions, command structure. Never innovator, always follower. But the follower won—through tactical reserve, timing, understanding its actual position. The marrying maiden making herself indispensable.
Practical Integration
You're in secondary position. The thing that comes second, follows the established pattern, makes no claim to originality. The classical text is clear about the danger: if you're in secondary position and try to act like you're primary, disaster follows. MS-DOS succeeded because Paterson didn't pretend to innovate. He explicitly copied CP/M's conventions. This wasn't plagiarism—it was tactical clarity about actual position. He needed an OS fast for 8086 hardware. CP/M was the model. So he built a CP/M-like system. Honest about the relationship. He called it "Quick and Dirty" for a reason. Here's the paradox: the follower can become dominant, but not through usurpation. MS-DOS didn't defeat CP/M through technical superiority. It won through timing (IBM PC deal), accessibility (cheaper licensing), market dynamics. The maiden who maintains correct behavior within her actual position can ultimately achieve recognition. But that's different from trying to seize recognition prematurely. What matters for your work: if you're building something derivative—and most things are derivative—be honest about it. Don't pretend you're inventing from scratch when you're adapting existing patterns. That's not weakness; it's clarity. The value is in the adaptation, in serving the new context correctly, not in false claims of originality. Paterson's honesty about the nature of QDOS allowed it to succeed in its actual role. When Microsoft bought it and licensed it to IBM, the secondary thing became the standard—but the underlying relationship to CP/M remained. MS-DOS was always the follower. That was fine. It served the role well. The text warns: undertakings bring misfortune. This doesn't mean do nothing. It means don't overreach. Know your position. Maintain tactful reserve. Build what's actually needed, not what your ego wants to claim. The maiden who tries to supplant the mistress ends badly. The maiden who serves her role correctly can thrive. Secondary position isn't inferior position. It's just different. Know your place. Do the work. Let the rest follow from correct behavior in your actual role.