Why I Love Technology

Posted on September 15, 2013 Updated on December 1, 2023

Technology was not native to me, at least relative to children and young adults today. Simple four-function calculators started becoming popular when I was in Elementary School. I only had a single computer course in High School (it was the only one offered). We had a Timex Sinclair and, later, a Commodore 64 computer at home. It was fun, but I wasn’t hooked yet.

I started a car and motorcycle parts business when I was 18. Initially, I was looking for a way to get cheaper parts for myself and thought if I could make money doing it, then all the better. Nearly everything I did was manual. Then I learned about a Radio Shack TRS-80 at college that had a word processing program. I used that to create mailings to parts companies, distributors, and potential customers. Before long, I had a catalog of products I could sell and a small but loyal customer base buying products and services from me. If Quickbooks had been available back then, I may have kept the business running. Doing everything manually just took too much time. Even so, this was my first technology win, and I liked it.

A few years later, I was programming at a local marketing company. The MIS Director (what IT used to be called) purchased a new relational database product with a 4GL application language. This was in 1987, and this technology was very new. The product was sold as saving “75% of your development time and effort.” Most seasoned people in the group did not want to risk their reputations on something that might not work.

I was new and had nothing to lose, so for the next month, I read every manual cover-to-cover. Before long, I worked on new applications and soon became the in-house RDBMS/4GL expert. This led to a fast track of promotions and being selected to develop the majority of new custom applications sold by our company. It was not easy, but it was fun and good for my career.

My first and arguably most influential mentor was my manager at this job (Jim). He taught me about designing parameter-driven systems that were flexible and extensible. He also taught me that “good enough usually isn’t good enough.” Most people are lucky to have one really good mentor during their career. I’ve been blessed with four of them at different stages of my career. It has motivated me to return the favor and help others whenever possible. This job helped me grow in so many ways.

A few years later, I worked at a software company creating a new standard product on this database platform. Nobody was trained on the product, and most wrote their embedded C / SQL programs like any other 3GL program (i.e., non-transactionally). I pointed out to the VP of Development that this would be a problem. He didn’t want to hear that. I pushed for a concurrency test, and everything locked up. Many people were suddenly upset with me, but the longer you wait to solve problems like these, the more expensive it becomes.

We spent the next two months creating functions to manage transactions, optimizing everything (even table structures to get the best byte alignment), and making this new packaged system work. The VP now liked and respected me, which changed our working dynamics. That shifted the focus from people and personalities to technologies and results.

We also worked on other aspects of the system to enhance performance. We created a system much like Memcached in Perl (back in 1990) that allowed us to handle the workflow of even the fastest warehouses in near real-time. We did many leading-edge things at the time (HA clusters with automatic failover, automated restart of remote devices to resume work in progress to the point of failure, outsourcing to India using an X.400 connection that I configured, distributed systems, client/server systems, etc.) I learned a lot from that experience and was proud of the results.

Later, I worked for that database company (Ingres). This was in the heyday of consulting, where projects were huge, and rates were high. My first project (started on my second day on the job) was being assigned to redesign a Risk Management System at an insurance company that started using our products. I soon found that the project had been in progress for two years and had binders full of specifications, but nothing was actionable. I did not make many friends those first two weeks, as I pointed these things out.

I offered to facilitate a JAD (joint application design) session with multiple lines of business. This pointed out issues that even they were unaware of and allowed us to begin designing a flexible system that would accommodate all lines of business. We used an agile approach to prototype the new system, demonstrations to get buy-in, and moved the project forward quickly. Six months later, the first part of that functionality went live. The system was fully functional within a year!

I had the opportunity to work on some of the largest databases at the time (roughly 300 GB total, which is small by today’s measures), work on leading-edge technology (Clustering, VLDB, and Enterprise Unix systems), and really become a true Consultant along the way (with the help of another mentor – Bill). I was sent to several Unix Internals courses and then worked with our Engineering team to improve our products and create configurations supporting other large companies with similar problems.

A few years later,, I worked at a small start-up company that created the world’s first commercial JDBC driver. I have worked with many very smart people before, but now I worked with a couple of very brilliant people. My main contribution this time was on the business side, but we learned a lot from each other as we grew the business to over $1M in sales within the first year.

One thing that sticks with me is that I became interested in VRML (virtual reality modeling language) during this time. I had an idea (1997) that we could create a website to show the insides of buildings, productize them, and sell them to real estate companies and larger apartment complex owners. My idea was not well received by the team, but a few years later, systems like this were being developed, and a few people were making a lot of money. That taught me to have more faith in ideas based on new technology, regardless of what others thought. It also brought me back to an important concept in Business and Consulting, which is being able to communicate ideas and benefits in ways that are easy enough for everyone to understand as opposed to focusing on the technology itself.

Over the years, these lessons learned have helped with BI (business intelligence) – building dashboards using relevant KPIs tailored to the specific audience, mobile computing, cloud computing, IoT, and big data. Most people think these things are “not important until they become important,” often 6 – 12 months (or more) later. From my perspective, the real trick isn’t in trying to understand the next big thing but rather in considering better, easier, and more efficient ways of doing things you do today.

This is why I love technology. It has helped me accomplish many things that have had a tangible impact on the businesses I have worked for and consulted with. It has taught me to think about problems and ideas from various perspectives and to leverage lessons learned in one area to help solve problems in another (i.e., transfer knowledge and skills from one area to another). Technology has provided me opportunities to learn about and work on solving business and technical problems in several industries as I ponder, “Why not?” 

My interest in technology has allowed me to meet and work with many interesting and incredible people throughout my career in many industries and settings. That’s much more than I ever expected when I took my first programming course so long ago, and it has become a significant aspect of almost everything I do.

Welcome to this journey of discovery and sharing.