soft·ware gen·er·al con·trac·tor/ˈsôf(t)ˌwer ˈjen(ə)rəl kənˈtraktər/ · n. · coined usage
1.An operator engaged to plan, build, and own a software system
in its entirety — as a general contractor oversees a construction
site: coordinating discipline, sequence, and structure toward a
finished result. Unlike a subcontractor, who executes one trade, the
software general contractor holds the blueprint and bears
accountability for the whole.
2.(emerging) One who applies judgment, architecture,
and craft to software in an era when writing code has become what
hammering a nail once was — a mechanical act, largely automated. The
general contractor's value was never in the hammer.
From general contractor (construction trades, 19th c.)
+ software (computing, mid-20th c.). Coined to
describe the application of the general contractor model to the digital
built environment, wherein systems of code — like systems of structure
— require a single party accountable for the whole.
I build and ship software. New products, legacy systems, technical
leadership, so on and so forth. I come in, form it up, and make the
change.
How I work
Fractional CTO
Part-time technical leadership at the executive level. Own the
engineering function and drive strategy without a full-time hire.
Project
Fixed scope, fixed outcome. We agree on what gets built and I own
the delivery.
Advisory
Hourly consultation. Architecture, technical direction, or a sharp
outside perspective.
Retainer
A set monthly engagement. Available on an ongoing basis for whatever
comes up.
Contracting
Embedded hourly work. I join your team and build alongside you.
Forward Deployed Engineer
Stationed within your org to ship. Own critical path and operate with full autonomy.