In 1994, just after I got married, I started working on a DOS program for doing Bible searches. Yesterday, I released version 8.3 of this same program.
Of course, the original code I wrote in 1994 isn’t actually being used any more, but what originally was known as Bible Assistant was consistently re-worked and improved to eventually become the mature application today known as SwordSearcher.
Here’s a picture of me holding up the very first order form I ever received for my Bible software.
The order form is dated December 26, 1994. (I’m outside in a short sleeve shirt because I was living in Hawaii.)
At the time this photo was taken, my “real job” was digging ditches and working on septic systems. I didn’t know it back then, but my real job was really writing Bible software.
It took me another seven years to get to the point where I would no longer need to hold down side-jobs to pay the bills. In the early 2000s, I quit my job at RadioShack, where I helped customers find batteries and resistors for five years.
Since then I have spent most of the working hours of my days developing my own Bible software and working as an independent contractor on other people’s projects.
It only dawned on me last night, as I wrote up an announcement for version 8.3 of SwordSearcher, that I had been doing this for 25 years. What tremendous grace of God I have been shown – to be able to work on technology for studying the Bible for nearly my entire adult life!
I also completely re-designed the SwordSearcher website. It has been six or seven years since I made any significant changes and the site was just not up to par for 2018. Hopefully this will be a bit better, and Google will stop telling me that I am losing traffic because the site wasn’t mobile-friendly… Now I just need to write more content. I much prefer the coding. :-)
VCF East had the ultimate Commodore showcase, the Commodore Retrospective Exhibit. Here’s the video, which serves as a quick survey of the history of Commodore machines, starting with typewriters. That Commodore 65 prototype that the guy grabbed for $40 could sell for thousands on eBay.
Vendor lock-in is a barrier to entry, not an incentive to stick around.
15 years ago or so, I started using a program called eWallet to store sensitive data like passwords, financial account info, and pretty much anything I need to keep around but wouldn’t want someone else to see, locked with a master password. Over that time my database grew to over 900 items. For YEARS I have been frustrated with this application because their mobile support only barely works for me — there is no automatic sync and their Windows Mobile support is essentially abandoned, and manual mobile sync was one-way. The worst part of this is that Illium Software deliberately locks you in to their system by not giving you a structured export method. You can dump your data but only into a flat text file with no field delimiters (and despite my expertise using RegEx to parse stuff, there would be no way to do a thorough conversion without manually fixing hundreds of custom fields). So you can imagine I have been reluctant to switch! But I really wanted to start using Enpass — because they support all platforms and even Windows Hello on my Windows Phone with a great UWP app, with auto sync using OneDrive…
Today I finally found a way to move my data without loss and extreme amounts of labor. Somebody wrote a “data liberator” for eWallets that runs eWallet in its own process, pulls all your structured data from memory and dumps it into an XML file for KeePass. So, I installed KeePass, imported my wallet data into KeePass, exported that to a KeePass XML file, and finally imported into Enpass.
Looks like I have everything, even all my custom fields, in proper folders, with only a little bit of category management to do. Yay!
The KJV-TSK for integrated cross-references right in the text of the King James Bible. This is one of those seems-obvious-now-that-it’s-in-there kind of things. It is also one of those can’t-do-without-it-now-that-I-have-it kind of things.
Complete, comprehensive support for Windows 10 scaling functionality. What’s that all mean? Perfect text rendering on ultra-high DPI screens, like the one on the Surface Book. (Believe it or not, this was the single most labor intensive part of the work on this new version, even though it is hardly glamorous and even difficult to demonstrate.)