Programming is what I do best. I have programmed for more than 20 years and the act of creation itself is enjoyable but what will move a job from “like” to “love” is the opportunity to use my skills to improve the productivity of others. For all my years at AT&T I created programs and procedures that allowed other people to do their work better, faster and easier. I would welcome the chance to do the same at your firm. I have more than 20 years programming experience across a wide range of languages and platforms. I am almost entirely self taught and have always brought value to any group where I have worked. Even when starting with new equipment and programs I have always quickly brought myself up to speed and found ways to increase the efficiency and productivity of my co-workers. I feel I would be a great asset to any organization.
I have always produced a great deal of work and not just for myself. I have always provided programming assistance to others and, for many years, I was the “go to” guy for programming help. People would come from other groups to ask my help, sometimes just to fix a bug, other times to create programs or entire applications. At one time I had created so many utilities in EXEC2 that I wrote up a catalogue of these functions which I then distributed to everyone who might be able to use them.
Each new assignment in my 24 years at AT&T brought a complete change in technology. When I started there in 1974 I had never seen a computer but soon learned to use the time-share computer terminals in my new group. I found that our programs were written in FORTRAN, so I bought a couple of used books and taught myself to program. Soon I was writing programs for people in my group and was temporarily promoted from clerk to programmer and given a major program to write. I completed all work successfully and on time. When I moved to a new group I found they used the database program RAMIS. I not only taught myself RAMIS but used my programming skills to perform an incredible feat.
A man I had worked with previously came to me and said that his boss wanted an application created in RAMIS but that he wanted it done in one month. One month or forget it. Everyone, including me, agreed that by normal programming methods it would take three months to do the work. I accepted the challenge because I had an idea of how I might do it. I spent the next three weeks writing, not his application, but a program I had been considering that would write the bulk of a RAMIS application automatically. After this new program was written and tested, I turned to his project and completed all work, not in three months or even one month, but in ONE WEEK. The resulting application was not only accepted, but was considered so valuable that it was made in a corporate program and transferred to a maintenance group. That is the kind of work I do.
My next assignment was for a group that used C in a Unix environment. I not only taught myself C but Shell scripting, with the same success as before. I have used C ever since in both Unix and Windows and am currently teaching myself Visual Basic and have been using Microsoft Access for more than a year to keep track of personal information. I would be glad to show you my work and even walk you through any of my applications.
I have worked the entire life cycle of programming from initial interviews to design and then coding, testing, documenting, training and maintenance. I have organized and chaired walkthroughs to get feedback from stakeholders.
Beyond that I have never confined myself to the programs themselves. I have made substantial changes to the way technical documents are written. I have created forms, methods and procedures to fix and improve the way business is done. I have never been content to simply do the same old work in the same old way. Everyone who has every worked with me has had their jobs improved and made simpler because I was there.
At the end of my time at AT&T one of my job was Technical Support which included diagnosing trouble in our Network from thousands of miles away and walking technicians through fixes without being able to see any of the equipment.