Cool stuff involving file/object services protocols and managing unstructured data.

Quaddra is a stealth-phase startup working on the problem of stale or improperly placed unstructured data and how to analyze, categorize, understand, and better store it to meet the economic and policy needs of the organization. We use high-speed file scanning and analytics to help this decision process, with scale-out and up a key part of the application. We target distributed multi-petabyte-scale storage deployments with many servers/filers and billions of files, collecting metadata information to use in analytics. Development work is primarily Python, with some C development in Python extensions and other utilities.

Customer Firmware engineer (Enterprise) - Role was to represent top-tier Enterprise OEM customers from within the WD organization. I was the firmware point of contact for the OEM (both from within and without); I had to understand their drive functionality specification in depth; how it differs from the T10/T13 standards, and how WD had to change or augment their firmware to meet the requirements. I disseminated that knowledge to both the customer and the firmware team within WD. Involved on a day-to-day basis with the firmware team in architecting, designing, and implementing the firmware to meet the customer requirements. Involved on a day-to-day basis with the customer to understand both the letter and intent of their requirements and communicate to them how (and when) the requirements will be met. Successful completion of my tasks would enable sales to the OEM of 10s of thousands to multi-hundred thousands of their customized drives.

Software Architect in the StorageWorks Division. Responsible for the architecture and product plans for the X9000 series of Enterprise NAS systems. After PolyServe was acquired by HP in May of 2007, I continued in my role as Architect responsible for all phases of design and implementation planning for File Serving add-on for base cluster product (X9000 series). Additionally, I served as Architect for Windows-based X5000 series of file serving products. I was Enterprise NAS group Microsoft Technical Liaison. Required deep understanding of CIFS/SMB and NFSv3/v4 file services protocols, file systems performance and design as it impacted remote file access (and system performance during access), and a thorough knowledge of Windows and Linux.

Architect responsible for all phases of design and implementation planning for File Serving add-on for base cluster product. Part of long-term planning team, laying out strategic product roadmap. Position involved solid understanding of CIFS and NFS file services protocols, their systems-wide effects on Linux and Windows platforms, and how best to use them with our file system. Responsible for technical aspects of PolyServe-Microsoft relationship, specifically technical liaison with the Windows core and storage teams.Senior Software EngineerSenior member of team of engineers implementing high availability file serving solutions (NFS, CIFS) based on a highly available cluster file system for Windows Server (2000, 2003, Longhorn) and Linux (SLES, RHEL). Position involved Linux and Windows kernel development of highly reliable / highly available NFS and CIFS-based file serving and file system software. Senior member of team of engineers implementing a cluster file system for Windows. File system features include distributed locking, multi-node cache coherency, journaling, and compatibility with many of the advanced features of NTFS.

As a Technical Evangelist in the Developer Relations Group, I was responsible for connecting application developers world-wide with new technology being developed for Windows operating systems and helping them integrate it into their products. This took many forms:  - consulting with software developers on a design and implementation level, with a strong focus on meeting release schedules (theirs and Microsoft’s). During this period, the developer relations group met with literally thousands of development teams to help them with their development of WIn32 applications for Windows NT. - highly technical presentations (Windows NT kernel development, Exchange server extensions development, others) to 5 to 5000-person developer groups; driving force for hosting the now-legendary (and only) File Systems Conference (‘94); writing sample code in a variety of languages.- contributing to industry working groups, usually designing new programming interfaces or protocols (member of Windows Sockets Interface working group for versions one and two).- managing the Microsoft Porting Lab and its staff of 5 developers, where external developers are invited to interact with Microsoft developers to ensure they implement their applications effectively; organizing and hosting technical events for the external developers and coordinated the Microsoft presence at the lab. Additionally, I served as the “last, best resort” technical resource for resolution of Windows kernel issues at the lab. - “Whatever it takes” ad hoc, self-initiated activities as needed to promote and ensure the success of the OS through the adoption of its new technology into ISP’s applications. My primary evangelism responsibility areas were Windows Internals, Windows File Systems, Device Drivers, Networking, Microsoft Exchange.The Windows Developer Evangelism team of which I was a part has been cited as being a prime influence on the success of Windows NT in the marketplace.

Software Design Engineer on Windows NT team during the initial (pre-Windows NT 3.1 release) development of the operating system. Implemented NetBEUI and XNS network transports for Windows NT. Designed and implemented TDI (Transport Driver Interface) for Windows NT.

Lead Engineer for LanMan-compatible file server product for VAX / VMS.

(DECWest) Networking Engineer developing transport / driver for object-oriented OS (Mica) running on hardware that later was revamped and became the Alpha. Project cancelled June ‘88 after four years of development.

Principal engineer for design phase of power management system for large eastern electrical utility. This project was the first networked power management system built by the company; based on DECnet and VAXen, it was a significant departure from power management systems of the day. My specific technical contributions were in the design and implementation of the data network between the 6 control centers, and in the use of off-the-shelf system components to implement the functionality in the system. The correct implementation of this system enabled the power company to make many millions of dollars a year through managing power flow through the system.

I was a software support specialist, supporting RSX-11M, VMS in the Tucson, AZ region, and DECNet in the Los Alamos, NM region.

Systems Manager/programmer for PDP-11s and VAXen at Esperanza open pit mine. Numerical methods/computer methods support for Mining Engineering staff.