I'm a computer programmer with many years of experience including some back in the days when computers had their own air conditioned rooms which people would visit with decks of punched cards. A lot has happened since then and it doesn't look like things will stop changing any time in the foreseeable future. For that matter, it doesn't look like the future of computing is very foreseeable!
I have been PEABO on Delphi Forums since it was an on-line service in 1984. My permanent e-mail address is peabo (at) peabo.com (spammers unwelcome). You may have reached this Web page via http://people.delphiforums.com/peabo or by automatic forwarding from http://www.peabo.com (link here, not there). You can also find me on NLZ, which is an offspring of the late BIX on-line service.
Here's a current copy of my resume in as a Web page, in MS Word format, and in PDF format for downloading. The MS Word document can be read by the open source program OpenOffice.org Writer.
Most of the programming I do is in the C or C++ programming language. I can program C in my sleep, but when programming C++ I always take care to be alert! In the old days I used to program in assembly language, and in some cases used console switches to enter hand-assembled binary code.
I am a member of the Scheme Boston user group, which is on summer vacation but which will start meeting again this fall at Northeastern University (one of the homes of PLT Scheme, a family of implementations of the Scheme programming language). The Web site Schemers.org is another great place to find Scheme resources. Although I haven't written any Scheme programs for hire, here's a moderately complex program I wrote to solve a puzzle.
My primary focus is on Linux right now, though I also use Macintosh computers every day and have programmed them in the past. The MS Windows machines I have used were mainly owned by the companies I have worked for, but over the years I have done a lot with them. I have a dual-booted Linux/Windows laptop and can run Virtual PC on my Mac.
I have written several HTML pretty-printers which attempt to diagnose HTML coding errors in a sensible way. Here's the output of one which diagnoses a systematic error (using LI in a table cell to get bullet points even though there is no encompassing UL) and a totally erroneous use of FRAMESET. (Out of respect for the guilty, I have not identified the original page.) This is an experimental program which needs a lot more work.
Here's a link to a compact chart of Web Safe colors.
Last updated 2003-09-06.