masonicb00m

When the major tech companies use a piece of infra, it’s likely they have a good reason. Here are some.

- not necessarily using/in control of db - audit log of who toggled which features and when - reporting on users exposed to each feature - A/B test support - toggle features without touching production database - ...

A slot machine is a “one armed bandit”.

I built an Nginx plugin to do something like this https://github.com/masonicboom/ipscrub

RMS has impressive convictions, but unless you've given up your cell phone because of his views, his thoughts on Bitcoin probably aren't applicable either.

Debasement.

There are people who have a bad experience and they complain about it on the internet. Nothing wrong with that. I'm just adding the opposite data point.

I have interacted with Apple’s app reviewers for years and never experienced what you’re describing.

It’s a great story. Congrats to Qualtrics!

It’s great having a case that fits correctly! Makes such a difference

Thanks. I didn’t realize Blender did bode graphs—I’ll have to check that out.

I’ve been using ImageMagick but the CLI invocations are pretty awkward. Maybe I’m just looking for a DSL on top of ImageMagick

Scientific proof of the need for DND Shades (http://dndshades.com)

“After devouring nearly as much energy as all of Iceland’s households combined, Bitcoin miners may be about to return something to the community that’s housed them.” Implication is that the miners do nothing for Iceland? Seems unlikely. They’re probably incorporated businesses paying taxes and injecting wealth into local economy through payroll and other expenses. Why is Bloomberg anti-bitcoin?

Great work! Having access to this scale of computing for so cheap really is amazing

Where do you get your demand information?

John Carmack's attention to quality and detail is incredibly inspiring.

If you need stable links then buy yourself a domain or use a URL shortener that you can update. Might be wise to also provide content hashes of the data you're referencing in your paper.

The cool thing about git is it doesn’t matter what happens to the platform. You can take your repo and push it somewhere else if you don’t like how Microsoft runs the show. Given how Microsoft took Github’s idea with Atom and ran with it to make VSCode, I wouldn’t be surprised if Github improves under Microsoft’s rule.

I second eliminating the one year cliff. This is becoming market-standard. And not just for the employee's benefit. It's a lot easier to tell management their heads are up their asses when you're vested. Good for the company.

It can be helpful to find yourself a business partner. They provide a feeling of obligation and camaraderie that helps you to get going and keep going through the tough parts.

がんばってね！

Ah. Like Linux, I guess. Thanks for the info.

What was bad about arc4random?

Try DND Shades (http://dndshades.com). Much more explicit than headphones.

I can’t wait for dark mode. Awesome

I used to wear two at a time as a kid :P

Have you seen https://www.gq.com/story/watch-of-the-week-casios-neon-core-...? I had one once and wore it till it broke. Great for 80’s nostalgia

How has no one mentioned the best part of QBASIC??? The question mark character character is a shortcut for inserting a PRINT statement. <3

Great job on SUPERHOT! All the smashed monitors are worth it ;)

I hear your point that phrasing in terms of angles may be more understandable.

The x-axis in my plot shows the ratio of lengths of the longer to the shorter of the two non-hypotenuse sides (yes, typing this out it does sound convoluted). This ratio is 1 when those two sides are equal length, which implies that the two corners are 45°. So the plot does show that the return to cutting corners is maximized at 45°-45°-90°, but indirectly.

It's not an arbitrary decision that the graph only covers half the angle range. That's a consequence of the decision to label the shortest side "a" and the longer one (non-hypotenuse) "b". If those labels were applied to specific sides then you could explore the full angle range, but it would be redundant. I'm open to the idea that people might find this easier to understand though.

I think the natural way to refer to the sides of a triangle is by their length, which lead to my formulation. If you feel like plotting your formulation, here's my source code (in R): https://gist.github.com/masonicboom/dafeb49b3c1d4c44998969ef....

Cheers!

Thanks for the feedback. I included that much range to show the limit. I have a plot with truncated range that I skipped including for brevity. Maybe it’s worth throwing back in.

Maybe so. Does your method give a way to plot the function over the full range of values though? I think that seeing how the gains fall off is as interesting as computing the best case.

At least on macOS, screenshots are PNG. Does Windows make JPEGs?