Article - April 29, 2016
Yesterday marked the final day of the Guild Apprenticeship with Guild member David Nichols. After a full month in the shop together, today was my first real “office day” in weeks, which gave me some quiet time to reflect on the experience, what went right, what went wrong, and what actually mattered.
David was a great sport from day one. He jumped in wherever needed, handled repetitive tasks without complaint, and proved to be a thoughtful, capable helper throughout the build. He even played an active role in refining the design of the Barrister’s Bookcase, collaborating with me on joinery choices and finishing details. That kind of back-and-forth is always energizing, and it’s one of the things I enjoy most about working alongside another woodworker.
But like any real project, especially one built under real constraints, it didn’t all go smoothly.
In the first week, we hit a wall.
We were building the side frames for the Barrister’s Bookcase and, after a quick dry assembly, something immediately felt off. Nearly every rail-and-stile joint showed a discrepancy. The parts weren’t a consistent thickness. One corner of each board was noticeably thinner than the opposite corner.
Some mistakes can be hidden, adjusted, or worked around. This wasn’t one of them.
There was no clever fix, no subtle tweak that would make it right. We were three days into the build, and the only honest solution was a complete mulligan. Every frame part had to be remade from scratch. That’s a gut punch under any circumstances, and even more so when you’re the apprentice watching several days of work get tossed aside.
Once we stepped back and retraced our steps, the cause became clear. During finish sanding, David was using my random orbit sander on the narrow frame parts. While this wasn’t his first time using a sander, he didn’t have a lot of experience balancing one on small, thin components. As you probably know, if a random orbit sander tips one way or the other on a narrow part, it will quickly remove more material from one edge or corner than you intend. Over multiple passes, that error compounds.
In David’s own shop, his normal workflow for parts like this is very different. He relies heavily on his drum sander, running pieces through at a very fine grit and leaving only light hand sanding before finishing. That approach minimizes the risk entirely. Balancing a random orbit sander on narrow stock simply isn’t something he ever has to think about.
The other factor was psychological. David was a guest in my shop. He didn’t feel entirely comfortable pushing back or suggesting an alternate approach, so he did exactly what I asked, even though it wasn’t how he would normally handle those parts.
Ultimately, the fault was mine as the instructor. I dropped the ball by making assumptions about David’s experience. I dropped the ball again by not checking in on his progress before the problem got out of control. Not to get sidetracked on technique, but an easy remedy for a situation like this is to sand multiple parts, side by side, so that the sander is fully supporting during the process. This is something I could have (and should have) shown David.
On paper, we lost three days. In reality, we gained far more than that.
Once we committed to the rebuild, we moved faster, worked more deliberately, and made a few small improvements along the way. What felt like a major setback turned into an opportunity to refine the process and tighten up details that might have otherwise been rushed. We caught back up in about a day and a half, and the final result was an even better bookcase than the first attempt would have been.
This is something I’ve seen over and over again, both in my own work and in the projects shared by our community. A mistake forces you to slow down, reassess, and re-engage with the fundamentals. When you do that honestly, the work almost always improves.
I encourage practice. There’s absolutely value in cutting joints on scrap, testing finishes on sample boards, and rehearsing techniques before committing to a build. But the most impactful lessons almost always come from real projects, the ones with deadlines, expectations, and consequences.
When the stakes are high, details matter more. Decisions carry weight. And mistakes hurt just enough to make sure you remember them next time. That’s where learning really sticks.
Because the apprenticeship was explicitly designed as a learning experience, I made sure David understood that I wasn’t upset, not even a little. This is what learning looks like in the real world. It’s messy, uncomfortable at times, and occasionally expensive.
The moment you stop making mistakes is usually the moment you stop pushing yourself. If you stay safely within the boundaries of what you already know, you might approach perfection. But the instant you venture into unfamiliar territory, new tools, new techniques, new designs, those mistakes come rushing back.
And that’s a good thing.
So build. Make mistakes. Learn from them. Then do it again. That cycle is the craft.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |