SUMMARY:

• Seasoned, hands - on Software Engineer with extensive and varied experience, most recently in configuration management, release engineering, and build architecture and automation. Highly skilled in the design, development, and documentation of software tools and applications on numerous hardware and software platforms and in developers in their use. Quick in learning and applying new technologies.

TECHNICAL SKILLS:

Technology and Tools: Fluent in Unix shell, Perl, C, make, Tcl, Tk, Expect, Fortran, and PL/I; conversant in C++, java, COBOL, and IBM JCL and file utilities Source code management systems: ClearCase (both Base and UCM; peripherally MultiSite), BitKeeper, and Confidential (administrator and skilled user); ODE, SCCS, and RCS OS experience on Solaris (both Sun and PC hardware), Digital UNIX, Linux(MKS) - (RedHat, SuSE, Slackware, Debian, and others), IBM/360, SunOS4, Windows (95, 98, NT, and 2000), HP-UX, AIX, and IRIX5; acquainted with VMware Hardware experience on IBM, Amdahl, Sun, HP, Confidential, SGI, and various PCs.

PROFESSIONAL EXPERIENCE:

Consulting Release Engineer

Confidential, Marlborough, Mass

Responsibilities:

• Imported and versioned a directory of build/regression scripts to a new ClearCase VOB
• Converted a work group to use “bash” rather than “csh”, coding a "tcsh2bash" script, and providing template .profile and .bashrc files for general use; applied the conversion techniques to a large suite of
• “csh” test and regression scripts, generalizing them in the process
• Implemented interoperability for two geographically separated sites (originally very differently structured)
• Reconfigured two LSF installations for speed, efficiency, and interoperability
• Created tools to facilitate rebalancing (extremely full) crontabs controlling build and regression scripts

Consulting Release Engineer

Confidential, Lowell, Mass

Responsibilities:

• Installed RedHat Enterprise Linux 4.4 on 70+ machines at 3 different locations, to support ClearCase
• Merged six divergent build processes into a single, more efficient, thoroughly documented process
• Produced HTML/CGI interfaces for remote interaction with local programs
• Produced a state-of-the-art set of triggers, a daemon, and other scripts for controlling release streams in
• ClearCase UCMand MultiSite
• Dealt with Electric Cloud installation and provided interface tools for emake usage.
• Produced and maintained techniques for kitting and installing required tools at multiple sites world-wide.
• Developed a cross- system tailored to the Confidential project, dealing with makefile macros and inclusions, and C and/or C++ entrypoints, subroutine s, and global definitions and s

Consulting Configuration Management Engineer

Confidential, Framingham, Mass

Responsibilities:

• Evaluated the advisability of a switch from Confidential to Confidential for a legacy product line; advised against it because of low return on investment and relatively high risk of porting
• Created, documented, and supported an extension for Confidential that enforces consistent branching and merging protocols and provides changeset capacity; also deployed and trained at a subcontractor site

Consulting Release Engineer

Confidential, Billerica, Mass

Responsibilities:

• Updated "portage" build environment to provide reproducible bases for many tools used in building Nortel's dolphin project
• Provided a version of perl 5.8.4 cross-compiled on Intel Linux to run on mipsel
• Automated the method of automatically generating code for "flash" images and related software
• Provided a cross- system for the dolphin project, permitting calling-tree analysis of a complicated body of code
• Updated the kitting program for improved clarity, efficiency, and speed

Staff Software Engineer

Confidential, Boston, Mass

Responsibilities:

• Configuration Management support and in BitKeeper and Confidential
• Maintenance, enhancement, and automation of a multi-distribution and multi-kernel build system for Starcore and for Confidential 's versions of MPICH and DAPL
• Post-build labelling of executable binaries and libraries
• Kitting and installation design, implementation, and documentation, both with and without use of Linux's "rpm" technology

Principal Software Engineer

Confidential, Bedford, Mass

Responsibilities:

• Release Engineering for XIS (an XML database product) and build automation for XIS and the JMTL, PSE, and RTEE products
• Designed and implemented “build numbering”: a multi-platform way of embedding platform- and build-specific labeling into executables and shared objects, post-build.
• Designed, implemented, and applied a new multi-platform auto-archiver for packaging and installation of software, which cut package size by a factor of 6 and packaging time by a factor of 4.6.
• Enhanced, maintained, and administered Confidential Corporation’s “snapshot system”, a home-grown wrapper around ClearCase used for sophisticated configuration management; also ported it to Windows using client/server technology, along with ClearCase administration and consulting

Principal Software Engineer

Confidential, Bedford, Mass

Responsibilities:

• Improved the build system environment by designing and implementing tools and/or ClearCase triggers to: report build schedules and to generate and report build status; kill a build that continues in the background for too long; lock projects against improper promotions of files, queueing the promotions until the lock is released; record all promotions on a per-project, per-user basis, conserving timestamp and ClearCase version; install constructed files in an export VOB, with periodic safe cleaning of that VOB; determine which build components need reconstruction;substitute for rsh in Unix/WinNT communications where standard techniques were unsafe to use
• Unified multiple versions of the “same” build scripts across several projects into single versions, differentiating between projects by means of a descriptor file
• Collaborated with a colleague in constructing a small, self-contained, heterogeneous enclave of machines to verify the “Y2K” correctness of Confidential ’s build techniques and tools before Y2K.

Principal Software Engineer

Confidential, Chelmsford, Mass

Responsibilities:

• Designed, implemented, and documented an entirely new build system architecture and toolset for Confidential, after first collecting requirements from the development community. Applied to two mission-critical ClearCase views, it supported heterogeneous distributed builds, completing a clean build three to four times faster than the old techniques. It also cleanly separated control flow from definitions of makefile macros and rules, kept source and target trees disjoint from one another, facilitating building for different targets on different machines, and was completely documented.
• Constructed a cross- system tailored to Mercury's specific needs, including the necessity of dealing with object files from 12 different platforms (or 19, depending on how you count), rationalized an Expect test-automation tool, and designed and implemented a perl package for test automation.

Software Principal Engineer

Confidential, Nashua, New Hampshire

Responsibilities:

• Automated the installation and running of a large number of tests and test suites for Confidential, both in collaboration with another developer and by myself, including developing and presenting a four-hour course covering the elements first of Tcl, then Expect, and finally Batch Automation itself.
• Provided Confidential Unix developers for the first time the ability to do incremental builds before making code submissions, permitting errors with global impact to be caught much earlier.

Senior Software Engineer

Confidential, Bedford, Mass

Responsibilities:

• Initial design and implementation of the Confidential graphics generation system; Confidential, a communications package between two of Computervision's proprietary operating systems; a tool for secured assembly of configurable ~80-Mbyte Confidential executables at programming- customer sites; crash recovery module for Confidential ; geometric database interface packages for solid modeling; parametric execute files in Confidential ; list-processing environment; command processor; language-configurable message system; asynchronous device driver for workstations
• Computer Aided Software Engineering: High-speed, multi-platform cross- system in several varieties of UNIX; self-configuring, platform-independent makefile-generation tools; maintenance of and enhancements to a home-grown configuration management system; tools for modularizing Confidential by disentangling “spaghetti” structure in the body of routines making up Confidential ; development of software for a dynamic-loading scheme for independent invocation of the ~1400 independent modules identified by those tools; software metrics tools; argument-list verification tool
• ‘Care and feeding’ of VLPs (“Very Large Programs”): Improved schema for programmers’ assembly of private versions of Confidential ; tool for patching existing versions of Confidential at customer sites with bug fixes; design and maintenance of memory layout and assignments for Confidential 4X; enhancements to a proprietary OS’s LOAD command and the associated overlay manager