Once my wife learned of my plans, the requests for custom pieces started rolling in. Knowing that whatever I build has an eager recipient awaiting it is rocket fuel for motivation.
And since it's my wife asking for it, it's easier to justify buying the tools I "need".
I've grown my tool collection repeatedly this way :)
In 7th grade, our wood shop teacher lost a finger on the table saw, in the classroom. Not when I was there, and I'm not even sure it was during a class or with kids around, but she'd lost a finger, and that room was closed the rest of the year.
A few years later, a different teacher also lost part of a finger on a table saw, just working on something in his garage.
These weren't major factors, but have been partially responsible for me never developing a taste for hardware. I enjoyed metal shop in 6th grade for a bit, but... it got very loud, sometimes very hot, and the cost of doing anything wrong was great pain or death.
Contrast that with "nerdy" computer stuff... I could sit, relaxed, and 'create' stuff myself (often just typing in code from magazines and books, but it was a start!)
While not as tight to the blade as a riving knife, I've found these splitters[1] paired with a zero-clearance insert are an excellent alternative, and can be custom-fitted to almost any saw with nothing but a hand drill and the saw itself.
I learned respect for my table saw early in my software engineer turned part time woodworker career after a near miss kick back incident. I’ve been using MJ splitters ever since on my old school Delta unisaw.
Thanks. I only started using table saws a few years ago, so I watched a lot of youtube videos on safe operation.
It seems clear that using (riving knife) + (blade guard) + (push sticks or similar) + (feather board) + (careful adherence to safe operation) eliminates most of the risk.
I'm still unclear how much risk remains when following those rules. Maybe because most injuries I hear about involve people skipping at least one of those five elements.
Contrary to what YouTube will make you believe, you don't actually need any power tools to take up wood working as a hobby. You can do everything with hand tools, it will just take longer and often needs more skills.
My father was a professional cabinet maker and a decade ago he built a new kitchen from scratch. The only power tools he used were a table saw (which admittedly is one of the worse) and a belt sander. Everything else he did with hand tools.
I know it doesn't cover all the risks (including other tools and even poisoning) but it was a no-brainer for me to upgrade to a SawStop when I decided I was liking this hobby and was going to stick with it for a while.
I built HTML emails once upon a time - "in the trenches sending spam emails" is how I describe it. One can only send so many undesired trash missives that literally have no effect upon the physical world before you need an outlet. Woodworking allows me to use my skills, raw strength, and attention to detail to create things that look beautiful, are useful, and don't get deleted instantly.
I got out of HTML email a long time ago, thankfully.
out of curiosity — since it sounds like you might have been working on promotional or unsolicited email — did you ever see responses from your emails?
i’ve been responding to marketing emails recently — often CC’ing generic accounts like marketing@company, help@company, etc to try to reach actual humans in the loop. the process has been fascinating to me and the number of (intentional or unintentional) choke-points makes me wonder if — even in the more enlightened organizations i’ve worked in — i could ever stand a chance of understanding our email campaigns, inside and out.
These were largely upsell emails to existing AT&T customers, and I was a designer/developer for a marketing agency, so I barely had anything to do with the sending. Think like the largest of the large; audiences in the millions.
So, no replies, but my grandmother got one of the emails my agency designed! That one made me feel queasy.
Apologies if what I said was misleading. That agency laid me and over a hundred coworkers off; hence no qualms about divulging our primary customer.
If your work is abstract, making something concrete is very satisfying.
I used to have a big yard, and loved spending an hour on the riding mower enjoying the clouds and the birds. When I was done I could see something that I had accomplished.
I make my own surfboards for similar reasons. I tend to only code in my free time if I can't surf, or work on my next board (night time or no surf). Not sure how wood working it toddler friendly though?
This is great. I took up woodworking last year. The only thing about it that bummed me out is how expensive it is. I didn’t expect that. There’s a saying: “Why would I buy my wife a $500 dresser when I can build it myself for $1000?”
While it is true you can often buy IKEA furniture for less than the wood would cost you, for any “real” furniture made out of real wood, anything you build will be far, far cheaper than what you can buy. Of course that is valuing labor at $0 and cost of tools at $0.
If you are making something like cabinet doors that are mostly labor and not much wood, you can easily make them for one fifth the cost of what you’d pay from ikea… but tons of labor!
No way! I built myself an oak side table. Solid oak, $200 worth of wood. Now, this was during the beginning of the pandemic when wood prices were through the roof, but still, I bet I could get the same oak table for $150 or less.
There is some arbitrage as certain species of wood are cheaper if you are closer to where they come from (for example Douglas fir is cheaper on the west coast vs pine on the east coast), and for a small item it can be built where the wood is cheapest and shipped from there.
However, I think it’s not likely to make that large of a difference. Wholesale lumber prices aren’t that far off from what a hobbyist pays if you go to the same places.
Auctions for new and used wood are a great place for bargain.
I built my workbench out of $5 of scrap wood by buying a homemade platform that had been used for judging volleyball games, because no one else wanted a volleyball judging platform and I was willing to break it apart and cart away a couple hundred pounds of lumber.
I recently purchased a good quantity of rough cut maple, locust and oak for around 10-25 cents a board foot from another auction because the owner of the woodshop in question was retiring and everything must go.
This seems true to me (as a non-woodworker whose ex-partner got really into it), but what she explained to me was that her own furniture would be higher quality and also made the way she wants it (which you can't really put a price on)
You can definitely pick up used solid wood furniture for cheaper than building it yourself (especially if you consider the opportunity cost of your time), but you might not get exactly what you want.
Mass-produced hardwood furniture (OakFurnitureLand etc.) seems to be made of absolutely tiny scraps glued together, whereas if you are making something yourself you're more likely to use larger pieces of wood and less able to make use of small offcuts. I think that accounts for a lot of the price difference.
Where are you going to find an oak table for $150? $500 maybe if you're ok cutting corners. I was just out yesterday looking around and there wasn't a thing I'd put in my house (and I'm not that particular) that was under $1500.
The same thing can pretty much be said about any hobby. I know several people that do handmade clothing with both sewing or knitting. The knitters buying the really nice yarn will spend more in the yarn than a finished item from the store.
Aside from the pleasure of just doing something on your own, what you will probably have is something unique. People making electronic projects will probably adding features not available retail, or clothing in patterns and stitch design their own, etc.
So many hobbies are expensive. I know I'm not competing with mass-produced pieces. It's like never dining in a nice restaurant because there are so many fast-food chains out there.
So many hobbies are just various themes of consumerism. Like a hobby of buying watches/pens/keyboards/etc. There are a huge number of cheap/free hobbies though.
I've managed to do it on a budget. Tools can be bought used and wood can be scavenged from the curb or dumpsters. Both have a large time investment to find, so the trick is to do it passively. I take a lot of walks, and when I see a nice piece of free wood, I take it home and make stuff from it.
I joke with my friend: “I can build it myself for more!” And true, some projects cost more than buying it from a store… but the experience is worth it, and usually the end product is better than what you can get from a store.
The internet also makes it see like a consensus exists when in reality it is a tiny sample of the world. I am also constantly surprised by how many people give advice on a topic they have never actually partaken in, so this consensus may not even be borne of the real world.
> I am also constantly surprised by how many people give advice on a topic they have never actually partaken in, so this consensus may not even be borne of the real world.
Hey, that's why I'm on the internet. I could hardly talk about woodworking to actual carpenters in real life, could I?
You can guarantee whatever quality you want, though, which is nice. You'll know for sure whether corners were cut or material substituted, and if you do do that you'll know it was done as an explicit trade-off that you made.
Try working with metal - lot of tool are needed, and you always need one more. All of my wood working tool together cost the same as ONE tool for metal working.
So the end product may cost a bit on the material side, but cost way more with tooling factored in. And most of the tools I have are 30 to 50 years old :D
I'm guessing you're referring to machinist tools like milling machines and lathes? Machinist tools are quite expensive, but other types of metalworking (welding, brazing, blacksmithing) can be done with much more modest budgets.
You gotta find logs (which you can get at firewood places or haul off people’s downed trees) for very cheap/free and then saw your own slabs. The dimensional lumber at stores is incredibly expensive. You have to have a jointer and a planer for this to work though.
Agreed. I believe that used quality tools can often be found for a reasonable price. This is especially true if you don't mind doing some cleanup/repair on them.
2 years seems to work well where I live, but it depends on type of wood, recent weather, where you live, where you store it and many other things. I have a bunch of timber in various states of readiness for a bunch of different projects. It's a slow start, but once you've been doing it for a couple of years you will generally have something you can work with.
Yes, it depends on the thickness of the slabs, the local climate and the initial moisture content of the wood.
But, that much lumber is worth a lot of money. I think most domestic hardwoods are currently in the $5-$10 range per board foot (e.g. 12"x1"x1"). And that's rough sawn, you still need to mill that into usable pieces.
At least a year but what I’ve found is a lot of trees that get downed are already dead and dried out before a storm eventually brings them down. In this case, there is no waiting.
Alternatively you can take them to a kiln to get dried and the price still ends up being far below what you would pay per board foot for S2S lumber.
It starts like that, but experience builds and in the end you get to ‘making cool stuff out of scrap wood and discarded furniture picked up from the road side and maybe €10 in hardware’, ‘repairing a rotted window sill for €50 in hard wood’ (a fraction of the cost of getting someone to do it for you), and ‘building the perfect built-in closet that only you could do knowing the house and your wishes’.
And then there's just the efficiency of having a little workshop where you fix stuff in a jiffy and hardly notice the amount of things that get their lifespan doubled. Good for your bank account as well the environment.
Oh, and seeing your children grow up with the idea that their parents just make/fix stuff, and that repairing things is the natural way to go about life. My three year old son regularly takes his portable toy kitchen, his toy tools, and starts 'repairing' it. That's priceless.
The problem is, if you own a "nice" house, you need very good skills to do many DIY home improvements, for them to actually look good enough to match the house. Otherwise, you are reducing the resale value of your house with shoddy-looking work.
If I owned an old cottage or something like that, I would be quite comfortable doing DIY work on it. It's a little bit like doing DIY auto repairs on a brand-new Acura TSX vs. a 2002 Honda Civic. The stakes are different.
Disagree. Cookie cutter newer houses which may look "nice" and have "nice" values (probably inflated) don't have the craftsmanship you are describing.
I think its quite the opposite. If you owned an old cottage with exposed hardwood trim, stained glass window, exposed hardwood stairs with a carpet runner, and custom built-ins it would be much harder to DIY improvements. That type of older house may also have older plumbing, older electrical, and possibly plaster walls, all of which will require more care and knowledge to DIY things than new electrical, plumbing or drywall.
Take for instance fixing a piece of trim that is an exposed hardwood vs. fixing a piece of trim that could be PVC/composite and some-shade-of-white. You can caulk over mistakes with white trim vs. trying to do a miter on exposed hardwood trim with not-square walls.
A comment made by a carpenter friend of mine some 20+ years ago still sticks with me.
"The only difference between me and the guy who goes to Home Depot and does it himself is that I get it right the first time. This isn't rocket science."
His entire value proposition is that he can do something at high quality and get it done quickly. Yours is that you can do something high quality because we assume that you can take multiple attempts until you get it right.
I think it depends on the final quality and lumber used, too, though.
Pre-pandemic, I built my own cabinets in my garage with cabinet-grade plywood and Ikea butcherblock counters. I over-bought the wood by about 50% (because of a stupid mistake) and bought a really expensive track saw, and I still saved like 25-50% compared to buying the cabinets pre-made with the features I wanted. Even cheap cabinets would still have been slightly more expensive than DIY.
Granted, my cabinets are not perfect and I wouldn't put them in someone's kitchen, but they are more than good enough for what I need them for and both me and the wife are happy with them.
I don't think that is the case. Not for quality furniture.
When I build furniture there is no MDF or masonite anywhere in the build, no veneer, no staples (or pin nails) ... usually no fasteners at all.
And as had been pointed out in this thread — it is the exact height, width, depth that I want, with the features I want and the wood and finish that I want.
It's expensive? I really don't get that. That solid hardwood dresser that you build yourself, could easily last 100 years. The ikea stuff won't last a fraction of that. You shouldn't compare a store bought dresser with something you make yourself.
Also if you don't want the expense, there's plenty of small things you can make with a handful of tools. Whittling and carving is quite cheap and very satisfying.
Woodworking lacks rigor, too much "doing by feel" and too few carpenters have proper structural/mechanical engineering training. I recommend EE as a hobby for software engineers instead, RF and signal processing are just as concrete as woodworking and much more practical.
If you're serious, that's the point. We spend much of our lives doing rigorous work that's extremely logical, and unless you have a true connection to your code, there's no chance to "feel it out". Woodworking is that chance for many of us, even myself, building simplistic rabbit cages and ugly farm furniture.
I'd say try wood-lathe work. make a box and it's easy for it to end up wonky is the measurements are off. But make a goblet and the curves are what you make it - not necessarily what you plan.. But it feels good to shave off that wood.
I love wood working. I wish you could see my massive deck and outdoor sauna I made last year. It was one of the most fulfilling things I've done. It's also like meditation for me. You need to keep a clear head and maintain focus. In much of meditation there is a mantra you repeat to yourself. In wood working my mantra is the length of cut I need to make. I keep on repeating 15 and 5/8's (or whatever measurement I need) and I think it calms me down just as a meditation mantra.
I have a few hundred hours under my belt with a dining table, chairs, and even something with a roof to show for it.
For me, a huge chunk of each project’s fun was planning. Going through my first two prototypes in Sketchup (rather than in real life) was a massive amount of fun. That part really was not so different to hacking code, really.
The physical work itself is then completely different to software engineering. Nothing is simple — every step of the project presents some unique problem that you have to work around carefully. Maybe you forgot to include the width of the saw in a measurement. Or your stock has a knot in exactly the wrong place. Or you didn’t plan the assembly in the best way to optimise for clamping. Or you drip glue awkwardly and have to clean the first of six benches up before oiling. Or you want to add a shamfer in an awkward place to a piece you’ve already partly assembled.
Imagine having to stop work every few hours to hone the edge on an IDE that’s gone blunt. Imagine running out of 8mm if-statements (dowels) and having to improvise some more so you can peg a project together.
There’s no homogeneity with a natural product. Everything is slow and methodical with few opportunities to hack / test / prototype. You have to think and solve problems that you never thought would happen in a new kind of way because you can’t roll back or undo.
Above all, there are many things you just cannot automate. Sanding up the frame of a pergola getting it ready for oiling is going to be O(n) at best, with only ever a single processor to throw at the problem which itself is hard bounded by mealtimes and hours-in-day.
I respect that, but tbh I get a kick out using Svelte repl to generate SVG that I use in my CNC machine to cut wood. Feels fun to use software for some non-business purposes.
> The physical work itself is then completely different to software engineering.
It’s funny, but I often think how similar they are after doing a project. Maybe I haven’t written enough software for it to feel routine, but I often enjoy the unique and unexpected challenges in each that require creative thinking to solve.
One interesting woodworking tip I carried over was “Know your tolerance”, i.e. does it need to be accurate to within an inch, an eighth, etc. I often apply that when working on software now (i.e. how “perfect” and bug free does this component really need to be?)
People often say that “code is malleable” and you can change anything, whereas working with wood and tools is unforgiving. I actually think they’re comparable again, in that your time is what costs the most, and you can fix anything with minor materials cost compared to the time cost. Throwing away a piece of wood I worked on for a while and messed up isn’t much different than deleting a working branch that didn’t pan out. (Working with a contractor makes this more apparent. They’ll happily change almost anything after they’ve done it if you’re willing to pay for it).
Oh, and another similarity: I start lots of projects that interest me, but the ones that get finished are the ones my boss (the wife in this case) keeps hassling me about ;-)
Wood is malleable as well. Building a swing set for my children I learned the trick of taking the bow out of a warped 2x4 by applying leverage and screws as I assembled sections.
Better glue and screw that or it will surprise you at some point (unless you used screw overkill :) ). Better still: ripsaw, reverse one part then glue back together. (a lot more work, but that way the internal stresses in the wood will cancel out).
Would you use screws over internal dowels/biscuits for such a project? curious about best practice for something that is going to be outdoors 24x7. i agree that you need something to counteract the shear forces from the wood trying to bend back to its original warp. Not arguing, just intellectually curious.
In something like a swingset my first consideration would be safety, make everything from stuff that I'm 100% sure isn't going to surprise me one way or another, and given that it is a dynamically loaded structure with kids doing 'creative' stuff with it I'd aim for overkill rather than getting it 'just so' or working for something that looks good but that may not be strong enough.
If it's going to be outdoors in the weather over a very long period of time I would not count on glue (unless you have very good process control and know exactly what the long term properties will be) but I'd use steel to connect the various wooden bits, typically hole through (large diameter), then epoxy the hole and then drill again (smaller diameter). That stops the wood around the hole from rotting away. You also want to take care in what kind of wood you use in the first place a nice wood for stuff like that is Tamarack, which doesn't rot.
another principle applicable I think is knowing what may or may not change in the future. being able to switch from legs to wheels is useful, so maybe put an interface in between. being able to change a table into a bed - not useful and will sink your project.
The friends library is well known to have lots and lots of dependencies, and can be very rough to work out the multiple things available to have a working friends class.
Or shims. I always feel like I am responsible for a personal feeling when I need to use a shim, even if it’s because the wood I bought didn’t have the right dimensions.
> Can I make 2 things of the same dimension with 1 cut?
When I realized that "measure once, cut twice" is actually the superior methodology I laughed for a week.
(As in, set up your cuts or use jigs so that you aren't trying to mark 34 5/16 inches on 6 separate pieces of wood and expecting them to be the same length afterwards.)
Lol I guess you have not seen some of the code I have trying to use reactive programming at all costs.
In all seriousness though, I think software is quite flexible. A lot of what programmers do is take two APIs which don’t quite go together and find a way to bridge the gap.
Even the word “shim” is borrowed from woodworking and used in programming as well.
While writing my comment I thought about whether it was really correct (happens to me often).
I think the analogy for a software hack in the real world is not a hammer blow but rather, pieces of string tying together things that don't want to work with one another.
Strings tend to wear with use, and eventually break, sometimes catastrophically; whereas pieces that were forced to fit, usually stay put forever.
Sometimes yes and sometimes no. Sometimes a hack is also filling in a gap in the back sawdust mixed with wood-glue, and that will generally last longer and be more durable than the rest of the piece.
I used to be a Carpenter and Joiner. I gained some financial qualifications through distance learning and needed some experience.
The guy who hired me told me later that there was some resistance from the team to my joining. He told them that if I could work out winding stairs, accounts would be no problem!
Regarding the ability to fix with a hammer, I would say that with software humans tended to just work around the poor fit!
Honestly this just sounds like you're just happy to be a junior at something again, where you don't know what you don't know and can't plan accordingly, and each time you solve a problem you get dopamine.
100s of hours of wood working is nothing, A wood worker that does this for a living with 1000s of hours doesn't run into these issues nearly as often, same for senior devs with programming.
> Imagine having to stop work every few hours to hone the edge on an IDE that’s gone blunt. Imagine running out of 8mm if-statements (dowels) and having to improvise some more so you can peg a project together.
This sounds like IntelliJ. Have to restart it every once in a while, invalidate caches, tweak some settings, sometimes re-import the project. Oops, an update arrived and now all your settings are reset to bizarre values. That's another few hours trying to get it right again.
My googlefoo is failing me, and I'm out of searches this month on Kagi, but there's a very famous programmer that now runs an arcade/bar in SF. He's got a real long blog post about how he doesn't update anything.
Maybe when intellij tells you it wants to update again, just tell it no
> For years I've had it drummed into my head that you always have to keep your systems patched, if you aren't running the latest security fixes, the script kiddies will eat you alive, running a six month old OS is like leaving your front door wide open, blah blah blah. Well you know what? Fuck that noise. I'm done upgrading anything ever. The next time I get this shit into a state that seems even remotely stable, I'm never touching it again. If we get hacked, oh well. I have backups. It has got to be less work to recover from than constantly dealing with this kind of nonsense.
Or possibly this CodingHorror blog entry that summarizes a few other instances of jwz saying this:
I try to instill in people the idea that their judgement is compromised at the end of the day and especially the end of the week. If you don't fight the urge to 'finish' something before going home, then what you're doing is dropping code that isn't up to your normal standards on your coworkers and then leaving the building. If you are the sort who comes in late and leaves late, you're painting a giant target on your head doing this, because everyone has had time to stew about anything you broke (possibly before their morning coffee has kicked in).
I mention this because the alternative is to have a cutoff of 90 minutes before you leave, and then have a lot of days where you end up with 45+ minutes to kill before it's acceptable to go home. What can you do in this time that makes sense? Basic maintenance is one thing. Rebooting your machine, restarting that IDE, clearing up disk space, upgrading things. Documentation is another. Cleaning up the Wiki is a good thing, especially on that odd day when you finish a project 1pm on Friday and starting something new makes no sense.
But for upgrading software? I think the best option is to look at your team and think, "who would I go to if my code/machine is behaving like the magic smoke got out?" Those people should be doing all of the upgrades, and then reporting their success/failures to everyone else.
I think what Jamie is seeing here though is the downside of open source. Nobody is getting paid to care as much about your use case as you care about it. Sometimes that's empowering, but it's also a huge responsibility. People who pay a lot for software are trying to delegate that responsibility. Win, lose, or draw, that's why they do it.
And what Jamie is missing here is hackers with a vendetta. "If we get hacked, oh well. I have backups." They know you have backups. If they just want to count coup, then your backups will be fine. But I've known of two different services where a slighted user hacked them and made it hurt.
In the first case it was something I hadn't used for a year or two, but I knew a guy who knew a guy who got banned. Found out through my friend that this guy put a time bomb in the backups, and managed to kill their server and all of the backups on the same day. That site was down for months, and almost didn't come back at all.
In the second case, the hackers didn't even take down the site. They exploited a kernel bug and logged all of the private conversations of the administrators, then cherry picked all of the worst bits and some spoilers and posted them online. That site was supposed to be down for a month+, and I think was down for almost 3.
There's also the Home Depot Game, which is whether you can go to the hardware store once at the beginning of the project, and then not have to go a second (or third) time before you're done because you forgot something or you broke one of the pieces and didn't buy spares.
Fellow coder and woodworker here. I can relate to the article for sure and I'd add that in my case I make a point of avoiding using software or computer-assisted anything in my woodworking. So no Fusion 360, no SketchUp, no CNC, no laser cutters, no 3D printers.
It sounds radical but it feels important to my mental health to keep my woodworking physical an analog as possible. Now, I'm still a power tool junkie so I'm not about to give up my table saw or planer.
Aside from being phisical I think it has also to do with real time play and the easier ability to enter flow state. And nowadays with all the dev stacks, frameworks, cloud platforms and all the other noise, with coding it has become harder reach that zone. I don’t do woodwork but paint and I imagine it registers quite close to woodworking. Enjoy the experience.
I tried doing things with no cad step and the result is just garbage. Maybe if you have a lot of talent you can pull it off but I ended up making mistakes and then being unable to recover from them.
Same here. I love woodworking and got some tiny skills but I keep it totally separate from the digital world. Now: at times I wish I had a 3D printer and 3D modelling skills and could models some plastic pieces I'd need for this or that.
You should try giving hand tools a try, if you want to take even one step further from avoiding The Machine.
Hand tools take a bit more practice but the rush of seeing your skill progress never goes away. Just yesterday I made a well fitting mortise and tenon joint. This is something I've done a thousand times, yet I still get the deep sense of satisfaction every time I see it set nicely.
I bet I could square up rough stock with my hand plane faster than your power planer/joiner, too. Cutting to size the hundreds of 1X3" I needed earlier, on the other hand...
I found Sketchup helps plan larger items where there are dimension constraints like a built-in for a closet or a workbench. Once you learn enough (and restrain yourself from becoming an "expert") of the tool it can be easier/faster to plan things out than pencil and paper. It could be that as a rookie, Sketchup lets me experiment with things where if I had a few projects under my belt of the same type I could just get rough dimensions jump in.
I do love heading into the shop and just making something though.
Same here, I really enjoy sketching it on paper. I've only made small, handheld objects so far though, I may change my mind once I decide to take on larger projects
Interestingly, woodworking is where I get to apply math, 3d modeling, drawing, and other things I dreamed tech would let me do. As a software engineer I don’t do many of the things I envisioned, at least not the way I hoped, so woodworking scratched the itches still.
I got into woodworking as my first real job. It’s such a great pastime too, though. Just like this post says.
Something I highly recommend if you find woodworking too expensive is to look into what you can do with basic hand tools and found wood. Try making spoons from green wood, for example. If you can get into it, it’s practically free and incredibly gratifying.
There are plenty of cool things you can make and even gift to people without a single power tool.
I like woodworking because it takes me away from the world of purely mental, metal things. It also doesn't hurt at all that it was the profession Jesus worked before fulfilling the Messianic prophecy.
I also find the products of my work aesthetically pleasing or useful. I am very happy, grateful to be able-bodied to do any amount of woodworking. I hope everyone else gets to enjoy something like that feeling for even just a minute.
Yeah, this is me. The main reason I don’t have any personal programming projects is because all of my free time is taken up with family and woodworking. I’m on sabbatical right now and I’m spending almost all my time in my workshop.
I mostly play with metalwork as a hobby. But I did make some of my furniture, mostly because I couldn't find what I wanted (bed, workbench), or because I wanted to build them in-place (bookshelves, different workbench, some storage).
The furniture thus far as been mainly functional - not that it is unattractive, but it is all very form-follows function. I rather like that in general, but also see my mistakes and room for improvement. But then I'm probably moving soon, and may well need to rethink and downsize furniture anyway.
Funny, I started woodworking partially because I was doing less development (more on the management side).
Woodworking scratches that "build something" itch.
Plus, it has a high SAF (spouse approval factor). If I spend a Saturday writing a software tool, my wife is wondering why the lawn wasn't mowed. If I spend it building a coffee table, she's delighted :D
I really like this article though, and relate completely. I do metalworking and fabrication (building race cars) as a side hobby because having a tactile, physical thing to tinker with helps cool off from the daily software work.
All this and more. I'm fortunate enough that while I could afford to hire trades to do all the things I've done in and outside of our house in the last couple years (gutted/rebuilt kitchen & bathrooms, built phase one of a three phase deck/backyard oasis) I have to keep telling my spouse, yes, we could hire someone, but I really LIKE doing this stuff. Like really like.
It's now got to a point that the requests, and "He can build that" comments to friends are not accompanied with the trademark eye roll.
All the points the author hit ring true - planning, design, tool choice, etc have similar parallels to code and systems I work with during the day. But, I can cook meals for my family knowing that I built that space, then sit on the deck watching the wind in the trees knowing how many pieces of pressure treated lumber are holding me up and how it felt putting them all together. I never get that visceral connection using a web app.
Machining and metal work is the same for me. And now we have a lathe and mill and lots of precise measuring instruments. It is fun to re-create things like stirling engines and steam engines and work your way through the technology of the industrial revolution. Machining and precision are more fun than wood work for me. It made wood working seem rather easy by comparison as the level of precision required is often less by an order of magnitude or more when wood working. If your goal is just to build useful things MIG welding is very accessible and with a bit of practice you can fabricate useful strong things with metal as well. Wood work and metal work can also be combined of course. Metal working and machining definitely gets more expensive than wood working though.
What kind of mill did you get? I've been interested in one but I don't have that much space and I've heard that benchtop mills are not that useful, I hope that's not true since it would be my only option.
I have a lot of space, but check out Blondihacks on YT. They are quite useful, they just have limitations you have to respect. Just depends on what you are trying to do.
(My mill is a Sharp LMV 49 DVS btw). Lathes are a better starting point for most beginners BTW. But really both are fine to start with if in budget.
Glue takes far longer to dry than even C++ takes to compile. Not a fan for that reason only. Ok, also, no undo button. Wrenching on my car, tho. That's fun.
You also see over representation of coders climbing and in the martial arts (particularly grappling) - I've done both myself. I'd do wood working if I had the space. I don't really know why its like this, except that they all make sense to me in the same way that writing software does. Any other reason is a just so story.
For me it’s simple. Woodworking is a problem that I can solve. I mean I am trying to meet market demand and producing a product that I know will be used. Now the part of planning, design, “procuring funding”, building the product and “selling” it is all a story end to end.
I have been a software engineer all my working life, and I absolutely despise woodworking or anything that smacks of DIY. I find them unbelievably stressful and frustrating partly because I can see how I want things to be, they never work out nearly that good and I can never fix them.
I would consider knowing when things are 'good enough' is a core skill in software engineering too. There's always time to take another swing at it later. Nothings perfect
Agreed, and I'm more than fine with that in software. My attempts at woodworking/DIY are definitely not "good enough" by any objective standards.
Bookcase that fell off a wall shattering a glass desk and filling an entire room with books and papers laced with splinters? Yup. That was me.
Shed with gaps inbetween the walls large enough you can see in from the outsides? Also me.
School woodworking project to make an engraving that was so terrible it transmuted into an ashtray even though none of my family smoke? You got it. Me.
Ikea bed assembly where I got so frustrated that my friends banned me from helping assemble it and did it for me even though it was my bed? Err I'm not proud of it, but it did happen.
I could go on, but in any case. I don't like woodworking and I have plenty of good reasons not to. Perfectionism is not the problem.
>Shed with gaps inbetween the walls large enough you can see in from the outsides?
if it makes you feel any better, there's advantages to that too. If the wind can get through it, it's unlikely that moisture will be trapped inside. as long as the gaps aren't so wide that it's raining into the shed, anyway.
I try to evolve satisfaction at my own jobs badly done. I also admire anyone that has done something, even when they fail.
There are uncountable skills to learn in one lifetime: there can be joy in accepting that one will always be crappy at most crafts. Celebrate tiny improvements.
I think we all have an IQ of 60 in different areas of our lives: being kind to our low IQ selves and encourage the best out of our poor weird misfired brains, like we would any child. Encourage the disabled you, usually nobody else will help much, or worse, lots of people will meanly cut you down. Be kind to yourself, mostly say positive things and be constructive.
> Bookcase that fell off a wall shattering a glass desk and filling an entire room with books and papers laced with splinters? Yup. That was me.
This one sounds as the worst "failure", but in general, hanging a book case off the wall is hard even for experienced professionals: books are notoriously heavy, and walls are of vastly different constructions, so sometimes, hanging it up is simply... impossible (eg. with a drywall if you can't find the drywall frame behind, or if that is too weak).
When I did remodelling of my place, I've planned for steel support behind wherever I wanted to hang heavy items (like a double vanity sink unit [people also lean on them], book cases, TV with a wooden panel behind it and similar). And you need to use special screws for different wall types and load (concrete anchors, wall/rawl plugs, toggle bolts, drywall anchor plugs... — though my English names might be off for these :).
So in short, don't hold this one much against yourself: it's sometimes hard even for seasoned pros, let alone hobbyists. I am just a seasoned hobbyist that's a sucker for hanging items (or actually, having clear floor to clean).
Anyway, the thing that attracts me to woodworking (and previously, chipboard cabinet construction) is that you get to make your own ideas: just like with software. But building stuff is not limited to software development or woodworking, and while there are plenty of software engineers enjoying woodworking, there are other ways to enjoy building your own stuff, and some might even enjoy not building anything after they've been doing it for 8+ hours a day.
that's the struggle of learning any new skill, though. at first you're going to suck, and you're gonna know you suck, but you have to keep going to stop sucking eventually. same with programming.
With programming you have source control and some form of an undo command. You also have a compiler and (if you can be bothered writing them) tests.
If you need another tool or another component you can just search for it on the internet and if it's available you can have it in seconds. No trips to a shop that may or may not have what you need, or queueing, or explaining what you need to a shop assistant who couldn't really give a shit, or being upsold on some other thing that you don't really need or understand, etc.
Also, crucially for me personally, there's no mess that needs to be tidied away before the rest of the family come find you. There's no storage area needed for half-finished crap, odds and ends you can't decide if you need in future, potentially dangerous power tools, that kind of thing.
Building software is like taking all the fun parts of DIY and leaving all the boring / dangerous / physically taxing parts behind, and you can pretty much do it wherever you have a power supply and internet connection. That's why I first loved it and why I continue to do it today.
> With programming you have source control and some form of an undo command. You also have a compiler and (if you can be bothered writing them) tests.
There is always an undo, just get another board.
> Building software is like taking all the fun parts of DIY and leaving all the boring / dangerous / physically taxing parts behind, and you can pretty much do it wherever you have a power supply and internet connection. That's why I first loved it and why I continue to do it today.
I have a different point of view. The software you build is ephemeral. You can't show it to someone. The architecture and the beautify of it's interplay is hidden and it's art is only available to you. I can show you my dovetail and let you feel how smooth the finish is. It's real. You can explorer it with your senses.
I also think a lot more people than just devs like woodworking. Some time ago, I spoke to a GP (family doctor) who was going to take woodworking classes because of COVID-fatigue. Perhaps there's a baseline that the author needs to take into account.
Woodworking is rooted in reality. Angles are not perfect, measures are not perfect. In coding, everything is perfect. That I don't like the first and like the second.
This is probably why I've spent most of my career in embedded systems. It's the juncture of "this code will always execute the same way over the next 100,000 cycles" versus "the actuator controlled by that code will execute the same way for the first 10,000 cycles then start to go haywire as the bearings wear and the salt water starts corroding the slides leading to a bug that only shows up an hour after high tide."
If I wanted to get into woodworking while living in an apartment in a city, any recommendations on books, places to look, or videos on how to get started? I've been looking for a hobby to take myself out of the whole digital grind and find some type of stress releasing, but challenging hobby
Maker spaces often have woodworking equipment. In LA where I live, and also in MN where I'm from, there were several options.
They usually offer classes if you don't want to start yourself. But you can learn a ton by looking up cabinetmaking or something else on Youtube. For a real trip, watch joinery -- it's mesmerizing.
Other than that, I started by just picking up a saw and going to town, and quickly googling "How do I" to find out much more than I wanted to know. It pays to learn about the basic tools first. Table saw, Router table, Chop saw, Drill press, etc.
He focuses heavily on using hand tools instead of machines, so much more suitable for apartments. He's also budget conscious, and tries to show ways of achieving things without spending a ton on lots of expensive or specialised tools.
Already some good responses to this, but for something different. Have you considered some other hands on hobbies? Knitting, painting, sharpening knives, advanced cooking.
253 comments
[ 1.8 ms ] story [ 255 ms ] threadA few years later, a different teacher also lost part of a finger on a table saw, just working on something in his garage.
These weren't major factors, but have been partially responsible for me never developing a taste for hardware. I enjoyed metal shop in 6th grade for a bit, but... it got very loud, sometimes very hot, and the cost of doing anything wrong was great pain or death.
Contrast that with "nerdy" computer stuff... I could sit, relaxed, and 'create' stuff myself (often just typing in code from magazines and books, but it was a start!)
I'm just curious what era of safety devices were likely available.
https://en.wikipedia.org/wiki/Riving_knife
[1] https://www.microjig.com/collections/mj-splitter
We were in a 'newer' school district - the middle school was less than 10 years old at that time. All equipment was relatively 'new'.
It seems clear that using (riving knife) + (blade guard) + (push sticks or similar) + (feather board) + (careful adherence to safe operation) eliminates most of the risk.
I'm still unclear how much risk remains when following those rules. Maybe because most injuries I hear about involve people skipping at least one of those five elements.
You can still do much worse of course, like chewing off all your fingers in a jointer or embedding an angle grinder wheel in your face.
My father was a professional cabinet maker and a decade ago he built a new kitchen from scratch. The only power tools he used were a table saw (which admittedly is one of the worse) and a belt sander. Everything else he did with hand tools.
I got out of HTML email a long time ago, thankfully.
i’ve been responding to marketing emails recently — often CC’ing generic accounts like marketing@company, help@company, etc to try to reach actual humans in the loop. the process has been fascinating to me and the number of (intentional or unintentional) choke-points makes me wonder if — even in the more enlightened organizations i’ve worked in — i could ever stand a chance of understanding our email campaigns, inside and out.
So, no replies, but my grandmother got one of the emails my agency designed! That one made me feel queasy.
Apologies if what I said was misleading. That agency laid me and over a hundred coworkers off; hence no qualms about divulging our primary customer.
Very true with wood unfortunately.
If you are making something like cabinet doors that are mostly labor and not much wood, you can easily make them for one fifth the cost of what you’d pay from ikea… but tons of labor!
There is some arbitrage as certain species of wood are cheaper if you are closer to where they come from (for example Douglas fir is cheaper on the west coast vs pine on the east coast), and for a small item it can be built where the wood is cheapest and shipped from there.
However, I think it’s not likely to make that large of a difference. Wholesale lumber prices aren’t that far off from what a hobbyist pays if you go to the same places.
I built my workbench out of $5 of scrap wood by buying a homemade platform that had been used for judging volleyball games, because no one else wanted a volleyball judging platform and I was willing to break it apart and cart away a couple hundred pounds of lumber.
I recently purchased a good quantity of rough cut maple, locust and oak for around 10-25 cents a board foot from another auction because the owner of the woodshop in question was retiring and everything must go.
You can definitely pick up used solid wood furniture for cheaper than building it yourself (especially if you consider the opportunity cost of your time), but you might not get exactly what you want.
Aside from the pleasure of just doing something on your own, what you will probably have is something unique. People making electronic projects will probably adding features not available retail, or clothing in patterns and stitch design their own, etc.
Lots of way to value something other than $
"Why would you do something to augment your experience of reality if it's inefficient?"
Hey, that's why I'm on the internet. I could hardly talk about woodworking to actual carpenters in real life, could I?
For some people, this comes with a condition: "as long as it's terrible" ;)
But, that much lumber is worth a lot of money. I think most domestic hardwoods are currently in the $5-$10 range per board foot (e.g. 12"x1"x1"). And that's rough sawn, you still need to mill that into usable pieces.
Alternatively you can take them to a kiln to get dried and the price still ends up being far below what you would pay per board foot for S2S lumber.
And then there's just the efficiency of having a little workshop where you fix stuff in a jiffy and hardly notice the amount of things that get their lifespan doubled. Good for your bank account as well the environment.
Oh, and seeing your children grow up with the idea that their parents just make/fix stuff, and that repairing things is the natural way to go about life. My three year old son regularly takes his portable toy kitchen, his toy tools, and starts 'repairing' it. That's priceless.
If I owned an old cottage or something like that, I would be quite comfortable doing DIY work on it. It's a little bit like doing DIY auto repairs on a brand-new Acura TSX vs. a 2002 Honda Civic. The stakes are different.
I think its quite the opposite. If you owned an old cottage with exposed hardwood trim, stained glass window, exposed hardwood stairs with a carpet runner, and custom built-ins it would be much harder to DIY improvements. That type of older house may also have older plumbing, older electrical, and possibly plaster walls, all of which will require more care and knowledge to DIY things than new electrical, plumbing or drywall.
Take for instance fixing a piece of trim that is an exposed hardwood vs. fixing a piece of trim that could be PVC/composite and some-shade-of-white. You can caulk over mistakes with white trim vs. trying to do a miter on exposed hardwood trim with not-square walls.
"The only difference between me and the guy who goes to Home Depot and does it himself is that I get it right the first time. This isn't rocket science."
His entire value proposition is that he can do something at high quality and get it done quickly. Yours is that you can do something high quality because we assume that you can take multiple attempts until you get it right.
Pre-pandemic, I built my own cabinets in my garage with cabinet-grade plywood and Ikea butcherblock counters. I over-bought the wood by about 50% (because of a stupid mistake) and bought a really expensive track saw, and I still saved like 25-50% compared to buying the cabinets pre-made with the features I wanted. Even cheap cabinets would still have been slightly more expensive than DIY.
Granted, my cabinets are not perfect and I wouldn't put them in someone's kitchen, but they are more than good enough for what I need them for and both me and the wife are happy with them.
When I build furniture there is no MDF or masonite anywhere in the build, no veneer, no staples (or pin nails) ... usually no fasteners at all.
And as had been pointed out in this thread — it is the exact height, width, depth that I want, with the features I want and the wood and finish that I want.
Started out building MAME cabinets, BTW, ha ha.
If you are just starting out, I'd recommend starting with just the core tools [1] and a block plane.
[1] https://www.lie-nielsen.com/nodes/4219/home-education-gettin...
Also if you don't want the expense, there's plenty of small things you can make with a handful of tools. Whittling and carving is quite cheap and very satisfying.
For me, a huge chunk of each project’s fun was planning. Going through my first two prototypes in Sketchup (rather than in real life) was a massive amount of fun. That part really was not so different to hacking code, really.
The physical work itself is then completely different to software engineering. Nothing is simple — every step of the project presents some unique problem that you have to work around carefully. Maybe you forgot to include the width of the saw in a measurement. Or your stock has a knot in exactly the wrong place. Or you didn’t plan the assembly in the best way to optimise for clamping. Or you drip glue awkwardly and have to clean the first of six benches up before oiling. Or you want to add a shamfer in an awkward place to a piece you’ve already partly assembled.
Imagine having to stop work every few hours to hone the edge on an IDE that’s gone blunt. Imagine running out of 8mm if-statements (dowels) and having to improvise some more so you can peg a project together.
There’s no homogeneity with a natural product. Everything is slow and methodical with few opportunities to hack / test / prototype. You have to think and solve problems that you never thought would happen in a new kind of way because you can’t roll back or undo.
Above all, there are many things you just cannot automate. Sanding up the frame of a pergola getting it ready for oiling is going to be O(n) at best, with only ever a single processor to throw at the problem which itself is hard bounded by mealtimes and hours-in-day.
I love it because it’s not like software.
It’s funny, but I often think how similar they are after doing a project. Maybe I haven’t written enough software for it to feel routine, but I often enjoy the unique and unexpected challenges in each that require creative thinking to solve.
One interesting woodworking tip I carried over was “Know your tolerance”, i.e. does it need to be accurate to within an inch, an eighth, etc. I often apply that when working on software now (i.e. how “perfect” and bug free does this component really need to be?)
People often say that “code is malleable” and you can change anything, whereas working with wood and tools is unforgiving. I actually think they’re comparable again, in that your time is what costs the most, and you can fix anything with minor materials cost compared to the time cost. Throwing away a piece of wood I worked on for a while and messed up isn’t much different than deleting a working branch that didn’t pan out. (Working with a contractor makes this more apparent. They’ll happily change almost anything after they’ve done it if you’re willing to pay for it).
If it's going to be outdoors in the weather over a very long period of time I would not count on glue (unless you have very good process control and know exactly what the long term properties will be) but I'd use steel to connect the various wooden bits, typically hole through (large diameter), then epoxy the hole and then drill again (smaller diameter). That stops the wood around the hole from rotting away. You also want to take care in what kind of wood you use in the first place a nice wood for stuff like that is Tamarack, which doesn't rot.
https://en.wikipedia.org/wiki/Larix_laricina
Combined with stainless steel hardware that should last longer than you will.
I had instant flashbacks of memory leaks in eclipse.
If you use
you can increase the processing power. Depending on the quantity of beerSupply can increase the errors and decrease effeciency of the extra processors> Module not found: Error: Can't resolve 'friends' in '/creakingstairs/people/`
on edit: the old it's / its problem got me.
So emacs?
- How can I get these parts/cuts etc accurate without measuring them all each time? Or without measuring at all but just transferring the dimension.
- Can I clamp that glue joint together with the weird angle?
- How can I get the most from these sheets of plywood / beams of lumber? How to fit the stuff in the car, or do I split up etc?
- Can I make 2 things of the same dimension with 1 cut?
- Can I make that without needed other tools?
When I realized that "measure once, cut twice" is actually the superior methodology I laughed for a week.
(As in, set up your cuts or use jigs so that you aren't trying to mark 34 5/16 inches on 6 separate pieces of wood and expecting them to be the same length afterwards.)
Obligatory link (often featured on HN): http://johnsalvatier.org/blog/2017/reality-has-a-surprising-...
But in actuality, it's often the case that one can fix physical things with a few well-applied hammer blows, especially in woodworking.
With some non-wood materials it's much harder to make something fit where it doesn't fit.
In software, it's usually impossible.
Lol I guess you have not seen some of the code I have trying to use reactive programming at all costs.
In all seriousness though, I think software is quite flexible. A lot of what programmers do is take two APIs which don’t quite go together and find a way to bridge the gap.
Even the word “shim” is borrowed from woodworking and used in programming as well.
I think the analogy for a software hack in the real world is not a hammer blow but rather, pieces of string tying together things that don't want to work with one another.
Strings tend to wear with use, and eventually break, sometimes catastrophically; whereas pieces that were forced to fit, usually stay put forever.
I used to be a Carpenter and Joiner. I gained some financial qualifications through distance learning and needed some experience.
The guy who hired me told me later that there was some resistance from the team to my joining. He told them that if I could work out winding stairs, accounts would be no problem!
Regarding the ability to fix with a hammer, I would say that with software humans tended to just work around the poor fit!
https://en.wikipedia.org/wiki/Duck_typing
100s of hours of wood working is nothing, A wood worker that does this for a living with 1000s of hours doesn't run into these issues nearly as often, same for senior devs with programming.
This sounds like IntelliJ. Have to restart it every once in a while, invalidate caches, tweak some settings, sometimes re-import the project. Oops, an update arrived and now all your settings are reset to bizarre values. That's another few hours trying to get it right again.
Maybe when intellij tells you it wants to update again, just tell it no
https://www.dnalounge.com/backstage/log/2006/04/
> For years I've had it drummed into my head that you always have to keep your systems patched, if you aren't running the latest security fixes, the script kiddies will eat you alive, running a six month old OS is like leaving your front door wide open, blah blah blah. Well you know what? Fuck that noise. I'm done upgrading anything ever. The next time I get this shit into a state that seems even remotely stable, I'm never touching it again. If we get hacked, oh well. I have backups. It has got to be less work to recover from than constantly dealing with this kind of nonsense.
Or possibly this CodingHorror blog entry that summarizes a few other instances of jwz saying this:
https://blog.codinghorror.com/let-that-be-a-lesson-to-you-so...
I mention this because the alternative is to have a cutoff of 90 minutes before you leave, and then have a lot of days where you end up with 45+ minutes to kill before it's acceptable to go home. What can you do in this time that makes sense? Basic maintenance is one thing. Rebooting your machine, restarting that IDE, clearing up disk space, upgrading things. Documentation is another. Cleaning up the Wiki is a good thing, especially on that odd day when you finish a project 1pm on Friday and starting something new makes no sense.
But for upgrading software? I think the best option is to look at your team and think, "who would I go to if my code/machine is behaving like the magic smoke got out?" Those people should be doing all of the upgrades, and then reporting their success/failures to everyone else.
I think what Jamie is seeing here though is the downside of open source. Nobody is getting paid to care as much about your use case as you care about it. Sometimes that's empowering, but it's also a huge responsibility. People who pay a lot for software are trying to delegate that responsibility. Win, lose, or draw, that's why they do it.
And what Jamie is missing here is hackers with a vendetta. "If we get hacked, oh well. I have backups." They know you have backups. If they just want to count coup, then your backups will be fine. But I've known of two different services where a slighted user hacked them and made it hurt.
In the first case it was something I hadn't used for a year or two, but I knew a guy who knew a guy who got banned. Found out through my friend that this guy put a time bomb in the backups, and managed to kill their server and all of the backups on the same day. That site was down for months, and almost didn't come back at all.
In the second case, the hackers didn't even take down the site. They exploited a kernel bug and logged all of the private conversations of the administrators, then cherry picked all of the worst bits and some spoilers and posted them online. That site was supposed to be down for a month+, and I think was down for almost 3.
I dunno dude, that sounds just like software to me, lol
Sounds like my brain...
It sounds radical but it feels important to my mental health to keep my woodworking physical an analog as possible. Now, I'm still a power tool junkie so I'm not about to give up my table saw or planer.
However I've picked up some skills along the way. It's nice to be able to design and build small projects around the home.
Power tool junkie FTW too.
If I do plans, it is using a pencil. But mostly I just improvise. There is only so much value in doing plans for one off projects.
Hand tools take a bit more practice but the rush of seeing your skill progress never goes away. Just yesterday I made a well fitting mortise and tenon joint. This is something I've done a thousand times, yet I still get the deep sense of satisfaction every time I see it set nicely.
I bet I could square up rough stock with my hand plane faster than your power planer/joiner, too. Cutting to size the hundreds of 1X3" I needed earlier, on the other hand...
I do love heading into the shop and just making something though.
I got into woodworking as my first real job. It’s such a great pastime too, though. Just like this post says.
Something I highly recommend if you find woodworking too expensive is to look into what you can do with basic hand tools and found wood. Try making spoons from green wood, for example. If you can get into it, it’s practically free and incredibly gratifying.
There are plenty of cool things you can make and even gift to people without a single power tool.
I also find the products of my work aesthetically pleasing or useful. I am very happy, grateful to be able-bodied to do any amount of woodworking. I hope everyone else gets to enjoy something like that feeling for even just a minute.
The furniture thus far as been mainly functional - not that it is unattractive, but it is all very form-follows function. I rather like that in general, but also see my mistakes and room for improvement. But then I'm probably moving soon, and may well need to rethink and downsize furniture anyway.
Woodworking scratches that "build something" itch.
Plus, it has a high SAF (spouse approval factor). If I spend a Saturday writing a software tool, my wife is wondering why the lawn wasn't mowed. If I spend it building a coffee table, she's delighted :D
I really like this article though, and relate completely. I do metalworking and fabrication (building race cars) as a side hobby because having a tactile, physical thing to tinker with helps cool off from the daily software work.
It's now got to a point that the requests, and "He can build that" comments to friends are not accompanied with the trademark eye roll.
All the points the author hit ring true - planning, design, tool choice, etc have similar parallels to code and systems I work with during the day. But, I can cook meals for my family knowing that I built that space, then sit on the deck watching the wind in the trees knowing how many pieces of pressure treated lumber are holding me up and how it felt putting them all together. I never get that visceral connection using a web app.
(My mill is a Sharp LMV 49 DVS btw). Lathes are a better starting point for most beginners BTW. But really both are fine to start with if in budget.
Close enough to drying glue
I have been a software engineer all my working life, and I absolutely despise woodworking or anything that smacks of DIY. I find them unbelievably stressful and frustrating partly because I can see how I want things to be, they never work out nearly that good and I can never fix them.
Bookcase that fell off a wall shattering a glass desk and filling an entire room with books and papers laced with splinters? Yup. That was me.
Shed with gaps inbetween the walls large enough you can see in from the outsides? Also me.
School woodworking project to make an engraving that was so terrible it transmuted into an ashtray even though none of my family smoke? You got it. Me.
Ikea bed assembly where I got so frustrated that my friends banned me from helping assemble it and did it for me even though it was my bed? Err I'm not proud of it, but it did happen.
I could go on, but in any case. I don't like woodworking and I have plenty of good reasons not to. Perfectionism is not the problem.
if it makes you feel any better, there's advantages to that too. If the wind can get through it, it's unlikely that moisture will be trapped inside. as long as the gaps aren't so wide that it's raining into the shed, anyway.
There are uncountable skills to learn in one lifetime: there can be joy in accepting that one will always be crappy at most crafts. Celebrate tiny improvements.
I think we all have an IQ of 60 in different areas of our lives: being kind to our low IQ selves and encourage the best out of our poor weird misfired brains, like we would any child. Encourage the disabled you, usually nobody else will help much, or worse, lots of people will meanly cut you down. Be kind to yourself, mostly say positive things and be constructive.
This one sounds as the worst "failure", but in general, hanging a book case off the wall is hard even for experienced professionals: books are notoriously heavy, and walls are of vastly different constructions, so sometimes, hanging it up is simply... impossible (eg. with a drywall if you can't find the drywall frame behind, or if that is too weak).
When I did remodelling of my place, I've planned for steel support behind wherever I wanted to hang heavy items (like a double vanity sink unit [people also lean on them], book cases, TV with a wooden panel behind it and similar). And you need to use special screws for different wall types and load (concrete anchors, wall/rawl plugs, toggle bolts, drywall anchor plugs... — though my English names might be off for these :).
So in short, don't hold this one much against yourself: it's sometimes hard even for seasoned pros, let alone hobbyists. I am just a seasoned hobbyist that's a sucker for hanging items (or actually, having clear floor to clean).
Anyway, the thing that attracts me to woodworking (and previously, chipboard cabinet construction) is that you get to make your own ideas: just like with software. But building stuff is not limited to software development or woodworking, and while there are plenty of software engineers enjoying woodworking, there are other ways to enjoy building your own stuff, and some might even enjoy not building anything after they've been doing it for 8+ hours a day.
If you need another tool or another component you can just search for it on the internet and if it's available you can have it in seconds. No trips to a shop that may or may not have what you need, or queueing, or explaining what you need to a shop assistant who couldn't really give a shit, or being upsold on some other thing that you don't really need or understand, etc.
Also, crucially for me personally, there's no mess that needs to be tidied away before the rest of the family come find you. There's no storage area needed for half-finished crap, odds and ends you can't decide if you need in future, potentially dangerous power tools, that kind of thing.
Building software is like taking all the fun parts of DIY and leaving all the boring / dangerous / physically taxing parts behind, and you can pretty much do it wherever you have a power supply and internet connection. That's why I first loved it and why I continue to do it today.
There is always an undo, just get another board.
> Building software is like taking all the fun parts of DIY and leaving all the boring / dangerous / physically taxing parts behind, and you can pretty much do it wherever you have a power supply and internet connection. That's why I first loved it and why I continue to do it today.
I have a different point of view. The software you build is ephemeral. You can't show it to someone. The architecture and the beautify of it's interplay is hidden and it's art is only available to you. I can show you my dovetail and let you feel how smooth the finish is. It's real. You can explorer it with your senses.
So one more good reason not to do any woodstuff at home when I can work with perfectly predictable things like the rust borrow checker instead :-)
We must be dealing with different codebases
They usually offer classes if you don't want to start yourself. But you can learn a ton by looking up cabinetmaking or something else on Youtube. For a real trip, watch joinery -- it's mesmerizing.
Other than that, I started by just picking up a saw and going to town, and quickly googling "How do I" to find out much more than I wanted to know. It pays to learn about the basic tools first. Table saw, Router table, Chop saw, Drill press, etc.
He focuses heavily on using hand tools instead of machines, so much more suitable for apartments. He's also budget conscious, and tries to show ways of achieving things without spending a ton on lots of expensive or specialised tools.