How I Got Into Development…
After I become an automotive technician about 2011, I was surprised to learn that the software we used regularly was rather dated, and some of it looked like it came from the era of Windows 98. There were third-party add-ons, but integration was limited. It was glitchy and, at times, very aggravating.
A coworker of mine insisted that I would be able to write my own program to take on the giants. I had tinkered with HTML and CSS long ago but knew nothing of programming. I inquired of friend what language I should use. He recommended Python. I hesitated in getting into programming. There’s no way I could ever write complex computer programs.
I took a technician job at new location. Even though the software was different, it still lacked efficiency. There was so much time wasted walking around to communicate. We picked up a third-party software that was in development. I was trying to suggest improvements that the salesman didn’t like. They didn’t work in a shop environment, I did. They were supposedly trying to build a program to help me but yet didn’t want to hear what it would take. He got so mad he said to me, “If you are so smart, why don’t you write your own program!” It was then that it occurred to me: “I didn’t want to be the idiot writing programs who didn’t know what he was doing. They are already out there, what’s one more?”
What I Like to Build
I enjoy building things that make what you easier, simpler, and less frustrating. Details matter. Some of the things that irritate you the most is when the fit and finish just isn’t there. It should feel natural to use. It shouldn’t have a bunch of quirks that make you think of “how it should be” every time you use it.
Things I Like…
- Spending time with my family.
- Logic and problem solving—I have to figure it out.
- The Bible and the local church.