shane's blog

Three Threads from Onboarding a CNC

· machining

TL;DR: A Makera Z1 desktop CNC arrives soon. Asking why feeds and speeds work the way they do led somewhere I didn't expect — through fracture mechanics, into earthquake physics, and out the other side at self-organized criticality. Two adjacent threads came out of the same conversation: how community knowledge stacks actually work in an era of cheap AI synthesis, and the case for committing decades to a craft that will outlast every framework I currently use professionally.

Three parts, written to stand alone. Pick whichever interests you.

1. Chipquake

From chipload to Griffith's criterion to the same equations that govern earthquakes.

The unsatisfying answer

The conventional onboarding path for a new CNC user is "learn feeds and speeds from a chart." The chart is fine. It's also unsatisfying, because it tells you what numbers to use without telling you why those numbers are what they are. Coming from domains like software and AI where the habit is to reason from mechanism rather than pattern, I wanted to apply the same habit here. The starting question was narrow: what is chipload, and why does it appear in every feeds-and-speeds discussion?

Chipload as the core variable

Chipload is the thickness of material each cutting edge removes per revolution. It's the physical thing being tuned. Everything else — spindle RPM, feed rate, flute count — is a knob that controls it.

chipload = feed_rate / (RPM × number_of_flutes)

Each tool geometry and material combination has a target chipload range, published on manufacturer datasheets. For a 1/8" 2-flute carbide endmill in soft wood, roughly 0.05–0.10mm per tooth. In aluminum with the same bit, more like 0.025–0.05mm per tooth.

Why it's a balance, not a maximum

Three regimes on the same axis, with two failure modes flanking a working window.

Chipload too low. The cutting edge rubs instead of biting. Friction instead of shear. Heat builds up in the tool because the chip isn't carrying it away — chips are the primary heat sink in machining, which is the part most counterintuitive coming from 3D printing. The bit dulls fast. In wood you smell burning. In aluminum the chip welds to the flute and the bit becomes a smooth cylinder that grinds.

Chipload too high. Per-tooth force exceeds what the tool neck can withstand. Carbide doesn't bend — it shatters. Deflection comes first as a warning (audible chatter, washboard surface finish), then catastrophic fracture.

Just right. A sharp knife through room-temperature butter. The edge is shearing, not impacting. The chip curls off cleanly, carrying heat with it. Force is steady and modest because shearing is energetically cheap when the geometry is right.

The torque balance, made explicit

Four coupled quantities determine cutting force: RPM, feed rate, depth of cut (axial engagement), and width of cut (radial engagement). Cutting force scales roughly with DOC × WOC × chipload × material_specific_energy. Required spindle torque scales with that force times the tool radius. Required power is torque times RPM. The Z1 has a 150W spindle. That's the hard ceiling. Increase any of the four inputs and the others have to compensate, or something gives — usually the bit, occasionally the workpiece, sometimes the spindle stalls.

This is where the conversation shifted from machining into broader physics. The interesting question turned out to be: why does fracture happen the way it does, and what else fails on the same physics?

The hammering

A 2-flute endmill at 13,000 RPM has a tooth engaging the workpiece about 433 times per second. Each engagement is a sub-millisecond impact-and-shear event. The bit doesn't experience cutting force as a steady push — it experiences a 433Hz hammering. It is, mechanically, a small-diameter cantilever beam taking rapid lateral hammer blows.

Carbide tooling is mostly tungsten carbide grains (hexagonal lattice of W and C, hardness around 9 Mohs) bound together by metallic cobalt at about 6–12% by weight. The composite architecture is what makes the tool useful: pure WC would be too brittle to survive first contact, pure cobalt too soft to cut anything. Cobalt provides toughness; WC provides hardness; the sintered combination is what desktop CNC users buy.

But carbide's failure mode under hammering is brittle. The atomic bonding in WC doesn't permit easy dislocation motion at room temperature. Stress builds up locally at flaws — grain boundaries, microvoids from sintering, scratches from grinding — until a crack nucleates and propagates through the material at near the speed of sound. The cobalt binder helps by blunting cracks, which is why you get chatter (bulk elastic deflection) as a warning before catastrophic fracture. But once a critical threshold is crossed, the bit breaks. Usually at the neck, the thinnest cross-section just above the flutes — the highest-stress location in cantilever bending.

