In the summer of 1984 I attended a seminar presented by Bob, a member of technical staff. I carefully listened and realized that my project would be changing some fundamental assumptions related to his talk. When the Q&A time arrived I asked this question– “If Grade of Service (GOS) is no longer a constant, i.e. a variable that changes for different connections, wouldn’t that have an impact on your results?” The speaker acknowledged my question with a brief response; I left the seminar feeling satisfied. After approximately a month into my summer job I understood enough about telecommunication networks to ask an intelligent question. What happen next surprised me.
About a week later, Arik, another member of technical staff, rushed into my office and stated “How did you know?”– referring to the question I asked last week. My question had prompted him to do some analysis taking into the account GOS as a variable. I assume the results had been significant enough to warrant Arik coming to my office. He paid me a complement; Arik spent his time to answer my question because he had become intrigued. So how did I know?
In the summer of 1984 I worked at the Bell Labs West Long Branch Campus. The group I joined consisted of engineers and mathematicians who specialized in telecommunication networks. They had begun to explore dynamic non-hierarchical routing (DNHR) for long distance phone networks. The challenge with any infrastructure consists of balancing the needs of the users versus the expense of the providers. Infrastructure can be a network of roads, sewer pipes or telephone lines. A phone call between Rockville, Maryland and Portland, Oregon would need to travel over a series of trunk lines and routing switches.
Hierarchical arrangement of routing calls had been the norm. Non-hierarchical implied not being restricted to a fixed set of routes. Routing dynamically implied that the routing could change depending upon the traffic demands. This needed to be done without sacrificing quality metrics- Grade of Service being a key one.
My summer job assignment– modify a FORTRAN program that implemented an DNHR algorithm to reflect different Grades of Service. This non-trivial task involved translating the constant GOS into a matrix of values associated with each route. This change involved making other changes to the calculation method of the algorithm. My technical supervisor, Magda, supplied me with background material which included using the Bernoulli distribution to represent network traffic. I figured out the coding changes required, navigated the Unix operating system and compiled the FORTRAN code on a regular basis. This project enabled me to build upon material I had learned studying electrical engineering at the University of Maryland. Specifically, I applied my knowledge communications, statistics and numerical analysis. I enjoyed wrapping my mind around a new way to route traffic. My work enabled me to ask a probing question during the seminar.
Thirty years later I still recall Arik coming to my office with– “How did you know?” I have cherished this moment because it buoyed early in my engineering career. Every time I doubted my abilities I would think back to that moment and know “I have the right stuff.” Not just to be an engineer but to be a inquisitive even when you’re new to field. While my engineering career took me in a different direction than telecommunications, I continued to ask relevant questions. The engineering fun continued when I sought the answers.
Have a productive day,
Dear Reader, What memory or question does this piece spark in you? Have you had an opportunity to ask a question of an expert? Has someone you admired paid you a complement regarding your technical acumen? Please share your comments or stories below. You too can write for the Engineers’ Daughter- See Contribute for more Information.