This repo contains samples of my work products generated over the last 45 years, for the purpose of enabling evaluation of the breadth and depth of projects I frequently work on.
All of these artifacts are either my own IP, or are from client engagements or jobs where the projects were terminated by the client, have been published elsewhere, or have been suitably redacted, so can be shared without conflict.
You've been granted access to this repo for a limited time, purely for your reading and evaluation, hence the artifacts should not be cloned nor shared with others, and I would appreciate if you treat this as a private communication.
It's divided into sections by artifact type.
- Anyone's Guide To Conversation Service - architectural and functional design for an integrated repository for recording and analyzing conversations and their NLP events.
- BPMEngineConcepts - high-level architectural and functional design of a workflow engine component, supporting modeling and tracking of business processes in Microsoft IT's massive supply chain system.
- Position Paper: Making Our Products Modular - very early-stage analysis of technology challenges and proposed solution faced by client rapidly growing through acquisitions, and faced with massive integration requirements.
- PDOM Functional Specification - functional specification for the Persistent Distributed Object Manager, a Smalltalk-80 package I developed and licenced to Network Intelligence, which replicated objects, transactions, queries, database management, and other computational assets, operations, and resources across geographically-distributed Smalltalk Virtual Machines.
- Modular Platform Proposal - proposal to adopt more powerful higher-order data and operation semantics in a client's event processing system, in order to radically simplify code, and improve overall stability.
- TheProblemsWithJava - notes about some of the most serious problems with the Java language architecture and implementation, and exploration of workarounds and extensions to the language and ecosystem.
- IDIOM Infrastructure Architecture Overview - slide-deck covering the design, architecture, competitive analysis, and high-level design of the IDIOM system management product suite I developed with Adaptec, to provide full system management fabric spanning their various storage, networking, and related product lines, running on 10 operating systems.
- MoneyFoundry.com Backgrounder - slide-deck proposing forming a new business providing financial services for personal and small business customers, circa 2001 (during one of the worst venture financing periods in history).
A couple of sample class definition files from EWorks, a proprietary application platform (out of about 7000 files containing 1.5 million LOC), to give a taste of my coding style, including fluent commenting, attention to readability, clear naming, strict source file structuring, and Smalltalk-style method grouping, all intended to maximize readability:
- Type.java - the base-class for the platform's type system, which spans full lifecycle, specifically exists at runtime in development, staging, and production environments, yielding massive advantages over Java's massive type erasure mistake.
- MetaEntity.java - the core metadata underlying EWorks's foundational entity architecture.
- CounteringPersistencePatents_for_SunMicrosystems - study done for Sun Microsystems to counter an IP litigation by Persistent Software, essentially invalidating Persistent's patent claims, based on my being the inventor of record for the technology (don't ask me why I didn't patent it myself).