If I may .... I was considered one for a small while. It was 1988, I had just attended John Ousterhout's intro to TCL at UC Berkeley, and I was smitten. At tha

If I may .... I was considered one for a small while. It was 1988, I had just attended John Ousterhout's intro to TCL at UC Berkeley, and I was smitten. At that time, the company I worked at was developing network management systems for the big telecoms of that era, and the front and back-end software was a horrendously complex system built atop a proprietary C++ framework and distributed object system (before CORBA). Any change to the system took ages to understand, make and compile. I realized in that TCL talk that I could wrap every C++ API function of the framework with TCL, and use it for configuration and testing and CLI apps using the framework. In a feverish daze where I lost track of time but later realized was 16 continuous hours, I learnt TCL and wrapped the entire back-end API. I demoed it the next day and the reception was rapturous ... the testers loved it, the marketing people loved it because they could demo changes instantly, the developers found a release from C++. I was the guy who enabled all devs become 10x devs. It lasted a small time, after which people got tired of the idiosyncrasies of TCL. But the scripting bug had caught on. The entire API was wrapped up in Python, and Python became the primary way to build systems using that framework. Meanwhile, I learnt Perl and wrote a book for O'Reilly (Advanced Perl Prog-- the panther book). I dream about going in that kind of zone again.