After graduating college with a B.S. computer information science degree, I was hired by Rollins Truck Leasing for a position with the branch teamto develop software for their branches and truck terminals. The software tools I used to develop at Rollins were Visual C++, Borland C++, Clipper (a dBase compiler) and SQL Windows. Databases were SQLBase, IBM and dBASE files. Also, I did a lot of embedded software for handhelds and devices.

The Clipper programming was for accounting and other applications for the branches. Before the internet, data was uploaded and downloaded daily to corporate by dial up. I recall accounts payable, receivable, general ledger and other other various programs.

A lot of the programming I worked on was for embedded systems. I programmed different handhelds for several tasks such as starting fueling transactions and scanning trucks, employees, drivers and barcodes to control other devices. I worked with an engineer that designed a controller box that controlled fuel pumps, solenoids, switches, monitors for the ground fuel tanks, etc. I learned to download and embed the software to the processor and burn chips. Also, I worked with cables such as RS 232 used to connect devices. Sometimes I traveled to branches throughout the United States to help install these systems.

The handheld barcode reader for this system connected to the controller which connected to the office PC which dialed up to corporate. At corporate we could monitor transactions in action at any branch, watch the switches, the fuel pumping to the 1/10th of a gallon and everything happening at a branch. This system caused Rollins to watch a lot of fuel being stolen by branch employees who were used to using terminal fuel for their own personal usage. Of course they were fairly warned after being caught but needless to say, it takes adjustment to being monitored so closely from a corporate office to a truck terminal that might be int he middle of a desert in Tucson.

At one point when Windows development became the mainstream, different members of our team were asked to recommend between Gupta SQL Windows, PowerBuilder and Visual Basic 3.0. Others recommended SQL Windows because it was the most powerful and integrated with Gupta SQLBase. I recommended and argue for VB 3.0 which at the time was the weakest product. I recommended PowerBuilder as the second choice. My reasoning was that I thought that Microsoft had a more likely life expectancy and programmer base. Though they redeveloped all of the software in SQL Windows, a few years later after I was gone, they did another rewrite in VB 6.0. because of the two reasons that I had argued.

At Rollins I had made many friends many of whom I am still in contact including the IT directory and my direct manager of Branch Applications. We still have a Rollins IT reunion and get together. It was a very memorable time and we were like family. This was my second position and first position at a fairly larger IT department.

back