The chipquake

The fracture mechanics conversation, once started, doesn't stop at the bit.

A. A. Griffith's 1921 paper on glass fracture established the energy criterion that governs catastrophic crack propagation: a crack grows when the elastic strain energy released by extending it exceeds the surface energy required to create the new crack faces. Below that threshold, stable. Above it, runaway. This is the foundation of linear elastic fracture mechanics (LEFM) and it applies to any brittle material under stress.

It applies, specifically, to faults in the Earth's crust. Earthquakes don't initiate from uniform stress in pristine rock — they nucleate at existing fault surfaces and weak zones, which concentrate stress by a factor proportional to the square root of the flaw length over the radius of curvature at the tip. Same equation as the carbide bit. Different units in the constants, identical structure.

The parallels run deeper than the initiation criterion:

The scaling is wild to think about. Hooke's law elasticity, Griffith energy balance, Mohr-Coulomb failure criteria — the constitutive parameters change across maybe fifteen orders of magnitude in length scale, but the equations don't. So "chipquake" is closer to a real category than a joke. Same dynamics. Different rock.

One layer up: self-organized criticality

The pattern generalizes once more. Earthquake magnitude-frequency distributions follow the Gutenberg-Richter law: roughly ten times as many magnitude-4 earthquakes as magnitude-5, ten times as many 5s as 6s. This is a power law — no characteristic scale, the system looks statistically the same at every magnitude until you hit the size of the fault system itself. Acoustic emission events in stressed materials follow the same power law. Same exponent, roughly.

This is not a coincidence. It's the signature of self-organized criticality (SOC), a framework Per Bak and collaborators introduced in 1987 to describe systems that naturally evolve to a state poised between stable and runaway. Sandpiles, forest fires, neural avalanches, financial markets, earthquake faults. All show the same long-quiet-then-large-event statistics. All sit at the same edge.

Why this matters past machining

The framework eats whatever you point it at. Cascading failures in complex systems — power grids, supply chains, ecosystems, large model deployments, geopolitical alliances — show similar power-law statistics and the same long-quiet-then-large-event pattern. The takeaway worth internalizing is unsentimental: self-organized critical systems are stable on the average and unstable on the tail. That is exactly the regime where security concerns live, both in machining and in everything else.

The concrete implication: be suspicious of any system claiming "stability" based only on the absence of recent large failures. The absence is consistent with both genuine robustness and with sitting one tooth-engagement away from a cascading rupture. Distinguishing the two requires looking at the smaller events — the microseismicity, the chatter, the b-value of the failure distribution — not at the headline.

This is geopolitics right now. It's also AI deployment right now. The fact that the same observation came out of asking why a 3mm endmill snaps is the kind of thing that makes me want to spend more time at a CNC.

References for this part

2. The Substrate Boundary

Why "no synthetic posts" is structural, not aesthetic, and what that means for community knowledge.

Context

Adjacent question that came up while planning the CNC: how does a new user actually learn this machine, given that no third-party book exists and Makera's official docs are still being written? The Z1 just shipped. The community of buyers is real (over 6,000 Kickstarter backers) but unorganized. What's the right shape for the knowledge stack that will form around this tool?

The conventional layered stack

The standard answer for any technical community is some combination of: an official wiki for canonical reference, a real-time chat (Discord, IRC) for live troubleshooting, a forum or subreddit for asynchronous Q&A, and ideally a single-author guide or book for the conceptual ladder a new user climbs once before they touch any of the above.

Each layer optimizes for a different need. Wikis for currency and coverage. Chat for immediacy. Forums for searchable history with quality voting. Books for sequenced narrative. They compose, rather than compete.

The Reddit-actually-does-most-of-this observation

The cleaner observation, once you stop treating these as separate platforms, is that a well-moderated subreddit checks most of the boxes by itself. Subreddits have wikis. They have stickied "start here" posts that double as canonical entry points. They have flair as taxonomy, voting as quality signal, search-indexed by Google. The activation energy to contribute a photo of a busted endmill and ask "what happened?" is roughly zero, which is exactly why subreddits accumulate practical knowledge faster than any other community format.

The remaining gap — sequenced learning paths and coherent voice — can be filled by a stickied wiki page or a linked external guide. The architecture isn't really four separate layers. It's a substrate (real users solving real problems with real machines) and a thin organization layer on top.

The synthesis layer

The architecture is being restructured by tooling. Reddit Answers and similar features point at a near-future capability that's already technically tractable: an LLM with retrieval over a community's full corpus continuously synthesizes wiki pages from accumulated discussion. Every new thread refines the reference. The wiki stops being a hand-curated artifact lagging behind the discussion and becomes a synthesis layer running on top of it in near-real-time.

The implication for documentation work: synthesis tools eat the procedural layer. How-tos, parameter references, troubleshooting trees — these are exactly the categories that fill most maker wikis today, and they're exactly the categories where retrieval-plus-synthesis is competitive with hand-curation now and will probably exceed it shortly.

What synthesis from a corpus cannot produce is content that isn't in the corpus. Cross-domain explanatory work — the kind of move that connects an immediate practical problem to the underlying physics that governs unrelated domains — can't be retrieved from a Z1 troubleshooting forum, because the people posting troubleshooting questions have no reason to write about the foundations. Connective authorship has to come from somewhere outside the community's own substrate. That's the remaining defensible writing work.

The load-bearing rule

Here's where the architecture turns sharp. The whole stack — substrate, organization layer, synthesis layer — is only valuable because the substrate is real. Strip out the substrate, and the rest collapses into noise referencing noise.

This makes "no synthetic posts" a structural rule rather than an aesthetic preference. The moment synthetic posts enter the corpus, the upper-layer synthesis becomes unreliable in a specific and nasty way: it starts confirming itself. A model writes a plausible-sounding answer. Someone posts it. Future synthesis retrieves it as evidence. The signal floor sinks. The community can no longer distinguish "this worked for me on real aluminum" from "this looks like it would work, written by a system that has never touched aluminum."

The defense isn't technical. It's moderation grounded in substrate. Show the part. Show the setup. Show the failure. Photo-or-it-didn't-happen as an epistemic norm. Real-world proof as the entry condition for participation. That's what keeps the corpus clean enough that synthesis on top of it remains worth running.

Communities that get this right (r/AskHistorians is the canonical example, with brutal sourcing requirements and aggressive moderation) maintain corpus quality through friction. Communities that don't end up with wikis full of plausible-sounding nonsense, regardless of whether the nonsense was generated by humans or by models. The failure mode looks identical from the outside.

The same pattern, in three other places

Once the structural argument is visible, it generalizes uncomfortably:

In each case, the failure pattern is identical: synthesis layers running on a corpus that has lost contact with its substrate. The fix is identical too: ruthless moderation at the substrate boundary.

The takeaway

This is the only sustainable design pattern I can see for technical knowledge communities in an era of cheap synthesis. Hard boundaries at the substrate layer; whatever you want above it. The implementation details of the organization layer matter much less than the discipline at the substrate-organization boundary — the moderation policies that decide what gets to count as a real contribution about a real cut on real material.

For the Z1 specifically: if a subreddit forms (or already has), the most valuable single thing the moderators can do is enforce substrate evidence as a posting requirement. Photo of the part, photo of the setup, specific machine and material, ideally video. The subreddit's long-term value is set by that policy on day one. Everything downstream — the wiki that gets synthesized from posts, the AI tools built on top, the eventual third-party documentation — depends on it.

3. The Long Bet

Why subtractive metalwork is a defensible thing to commit to for life.

The claim

The idea of doing CNC machining for the rest of my life has real appeal. Not as a profession — that's a separate question — but as a sustained practice, the way some people commit to woodworking or cooking or keeping bees. This third thread is the case for that kind of commitment, and the structural arguments turn out to be more interesting than the surface intuition that "we'll always need machined parts."

The thermodynamic argument

Subtractive machining on metal is, in the most literal sense, a controlled energy transfer that produces a part with specific geometric and material properties no other process produces equivalently. Casting introduces porosity. Forging is shape-limited. 3D-printed metal has anisotropy and surface finish issues that matter for any application with cyclic loading or precise tolerances. Machining a billet remains the only process that gives fine-grained control over dimensional accuracy, surface finish, and material homogeneity simultaneously.

That's not a fashion. That's a physics floor. The floor is set by what atoms do under stress, and atoms are not getting updated. Aluminum will still be 2.7 g/cc with the same yield strength in fifty years. The endmills will still need to remove material in chips that fit within carbide's fracture toughness budget. The fundamental problem the practice teaches you to solve is invariant under any plausible technological change.

