I went into the job of programming a database system without
having a clue of what a database was. Furthermore,
I didn’t know SQL or the dBase programming language (DBL), and I had no
concept of what USAFMSA did, or what their data represented.
I knew what dBase tables were, but the data looked like nonsense.
Make that over 1.7 million records of nonsense – in one table!
Eventually someone explained the data layout so I could
understand that a hierarchy existed in the data. There are headers, then under the headers, paragraphs, then
under that, detail lines. So
that meant I only had to worry about a few of the 11 thousand headers at a
time. That still didn’t
compensate for my lack of database knowledge.
The only strong programming foundation I had was in C++ on a
single PC. So, I started small,
but fortunately, that’s all the system needed at that time.
The first task I remember was to put some copy / paste functions into
the editing grid. It took a
while to get used to the dBase syntax, but I eventually got the job done.
I was amazed at the boss’ surprised reaction when I first
demonstrated that he could now copy multiple lines of data, or even delete
multiple lines. That simple
function had never been available in the system before.
Clearly USAFMSA needed to upgrade.
Despite my lack of experience, I trudged onward, gradually
picking up knowledge on database systems, SQL, dBase, and Force Management.
My programming skills grew by experimenting and researching
independently, but most of my Force Management knowledge is from observing
the documenters and discussing new objectives with my boss.
After working long enough, I started to be known as the
expert on the TDABuilder program. I
began getting calls from people using the software around the world, and
visits from users in the workplace. After
my manager discovered this, a notice was sent out to shield me from doing
user support so I could work on the necessary features. We weren’t neglecting the user’s needs, but I had a
specific objective, and it was the responsibility of the “help desk” to
provide user support. Compare
that to when I first started working, my desk was in the basement, and no
one really knew who I was or what I did.
From the learning experience prospective, this internship was
very successful. I was able to
apply my existing knowledge of software programming to a real project, and
learn many other valuable skills used in the software industry and the
workplace. Technical skills can
be learned in the classroom, and sharpened with practice, but workplace
skills can only be learned on the job.
Especially in Dept. of the Army, rank is a very important
factor for many decisions. Most
of the people at USAFMSA are retired military, which I would suggest adds to
the regard for order. However,
being a technology expert put me in a unique position.
Even though I was “bottom of the totem pole,” the project I was
working on affected the entire organization and consequently my status was
raised a few notches. However,
depending who was my direct superior, I found there were different ways I
had to act. Generally, my
bosses fluctuated mostly on how controlling they were.
Some were especially concerned that I was working only on whatever
tasks they had specified, and usually wanted frequent progress updates,
while others trusted that I was working toward the best interest of the
organization and only needed status reports every once in a while.
