Stories from Shell of an Idea
summary
PowerShell nearly doesn't ship; adoption hinges on getting Exchange to commit and on choosing a tiny workable core rather than every feature. Remoting is almost in v1, but it transmits objects as remoting serializes objects to XML losing methods; buffering lands later after someone implements remote buffering in 13 lines of code. The shell invests in a heavy parser so 30-parameter commands work for commandlet authors, and legacy cruft like filter stays because backward compatibility wins.
AI-written summary · about
chapters (19)
- 0:00PowerShell's origin stories
- 1:14PowerShell's rocky start
- 3:21PowerShell syntax trade-offs
- 5:07Clear product vision
- 8:00Microsoft's old dev cycle
- 11:59Provocative statements drive change
- 15:53Bill Gates' bifocal analogy
- 18:43Power of analogies in persuasion
- 20:31Ken Hansen's tactical coding
- 23:25PowerShell's filter keyword legacy
- 27:41Backward compatibility in software
- 29:27Why PowerShell had to win quickly
- 31:09Investing in parsing for adoption
- 34:00PowerShell pipeline evolution
- 37:12Consistency vs user experience
- 38:59Exchange team adopts PowerShell
- 45:24Remoting and Exchange Server
- 46:06Backward compatibility Windows to Core
- 47:33Closing remarks & Q&A
related talks
44mPowerShell Perspectives
41mto-Peer PowerShell: The Ins and Outs of Pair Programming
46mWhat I learned Judging 5000 Scripts
01h 31mPowerShell & Your Next Career Steps: Oh the Places You'll Go
43mThriving Through Transitions
48mCtrl-Alt-Del: Learning to Love Legacy Code.
56mMy Worst Code Was My Best Code
50mOld Is the New New