The capability-floor argument

This is the part that hits hardest when you sit with it. Nearly every other technology depends on machined metal somewhere in its production chain. The semiconductor fab tools that print chips in laptops were machined. The injection molds that produce every plastic part in the room were machined. The tooling that makes the tooling that makes everything is machined metal.

This is the actual base layer of physical civilization — a small, slow, deeply unsexy industry that everything else stands on. When people talk about reshoring, supply chain resilience, or the fragility of advanced manufacturing, what they're talking about underneath the rhetoric is machinist hours and machine-tool capacity. The U.S. has a documented and worsening shortage of skilled machinists. The median age of a working machinist is north of 50 in most surveys. The trade is being abandoned by the kids who would otherwise enter it because it's been culturally coded as "just a job" rather than the foundational craft it is.

Anyone who learns it competently in the next decade is going to find the labor market unusually friendly, regardless of what else is happening in the broader economy. That's not the reason I'm doing it. But it's a noteworthy property of the thing.

The cognitive-anchor argument

This is the actual reason, named directly.

A lot of technical work sits in domains where the substrate is unstable. AI security, where the threat model changes monthly. Software development, where today's framework is tomorrow's legacy. AI research, where last year's state of the art is now a baseline. The pace of revision in those domains isn't going to slow down. You can be excellent at all of it and still feel a particular kind of exhaustion that comes from never being able to declare anything finished, because the thing you finished gets re-relevant or de-relevant in eighteen months.

A milled aluminum part is finished. The chip on the floor was once part of the block; now it isn't; the part is the shape it is and will remain that shape. The geometry is committed to physics. No firmware update revises it. No paradigm shift makes it obsolete. The skill required to produce it transfers cleanly across decades — a 1970s machinist could walk into any modern shop and the conceptual conversation would be intelligible to both of them, even if the controls and software differ.

That's a genuinely rare property in modern technical skills. Most domains where this is true (woodworking, blacksmithing, masonry, certain kinds of cooking) have been pushed into hobby/craft framing because they've been disconnected from the leading edge of production. CNC machining is the unusual case where the same skill that grounds you cognitively is also still on the leading edge of how things actually get built. The grounding practice and the relevant trade are the same activity.

The pattern

This connects to a wider pattern of choices — preferring physical printed editions of books I care about, treating certain commitments as permanent rather than provisional. The unifying thread is deliberate maintenance of contact with the non-revisable. Things that exist independently of their current digital representation. The CNC fits cleanly into that.

The caveat

The grounding works as long as I stay in contact with the substrate. The failure mode for technically-inclined people who get into anything physical is the same: spending more time optimizing the workflow than doing the work. Researching the perfect endmill instead of cutting. Building the perfect fixture system instead of making parts. Watching CNC YouTube instead of watching my own machine.

The grounding effect comes from the cuts, not the planning. The chip on the floor is the proof.

The starter setup

The starter setup I have in mind: a stack of identical aluminum circles, an enclosed desktop machine, and an open-ended stretch of time. The plan is "do whatever" — cut pockets, slots, holes, grooves into the circles for no specific reason for several months.

This sounds undisciplined. It's actually structurally correct for the phase. Identical stock removes a variable: every cut, the only thing that changed between this attempt and the last is something I did. That clean signal is what builds calibration in the ear, eye, and hands. The motor-skill literature has a name for this period — "deliberate play" — and the finding is consistent: experts in physical skills almost always have a phase of unstructured exploration with the substrate before they have a phase of deliberate practice toward specific goals. The exploration builds the perceptual model that makes later practice transfer. Skip it, and structured practice produces narrow technical competence without flexibility.

Make junk. Make a lot of it. Look at the chip pile at the end of each session before sweeping it up — the pile from a clean cutting session looks meaningfully different from a struggling one. Color, size distribution, shape consistency. Burnt-blue chips, dust instead of curls, long stringy strands instead of clean commas; these are the substrate telling you what the session was. Most machinists develop chip-reading as an unconscious skill over years. Looking deliberately for the first few months shortcuts a lot of that.

The bet, in one line

Commit to the activity that produces a chip on the floor. Everything else in life can stay as fluid as it wants.