The first warning was a letter to the editor
Samuel Butler’s “Darwin Among the Machines,” read as a field manual for keeping an apprenticeship alive.
The first warning was a letter to the editor
Samuel Butler’s “Darwin Among the Machines” appeared in the Christchurch Press on 13 June 1863, signed Cellarius. The text used here is the version collected in Canterbury Pieces (1914).
Butler imagines machinery developing into a kingdom of its own. The unsettling part is not simply that machines might acquire power. It is that people could maintain them, improve them, and organize their lives around them until dependence feels natural. His speculative letter asks us to look at an arrangement we have helped to build.
The passage
Day by day, however, the machines are gaining ground upon us.
Samuel Butler, “Darwin Among the Machines.” This short passage is reproduced from the public-domain text; read the complete letter.
In the margin
What he got right: dependence. The sharpest question in the letter is not whether machines can think. It is whether we could still live without them. That is an operations question, and it has an answer in every organization.
What he got wrong: the remedy. Butler’s letter calls for the destruction of machines. The better remedy for a leader today is governance: rules written before dependence becomes total. Keep a means of checking the output, a person who understands the process, and an exit that exists outside the contract’s small print.
What it asks of you. List the processes in your organization that could no longer run by hand. For each, name who still knows how.
Why it matters now
Read Butler as a provocation about dependence, not a forecast about a model release. A tool can become part of the conditions under which we work long before anyone calls it infrastructure. The shortcut becomes the routine. The routine becomes the only way. Eventually, the person asked to explain the output can describe the interface but not the work.
The risk is quiet dependence: skills that atrophy, processes no one can explain, and vendors whose decisions set your choices. That is why the apprenticeship and the delegation line belong in the same conversation. A person cannot supervise a craft they have never had a chance to learn.
The practice
Pick one indispensable system. Ask what your team would do if it were unavailable tomorrow. Write down the first manual step, the person able to take it, and the knowledge the team would need to preserve. If there is no answer, you have found work for the next review.
Adapted from Nikos Acuña’s supplied manuscript. Prepared with AI assistance. Preview v1.0.
Final editorial approval pending. Sources are linked in the margin.