The Quirky World of Software Development in the 80s
Written on
Chapter 1: A Glimpse Into My Past
In this segment, I reflect on my two-decade journey at a rather unconventional workplace that I began exploring shortly after graduating from college in the 1980s.
John, my boss, managed two companies rooted in engineering and electronics, and I found myself in his electronics venture. I aim to keep the technical jargon to a minimum, so I hope you’ll find the stories engaging without getting bogged down by programming specifics.
Image created by the author, Autistic Widower.
The Version Control Catastrophe
About a year prior to my employment, John had begun marketing equipment designed to print batch numbers and expiration dates on factory labels. Each system utilized an Apple II computer paired with a standard dot matrix printer and custom circuitry he developed.
He crafted software in BASIC that allowed factory workers to manage the printer and maintain digital records. Initially, my responsibilities revolved around designing and assembling circuits to connect the computers with various production line devices.
Eventually, John ventured into creating his own printer to eliminate reliance on pre-made mechanisms. He attempted to use the Apple II to transmit data directly to a print head, but his compiled BASIC program proved to be too sluggish.
Having dabbled in assembly language programming on my Commodore 64, I decided to optimize John's program. Armed with my trusted Commodore 64 Programmer’s Reference Guide, I began coding in 6502 assembly language. The similarities between the microprocessors of the Commodore 64 and Apple II made this resource invaluable.
John was ecstatic when my program met his needs, which led to me taking on more of his software-related tasks. This pivotal moment helped me establish my role within the company.
When John requested modifications to his existing BASIC code, I stumbled upon his disorganized method of software management. I was handed a box filled with 5 1/4 inch disks, each labeled “Latest,” which didn’t help clarify which version was current.
It took considerable effort to discern the differences among them, and the code itself resembled a tangled mess—an unfortunate stereotype of BASIC programming. GOTO statements littered the code, complicating my attempts to understand its functionality.
Keep in mind, this was the 80s, long before the advent of sophisticated screens and software tools for code analysis. I often found myself regretting that I had impressed John with my assembly language skills, as taking over his software work introduced significant pressure.
John's code made perfect sense to him, leaving him puzzled by my struggles to implement the changes he desired promptly. Nevertheless, I persevered and gradually introduced small enhancements while adding version numbers and meticulous records of all changes.
Initially, John viewed my record-keeping as an unnecessary chore, but it eventually proved beneficial when inquiries arose about project timelines or the origins of specific changes.
Thank you for taking the time to read!
My Unusual Workplace Experience
After finishing college in the 80s, I dedicated 20 years to a place that could only be described as quirky. My boss had a unique style that made the workplace feel quite unlike any other...
Chapter 2: Mental Health in the Workplace
This documentary explores the complexities of mental health in the workplace, shedding light on the unique challenges faced by employees in various environments.