timhh

13 ms·

121.
by timhh 4y ago
Yeah. In fairness someone did link a method that I think could my lock (and this one). Basically you attach a laser to it so you can very accurately tell how far the key turned. That gives you a way to test the pins even though you can&#x27
122.
by timhh 4y ago
The only one I've seen was the Bowley lock. But yeah I sent my unpickable lock to him and he never mentioned it. :( https://youtu.be/7hUonUE1hEY
123.
by timhh 4y ago
Yeah same idea behind my lock too: https://youtu.be/7hUonUE1hEY I'd guess many many people have had this same idea.
124.
by timhh 5y ago
Yeah exactly. I had 20 samples from our codebase that showed some representative differences and you had to click on which one you liked more. The order (Black/YAPF or YAPF/Black) was randomised. I also had to turn off Black'
125.
by timhh 5y ago
In my experience it's better to just bite the bullet and do it. Eventually you will do it, so you either screw up git blame for a small codebase with a small amount of history, or wait until it is a large codebase with a large amount
126.
by timhh 5y ago
I did a blind survey of YAPF vs Black at my work. The results came back as 70% in favour of Black. Black gives generally nicer output, and also more predictable output because its folding algorithm is simpler. YAPF uses a global optimisat
127.
by timhh 5y ago
Thanks! I haven't really tried that way of working - mainly because it feels less clean (more complicated history), especially if you want to keep your feature split into a nice sequence of small diffs to make review easier (I think so
128.
by timhh 5y ago
I work on a fast-moving repo and got fed up with constantly pulling master and rebasing all my branches manually, so I made this tool to do it for me. It was surprisingly complicated!
129.
Show HN: Automatically Rebase Branches onto Master(github.com)
5 points by timhh 5y ago|4 comments
130.
by timhh 6y ago
> they can be equal Ha, funnily enough I did think of that, but I was trying to keep the explanation short and simple (and a bit hand-wavy). > 1/2 is positive. As is 1/3 Oops, fixed, thanks!
131.
by timhh 6y ago
I have thought about it, but I always worry about making large edits to Wikipedia pages that I'll put a lot of work into it and then someone will come along and just revert it. Maybe that fear is unfounded - I'll put it on my (ver
132.
by timhh 6y ago
Oops! I added brackets, thanks!
133.
by timhh 6y ago
This is an explanation of the fast inverse square root that I hope is easy to understand. I also managed to improve on it a little bit.
134.
Fast Inverse Square Root(timmmm.github.io)
294 points by timhh 6y ago|96 comments
135.
by timhh 9y ago
> Bkav simply scanned a test subject’s face, used a 3D printer to generate a face model, and affixed paper-cut eyes and mouth and a silicone nose. Ah yes, simple as that! > a BBC reporter’s twin brother was able to access his account