I build Wordpress sites and custom CMS and related web apps. I migrate databases, integrate rich media content and open source applications and manage R&D projects. I research vendors and technologies, helping clients find the best IT solutions for them.
I get asked a lot what tool I use to create websites. I have been writing my own tools since Day Two. When I first got into HTML, I tried Dreamweaver and quickly learned that the GUI wouldn’t let me do what I knew was possible and I wound up coding in their "code viewer". I immediately abandoned Dreamweaver and started hand-coding of HTML. I learned how to make fast pages that are compatible across browsers, easy to modify and keep the browser out of "quirks mode."
Then I wrote Perl and PHP scripts and templates to automate the process. I wrote scripts that wrote scripts and data-driven script generators. I like writing reusable, productivity-enhancers, because I see a gap in real-world operations and one-size-fits-all solutions.
I am currently building a semi-serverless, highly data-driven applications for end-to-end data management, auditing, filtering, formatting and publishing. The data is managed in structured data files so it is fast, flexible and secure. I have delivered REST interfaces to manage the time needed to load the page. Content updates are so fast, you can’ see them in the debugger. I have had to add animations so users can see the change.
Typical clients for this are companies with large product inventories with lots of parametric data. I have built several different kinds of parametric and related search tools to meet their needs. Yes, they are responsive.
Migrate national retailer with thousands of products from a legacy cart to Big Commerce.
I designed the sales brochure pages and internal portal for a retail trading information site.
Create online multimedia investor presentation. Powerpoint has limitations that make it less desirable for fast, rich online presentations. We wanted to integrate various media types, Flash, voice-overs and background music and by mixing Flash, frames and DHTML, I created a presentation that was modular, easy to modify and upgrade incrementally.
Web-based in-house sales ticket tracker that integrated three business units, increased transparency and enforced policies that cut costs and increased revenue. The solution was a Perl/CGI + DBM web application because the customer has a very heterogeneous server environment. This Perl program cost far less than customizing the accounting system.
Imagine putting your business into a World War I biplane every morning and flying it over the Grand Canyon. Well, that it what this business was doing with their mission-critical, proprietary database application. The hardware had been old enough to vote since the early 90’s. The companies that had built the various components had long since been bought and dismantled, and the software was hard-coded to it. Libraries and drivers had been deprecated decades ago. And of course, the entire ball of mud was thoroughly undocumented and unintentionally booby-trapped. Staff operations were not only undocumented, but laden with superstitions and magic keystroke combos that were handed down from the early times. No one single person fully understood what the app did, how it worked or whether it was working correctly. But because the application performed a mission critical, core business function, upgrading that software and hardware was like changing the piston rings while the motor was running. And yet me and my colleague did it. Today, that same app runs on a state-of-the-art firebreathing monster. The business unit has never gone down and a plan is in place to migrate the app going forward.
This desktop application performs a significant amount of data conditioning, file I/O, and printing – all of which went in a headless multi-threaded DLL. The data reporting model allows the client to make asynchronous queries and redirect the results individually. The raw data cache provides a data abstraction layer so the data conditioning code does not know whether the data came from the port or a file. The post-conditioning data cache allows the GUI to query without re-processing (which would be perceptible to the User). Finally, the GUI exe has a representational data cache because the User chooses a particular view of the data. This made the GUI client a little fatter, but it is GUI logic. The container class allows the client application to easily describe new representations, not just the ones in the specification.
"KeyJack" is a keyboard utility that redirects function keys to the console. It was developed for a terminal emulation project that needed to send keyboard commands over a telnet session.
I was the technical lead on this ISAPI webserver DLL and browser client. It was a multi-threaded, multi-tenant polling app that delivered multiple screens or views of information about a virtual call center. The technology was Windows API / C++, XML, COM and DHTML.
I re-wrote the front end of this Windows fat client. McAfee had acquired it from Cybermedia around 1998. It had 90+ DLLs, an unlicensed encryption library (that needed to be replaced), and some wild coding. I remember one comment around a particularly nasty bit of code that said simply: "this code is cursed. Don’t even think about changing it." In another spot, it had a
sleep() instruction with the comment, "Make the User think we’re doing something." I believe the state of California sued Cybermedia for consumer fraud.
I wrote several applications for McAfee, Network Associates and Helix Software for the Windows desktop in the ninties.