Cusotm Cut Nails- a Tip
Bill Tindall, E.Tn.
The nails that go into brad nailers make dandy cut nails. they can be nipped to any desired length. They have a glue coating on them so they hold tenaciously.
Knowledge You Can Build On — Est. 1998
Cusotm Cut Nails- a Tip
Bill Tindall, E.Tn.
The nails that go into brad nailers make dandy cut nails. they can be nipped to any desired length. They have a glue coating on them so they hold tenaciously.
Great tip. Thanks.
Re: Cusotm Cut Nails- a Tip
William Duffield
They're incredibly less expensive that the reproduction cut nails, and once driven into the moulding, who can tell?
Perhaps, the best tip is the one in your photo, but not in print. If you can't keep the tool with the hardware, at least write down on the hardware the tool you need to use that hardware. While my nippers, hammer and nailset are easy to find, and it's obvious which ones I need to do a particular job, remembering the drill size, or figuring it out again if I don't remember, can be a real waste of time, and I now know I will forget, every time. I learned that the hard way. Using a Sharpie pen, I also write down Allen wrench sizes on the machine right next to the cap screw or set screw, If I can't find a rare earth magnet and a spare wrench in the right size that I can leave in place. On jars of screws, for example, I write down the driver head type and size, the countersink size and of course the screw size and length. For bolt heads and nuts, I write the hex wrench size on the machine. There's nothing more frustrating than walking across the shop and returning with a half inch wrench and then finding out I really need a 12 mm.
Failing memory
John K Jordan
I thought it was just me with the failing memory. I write the air pressures and lug nut wrench sizes on the side of my tractor and my woodturning notebooks have every drill size I used next to the sketch. This has saved me so much reinventing time!
JKJ
Re: Failing memory
TomD
Indelible markers are great.
I guess we all have failing memories, but the mind is like the hard drive, an exponential requirement for storage, not linear, each new facts eventually draws in more facts to support it. Who would have ever thought one could fill 1 T drives.
I was reading up on a sail design program that was designed originally for a 256 K RAM computer. Hard to imagine you can design a 3d sail on that. Not sure the modern programs do anything different for being memory hogs. At the end of the day you either get plots or instructions to a ploter that cuts parallel sided cloth into cloth with one curved edge.
Re: Failing memory
John K Jordan
>>I was reading up on a sail design program that was designed originally
>>for a 256 K RAM computer. Hard to imagine you can design a 3d sail on that.
It is surprising what little memory it takes and how fast software can run when written efficiently. In the '70s I wrote 3d software in assembler that fit in maybe 20k of memory. Inputting coordinate data defining a small "world" of 3d objects, I built a dual joystick controller to fly through the data, rotate, zoom, etc. The software would interpret the joystick positions as a viewpoint vector, process all the transformation matrices, and draw all the objects with perspective and clipping on a b&w memory mapped display. (Essentially a flight simulator without the physics.) Running on an incredibly slow (compared to today) 2 mHz Motorola processor, I got a smooth 6 frames per second display!! This was incredibly exciting.
(BTW, my computer had a whopping 56k of memory - each 8k board was a $250 kit with 1434 solder connections. At those prices, the memory in today's laptop would cost a fortune and need an electrical substation for power. My first floppy disk drive was $2300. Things have changed.)
Unfortunately software today is bloated by enterprise development systems and bored clueless programmers pasting together huge, inefficient do-all libraries to do the hard work. I saw the start of this in the 80s and 90s and it gets worse every year. The day of the software wizard is long gone. :-(
JKJ
Re: Failing memory
Barry Irby
John, more than thirty years ago I had a friend who "operated" a satellite. Sort of like being a fireman. Nothing to do until it drifted out of position or something, then work like a madman until it was fixed. He got eleven masters degrees at their expense while waiting for the satellite to goof up. He wrote some programming for early cruise missiles. He carried a brief case with a number key pad in it. His explanation was that he programmed in machine code directly without using a language and running it through a compiler. Claimed the on-board computers of the day were too slow to process the language unless it was in machine code. Every once in a while he would get an inspiration, whip out the brief case and type away like a drunken accountant on the number pad and then put it away. Given a chance he would talk for hours about how it worked, but I did not understand any of it. He may have been the best BS'er ever.
Re: Cusotm Cut Nails- a Tip
Barry Irby
Bill, this is a great tip. I agree with the others about labeling things, as a great idea. I sometimes attach tools like Allen wrenches or specialized screw drivers to the piece of equipment.
A question. You mentioned the glue. I thought the glue was melted and activated by the friction of driving them at high speed. Are you convince it contributes to the holding power when hand driven?
Re: Failing memory
John K Jordan
Barry, I suspect your friend was on the level. He sounds very much like a guy I knew who wrote satellite tracking software.
Writing in machine code used to be very common. You actually wrote in "assembly" language which was just a way to put labels like MOV or JMP on the hex (binary) numbers the processor executed directly. An assembler program turned the letters MOV directly into the machine code. A compiler takes code written in a high level language (such as C or FORTRAN) and might turn a single line like "XTOT=XTOT+SQRT(INP)*3.14159" into a whole bunch of machine code. Assembler is absolutely the best way to squeeze the maximum performance and function into the smallest space (IF you are good at it!) but it takes a lot of skill to write. Code in a high level language is so much easier and quicker to write but can be less efficient, although today's compilers are far better than what we used to work with. A good programmer might write most of his code in a high-level language for a compiler but "hand code" critical routines in assembler.
I too would have talked the ears off of anyone who stood still long enough! But I gave all that up for driving the tractor, feeding horses, shearing llamas, processing honey, growing cushaws, and feeling sorry for the people I see driving to work every morning. :-)
JKJ
yes
Bill Tindall, E.Tn.
Are you convince it contributes to the holding power when hand driven?
Don't screw up. they are almost impossible to pull out.
Re: yes
Barry Irby
Somewhere I have a brad pusher. Worked well. Do you use something like that or a hammer and nailset?