Lead Developer / Development History
The Lead Developer of these solutions started with Fortran in 1988. He progressed into the Database and Business System Software realm in the early 1990s. He put together his first web page in the 1996 time frame. With support from others, he quickly progressed into E-Commerce sites and credit card processing systems from there.
Credit Card Processing and Initial Accounting Systems
He and an old partner are believed to have been the first to pass a credit card in a production environment via TCP/IP to Bank of America's Visanet in the late 1990's (or was it early 2000's?). He built his first web based accounting system in 2002. He built and certified a credit card portal in 2003 with VITAL/Tsys. It was believed to be the only system at that time that was "almost" fully script based (aka non-compiled code). It was done "easily" in Classic ASP. Only a small compiled COM object had to be created to handle the byte array streaming requirement. Unfortunately, Microsoft's desire to send two bits for every bit as part of an encoding system that nullified it as a viable method for byte stream communication was "odd" once fully recognized. Given a true and proper byte stream object would have enabled more direct communication between hardware and scripting solutions with far, far less programming complexity, one has to wonder what that was really about...
He and an old partner are believed to have been the first to pass a credit card in a production environment via TCP/IP to Bank of America's Visanet in the late 1990's (or was it early 2000's?). He built his first web based accounting system in 2002. He built and certified a credit card portal in 2003 with VITAL/Tsys. It was believed to be the only system at that time that was "almost" fully script based (aka non-compiled code). It was done "easily" in Classic ASP. Only a small compiled COM object had to be created to handle the byte array streaming requirement. Unfortunately, Microsoft's desire to send two bits for every bit as part of an encoding system that nullified it as a viable method for byte stream communication was "odd" once fully recognized. Given a true and proper byte stream object would have enabled more direct communication between hardware and scripting solutions with far, far less programming complexity, one has to wonder what that was really about...
ERP systems for "Small Companies" worth 7 figures+ with technology you've been lead to believe doesn't work
He has background in very complex ERP Systems (Enterprise Resource Planning Systems), yet he's never worked as a full-time employee in IT for any major corporation.
In the early 2000's he developed a system for a Dye House facility in Charlotte NC.. They dyed garments for Brand Name Apparel companies including Champion, Abercrombie and Fitch, and others. That facility ran 24/7/365 with 40 employees. The enterprise system he developed handled all their inventory, sales orders, production orders, quality control reporting and shipping management. It eliminated the need for full time customer service agents. It allowed national and mulit-national companies to log into his business, view their own inventory in his warehouse and create their own sales orders (purchase orders) in his system and submit for approval. Then it allowed them to log in and check production status for every production order that made up their orders. They could see exactly what machine each order was on, what was in quality control for inspection, what was on the dock waiting for shipping , what had been shipped, what was in rework and where it was in rework.
It was built with Classic ASP using a Microsoft Access Database. Very little Javascript. The developer was only in the facility for two days total during an 18 month development and roll out process. It took 1800 hours to develop from scratch. It was hosted on a $4/mo shared webserver in Canada. The internet connection from the ISP in Charlotte to the factory itself was radio/wireless due to a lack of land lines, and this was around 2004.
That system once ran for 8 months supporting 24/7/365 manufacturing for 3 shifts with 40 employees without a single support ticket for $4/month in overhead cost. Sales orders often had dozens if not hundreds of SKUs and were for 10,000's of items. Hundreds of production orders could have been required for fulfilling a single order. Quality had to be tracked to the batch and to the piece as did rework. Items could be drop shipped a single item at a time, by the 1000, or by the pallet with full tracking for every piece. The total cost to the company for 8 months without a support ticket was $32 in website hosting with no monthly maintenance or retainer for the developer. When there were support tickets, they were typically related to new programming changes that needed tweaking or they turned out to be related to the wireless internet connection as it struggled with piercing a tree filled with leaves that stood in line-of-site way during peak summer months. No significant downtime was ever attributed to problems with this system over the few years it was in operation. There were data backup systems in place if/when the system was burping.
This system was shared in private with an American Citizen who was a C level executive for a US Pharmaceutical Division in Mexico. It was an unplanned meeting in San Miguel De Allende, Mexico in 2010. That executive literally almost fell out of her chair when she saw it. She indicated that just one of the 8 modules in that solution was something she had asked for in a recent IT Proposal. She had been quoted $1M for a solution but that didn't include the important half of what that single module did, because the developers indicated that what she asked for was an impossibility due to complexity.
That Executive asked the Developer where she could get a copy of the software and/or how she could get that type of work done. He told her it wasn't for sale, he told her he had no interest in working for big corporations, and he wasn't aware of anyone else with the skills to do it. That was one of at least two very viable 7 figure opportunities he ignored since 2010.
He has background in very complex ERP Systems (Enterprise Resource Planning Systems), yet he's never worked as a full-time employee in IT for any major corporation.
In the early 2000's he developed a system for a Dye House facility in Charlotte NC.. They dyed garments for Brand Name Apparel companies including Champion, Abercrombie and Fitch, and others. That facility ran 24/7/365 with 40 employees. The enterprise system he developed handled all their inventory, sales orders, production orders, quality control reporting and shipping management. It eliminated the need for full time customer service agents. It allowed national and mulit-national companies to log into his business, view their own inventory in his warehouse and create their own sales orders (purchase orders) in his system and submit for approval. Then it allowed them to log in and check production status for every production order that made up their orders. They could see exactly what machine each order was on, what was in quality control for inspection, what was on the dock waiting for shipping , what had been shipped, what was in rework and where it was in rework.
It was built with Classic ASP using a Microsoft Access Database. Very little Javascript. The developer was only in the facility for two days total during an 18 month development and roll out process. It took 1800 hours to develop from scratch. It was hosted on a $4/mo shared webserver in Canada. The internet connection from the ISP in Charlotte to the factory itself was radio/wireless due to a lack of land lines, and this was around 2004.
That system once ran for 8 months supporting 24/7/365 manufacturing for 3 shifts with 40 employees without a single support ticket for $4/month in overhead cost. Sales orders often had dozens if not hundreds of SKUs and were for 10,000's of items. Hundreds of production orders could have been required for fulfilling a single order. Quality had to be tracked to the batch and to the piece as did rework. Items could be drop shipped a single item at a time, by the 1000, or by the pallet with full tracking for every piece. The total cost to the company for 8 months without a support ticket was $32 in website hosting with no monthly maintenance or retainer for the developer. When there were support tickets, they were typically related to new programming changes that needed tweaking or they turned out to be related to the wireless internet connection as it struggled with piercing a tree filled with leaves that stood in line-of-site way during peak summer months. No significant downtime was ever attributed to problems with this system over the few years it was in operation. There were data backup systems in place if/when the system was burping.
This system was shared in private with an American Citizen who was a C level executive for a US Pharmaceutical Division in Mexico. It was an unplanned meeting in San Miguel De Allende, Mexico in 2010. That executive literally almost fell out of her chair when she saw it. She indicated that just one of the 8 modules in that solution was something she had asked for in a recent IT Proposal. She had been quoted $1M for a solution but that didn't include the important half of what that single module did, because the developers indicated that what she asked for was an impossibility due to complexity.
That Executive asked the Developer where she could get a copy of the software and/or how she could get that type of work done. He told her it wasn't for sale, he told her he had no interest in working for big corporations, and he wasn't aware of anyone else with the skills to do it. That was one of at least two very viable 7 figure opportunities he ignored since 2010.
|
NOTE: The webmaster for Obama's first presidential campaign might be able to relate to the power of the older, simpler, script based programming paradigms. Much of the success of that campaign was attributed to the creative use of a very flexible web based technology that far surpassed all others. That campaign was done in Classic ASP too.
|
You simply don't know what you are missing when it comes to the simple and powerful technology that Microsoft and Bill Gates released in the 1990's and then rapidly suppressed in the early to mid 2000's. For suppression, they had heavy assistance from the Silicon Valley Media and Bankers when they figured out how powerful it was with no residual income for the powers that be.
Text Based Login Routines and Script based Encryption and Hashing with Composite Keys and Padding
Due to very problematic Monopoly Concerns realized in the early 2010's, he developed website login routines that used encrypted and hashed passwords for multipole users stored in text files with full login and logging functionality, also in text files. Reading, writing and logging to text files for authentication is not thought of much today in web design, but maybe it should be. This system was needed to regain access to backends if/when the authentication information in an online database had been compromised. Most hardcode a backdoor into their work with or without a password or encryption. By creating an entire user name/password infrastructure for important/all users in text with proper hashing and encryption, a more interesting goal arose.
He formalized a full set of RC4 and Hash Encryption routines he had been using ad hoc, with complex public-private key infrastructures along with padding routines that can only be cracked with the source code itself. This type of information may be problematic to publish in our current political and legal environment given there are laws which govern who can provide encryption technology to who, but it most certainly is something fun to acknowledge as a need for privacy, as well as something to ponder and play with privately.
Due to very problematic Monopoly Concerns realized in the early 2010's, he developed website login routines that used encrypted and hashed passwords for multipole users stored in text files with full login and logging functionality, also in text files. Reading, writing and logging to text files for authentication is not thought of much today in web design, but maybe it should be. This system was needed to regain access to backends if/when the authentication information in an online database had been compromised. Most hardcode a backdoor into their work with or without a password or encryption. By creating an entire user name/password infrastructure for important/all users in text with proper hashing and encryption, a more interesting goal arose.
He formalized a full set of RC4 and Hash Encryption routines he had been using ad hoc, with complex public-private key infrastructures along with padding routines that can only be cracked with the source code itself. This type of information may be problematic to publish in our current political and legal environment given there are laws which govern who can provide encryption technology to who, but it most certainly is something fun to acknowledge as a need for privacy, as well as something to ponder and play with privately.