![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
We bought a table saw. We bought it for a specific purpose where a hand-held power saw would just not cut it. We did the job, put the table saw away and mostly forgot about it.
We set it up again recently and searched out some learnings on its use. Jon Eakes videos are a good start, but that's epic amount of stuff on Youtube. After a while, you'll get overwhelmed by the sheer number of jigs people have built for particular tasks.
Kind of like jQuery libraries.
The thing is, even once you know how to do various things on the table saw in an abstract sort of way--practising a crosscut on a piece of scrap is pretty abstract--you still don't use the saw much.
What you need to do is change the way you think about doing a job. You need to get used to what the possibilities are, so at the planning stage you can make decisions you can carry out. If you never had a took that could cut a mortise and tenon, you might not think of that kind of solution.
This is exactly the same learning curve with programming. Until you know how to think as a programmer, all you're doing is writing code to fit an existing template you've been shown.
It's getting the mind reordered that's the long up slope of the learning curve.
(I think I just made an argument for site design including people who understand both the front end and the back end working together.)
We set it up again recently and searched out some learnings on its use. Jon Eakes videos are a good start, but that's epic amount of stuff on Youtube. After a while, you'll get overwhelmed by the sheer number of jigs people have built for particular tasks.
Kind of like jQuery libraries.
The thing is, even once you know how to do various things on the table saw in an abstract sort of way--practising a crosscut on a piece of scrap is pretty abstract--you still don't use the saw much.
What you need to do is change the way you think about doing a job. You need to get used to what the possibilities are, so at the planning stage you can make decisions you can carry out. If you never had a took that could cut a mortise and tenon, you might not think of that kind of solution.
This is exactly the same learning curve with programming. Until you know how to think as a programmer, all you're doing is writing code to fit an existing template you've been shown.
It's getting the mind reordered that's the long up slope of the learning curve.
(I think I just made an argument for site design including people who understand both the front end and the back end working together.)
