Woodworking scratches many of the same itches as programming for me, with one key difference: it’s unforgiving of mistakes, so requires a lot more care.
At least if you have a grinder, welding can sometimes be more forgiving.
Their pricing and supply times factored in a pretty significant failure rate, and we were basically asking them for highly precise screws and nuts for a couple thousand each.
But to check THAT tolerance, you have these metal screws that they need to securely attach or be unable to attach to. And since the metal fittings will be used for batch testing entire production runs of life or death parts for years to come, they go a little overboard with specifications.
I'm not sure if it really needed to be THAT precise, but that's just what it was
I'm not sure if this command will work? Well I may as well just try it anyway. Something broke? I'll throw in a breakpoint and try out a bunch of dummy variables and alternative methods until the errors stop.
And while it's a common complaint that compile times force some extra care, with hardware that extra care needs to happen outside the medium itself, mucking around with CAD software and such, before sending designs off to workshops. It'd be like if the solution to avoiding compile errors was very carefully handwriting code on paper
> (Western Canada, slang) beset with unfortunate circumstances that seem difficult or impossible to overcome; screwed.
https://en.wiktionary.org/wiki/hooped
I’d love to know its origin. I picked it up from family.
But working with wood a crippling anxiety hangs over me.