Jenkins setup, terraform (AWS using terraform/anslble) install-guy, creating / using Linux containers on AWS "ecs - docker container service"

One triumph: "split the 20-hour test process into parallel jobs on Jenkins and let it deal with the hard stuff," which reduced HIVE tests down to 60-90 minutes of wall-clock time (Or less!) if you had enough VMs.Using ansible, jenkins, python, and eventually tree-herder, to automate build and release processes and tighten up engineering work for handoffs.Writing code to infer test methods to run, minimally parsing Java source to infer import-relationships. Split 15-20 hour unit test blocks into shards of less-than-hour each, using minimal code.

One triumph here: optimized database usage to move department from 12-20 clerks-with-clipboards managing codeline work into a system that didn't need the manual management to get through the data. Used Python, "graphviz", and Oracle Hierarchical SELECT statements to get there.Unix programmer. Perforce / Graphviz / Math nerd, working to optimize about anything I get my hands on. Like to start with the data and how it relates to the world, before climbing to the user work.

One triumph: "at every job since this role, have offered to anyone in my group to write out their install / release documentation in exchange for that person giving me time explaining the work. My notes are your documentation, I tell them, and so if time is tight, please let me help!" (They often do.)13 years of build-consulting, test-strategy consulting, and running a private corporation with 2-5 employees to do so.Substantial build consulting, Perforce administration, and training work over more than a decade.

Many triumphs: Automated HADOOP builds of the original HADOOP group at Yahoo, including post-build install / smoke test (create cluster, run test jobs) prior to release to testing group. [ All work was Jeff's programming/coding for the project with review from coworkers / test group.]Working a release/build/deploy engineer and process-guy at Yahoo on hadoop (the map/reduce framework and HDFS underneath).

Principal of a Perforce consulting company, provided training and programming services to Perforce customers/users.

Learned many good things, including "that eighth-grader with a laptop is the security violation to keep in mind. He/she has time, an internet connection, interest, and an intellect."Teaching 8th-grade Algebra, and working on teaching/presentation skills.

Learned the phrase, "just enough process," at this position.First build/release engineer for successful startup. Brought in Perforce (source management), automated testing, and repeatable / automated builds."Jeff is hands-down the best build and release engineer I've ever worked with." - quote from Kurt Sussman in the testing group.

Testing Manager of Oracle Reports group within Oracle. Hiring, Managing test engineers and getting automation going in a GUI environment.

One triumph: "using Math major proof-skills to reduce a massively ugly programming project into a table-driven small bit of code that had the 17 use cases encoded into the table. When the custer added and deleted a half-dozen use cases on-site during installation, there was no coding effort to make the requested changes, but we still billed the customer handsomely!"Work on banking software for the Dutch equivalent of the federal reserve. Designed and programmed mechanisms for signature verification of checks, including some optimizations to reduce complexity of work from quadratic time (and problematic) to a short rules-based bit of C code that ran in linear time.

Manager (promoted from within company) of group that built / tested Windows4GL, a C++ database client. Immediately changed role of group from "build and test secondary platforms" to "build all platforms consistently and move all testing (and enough personnel/machines to succeed) to testing group for consistency."This caused all platforms to release within days of each other, increased quality, decreased stress on schedules and on people. The second release-schedule had a non-primary / non-development platform going out first, because the integration group was fast enough and that was (coincidentally) the first platform that finished testing --- which surprised every developer and pleased the release folks and support folks to no end.

Build release/integration group from the ground up, to simultaneously build and handoff a complex product on 5-7 platforms at once.

C developer on C library tools, working next to C++ subgroup at the Unix Development Group. and prototyping the C++ compiler libraries in my own work.

Programmer on staff.