Discussion about this post

User's avatar
Don Midwest's avatar

I realized by 1982 that what talented people could do with system development exceeded methodologies. AI is mechanized methodologies.

I started work at AT&T Bell Labs in 1978 when AT&T had a million employees, the largest company in the world, and Bell Labs was the best Research & Development lab in the world Sometime in the 80's I added a subheading about Bell Labs: "for a regulated monopoly."

I came from academia and convinced our hardware/software development project to hire David Parnas as a consultant. He was one of the best software engineer researchers in the world and his work underlies what today is called object oriented programming. We implemented his document driven method and wrote a paper published in the Bell Labs Technical journal titled "Using Documentation As A Software Design Medium". Our initial project produced sample documents and later they gave me the job to do a technology transfer of the method throughout the company. The implementations went very well. In 1982 I was offered the job as a manager of software engineering at National Bureau of Standards, NBS, now called NIST.

I transferred the method to 40 projects which from ranged from small to huge, from handheld devices to reimplementation of large systems and hardware development. Key people that championed the methods read the article above, looked at sample documents from other projects and were off and running. The clients on the projects were MS and Ph.D. developers. Two main areas of early adopters were old timers who noted that the method was just systematic reading, writing, and dialogue, and the other group were Ph.D.'s in physics who realized the need for an underlying model which was provided by the document framework.

I was a true believer in the power of design and human practice. Like the amazing projects described by Roger Boyd in this article, there were individuals and teams who did incredible work, who in my case, used the design by documentation method leading to the set of documents using the same names and often using the same symbolic abbreviations. In hindsight, I was naïve and thought that all I had to do was to interview these brilliant people to capture the essence of their work. So I began extensive interviews, listening as hard a possible, and recording their experiences. After a while I realized that their stories did not converge. These people were doing something beyond the methodology and recording what they did using the document framework. I thought that through interviews, with the starting point of a common document framework, I could tap into collective experience, The stories didn't converge. I had been given the opportunity to understand the creativity of design but in fact I realized that the people were doing what was far more important than the methods.

For years, I took it as a personal failure that I had been on the forefront of software engineering working with talented people but I was unable to capture the essence of what made the difference: people, project, new hardware, new challenge, looking at old problems in a unique way, etc. After a few years I realized that there are 26 letters in English, and a few other symbols, but that does not explain what a novelist does to create a story. I can now accept why my attempt did not succeed and how I was blinded by the excitement of project design and implementation.

I turned down the job offer at NBS because I knew that I did not understand software.

So, here we are in 2025 and this article by Roger Boyd recounts his experience in software and predicts that the AI fad will not deliver the huge returns because it is extracting resources from past successes with little to additional benefit. I agree.

Expand full comment
Al Felix C/S's avatar

Back in the stone age AT&T had labs to test both their equipment and vendor equipment sw updates and generic upgrades. This enabled the company to reach their 5 nine's goals (99.999) product availability. the lab I worked in tested signaling (as opposed to voice) data. Never had issues when the work was in the network.

we were appalled when we got a new boss who proclaimed how much $ could be saved by "offshoring the lab" to Texas. "Why test it twice" despite being told how often we caught issues because our testing was far more thorough. even tho he looked like Millhouse from the Simpsons the idea of cutting spending impressed the higher ups more than providing first rate service.

Expand full comment
5 more comments...

No posts