3 ms·

What is it with the intersect of coders and woodworkers?

by lwigo 6y ago

sleavey 6y ago
I wondered that too until I started woodworking. A fairly substantial part of it is pretty scientific - you have to propagate measurements and angles between cuts and joints and think ahead about how things fit together. It's related, in a very abstract sense, to the sort of problem solving involved in programming.
datahead 6y ago
Interesting presentation that explores your question. +1 intersection from this commenter. Tim Ewald - Clojure: Programming with Hand Tools https://www.youtube.com/watch?v=ShEez0JkOFw https://www.youtube.com/watch?v=ShEez0JkOFw
oh_sigh 6y ago
I don't think it just coders, I think it appeals to a lot of people who do a non-physical process for their job. It's nice to be able to build something physically with my hands, and not just edit a giant software codebase that makes some pixels change colors and conveys information, but otherwise has no physical world consequences.
dlisboa 6y ago
I like woodworking because to me it's the opposite of coding. Software is pretty complex and hard to explain to people. Concepts are abstract, changes are incremental and it's never really "done". Even if part of it is beautiful, in some short time it'll be outdated and replaced by something else. Woodworking, on the contrary, is something concrete I can touch and hold on my hand. It has practical uses, people can appreciate it and judge its form and function. If done even moderately right it'll last many years or decades. It's really rewarding to be able to point at something you've done yourself, mistakes and all, and see it in daily use. The feeling lasts a whole lot longer than "I've refactored this class into something better".
moistly 6y ago
In coding, making mistakes is expected and correctable. The challenge is often akin to solving a puzzle. You have a general idea of the shape of the solution, but it usually isn't laid out as a blueprint. The work is almost entirely mental. The challenge is intellectual. In (fine) woodworking, making a mistake is far more punishing. You have a blueprint, not a puzzle. The work is as much physical as it is mental. The challenge is in setting up and executing a series of cuts, shapings, sandings, and finishings with perfect precision. There are few correctable mistakes: material can be removed but never added, joinery must mate perfectly else it's useless, blemishes in the finish are extremely difficult to remedy, etc. I think a lot of coders tend to be perfectionists, wanting to be certain that their end product generates correct results and irritated to the point of obsession when it doesn't. I think fine woodworking feeds into that same perfectionist drive, and in an even more challenging way.

What is it with the intersect of coders and woodworkers?

by lwigo 6y ago

What is it with the intersect of coders and woodworkers?

I wondered that too until I started woodworking. A fairly substantial part of it is pretty scientific - you have to propagate measurements and angles between cuts and joints and think ahead about how things fit together. It's related, in a very abstract sense, to the sort of problem solving involved in programming.

datahead 6y ago

Interesting presentation that explores your question. +1 intersection from this commenter. Tim Ewald - Clojure: Programming with Hand Tools https://www.youtube.com/watch?v=ShEez0JkOFw https://www.youtube.com/watch?v=ShEez0JkOFw

oh_sigh 6y ago

I don't think it just coders, I think it appeals to a lot of people who do a non-physical process for their job. It's nice to be able to build something physically with my hands, and not just edit a giant software codebase that makes some pixels change colors and conveys information, but otherwise has no physical world consequences.

dlisboa 6y ago

I like woodworking because to me it's the opposite of coding. Software is pretty complex and hard to explain to people. Concepts are abstract, changes are incremental and it's never really "done". Even if part of it is beautiful, in some short time it'll be outdated and replaced by something else. Woodworking, on the contrary, is something concrete I can touch and hold on my hand. It has practical uses, people can appreciate it and judge its form and function. If done even moderately right it'll last many years or decades. It's really rewarding to be able to point at something you've done yourself, mistakes and all, and see it in daily use. The feeling lasts a whole lot longer than "I've refactored this class into something better".

moistly 6y ago

In coding, making mistakes is expected and correctable. The challenge is often akin to solving a puzzle. You have a general idea of the shape of the solution, but it usually isn't laid out as a blueprint. The work is almost entirely mental. The challenge is intellectual. In (fine) woodworking, making a mistake is far more punishing. You have a blueprint, not a puzzle. The work is as much physical as it is mental. The challenge is in setting up and executing a series of cuts, shapings, sandings, and finishings with perfect precision. There are few correctable mistakes: material can be removed but never added, joinery must mate perfectly else it's useless, blemishes in the finish are extremely difficult to remedy, etc. I think a lot of coders tend to be perfectionists, wanting to be certain that their end product generates correct results and irritated to the point of obsession when it doesn't. I think fine woodworking feeds into that same perfectionist drive, and in an even more challenging way.