HNHacker News
TopNewBestAskShowJobs

unholiness

1,306 karma · joined August 20, 2013

submissionscomments
unholiness··on Ellen Pao: My lawsuit failed. Others won’t
Just so that people can get a fair view and not judge from a cherry-picked post, here's a link to the top part from this month[0].

It's a pretty broad sampling of: - Laughing at fat people - "I hate this bitch in this picture"-style hatred - A post literally pointed at the victim at Charlottesville, "exposing the truth" that she was fat, saying they "wonder why" she died.

And in my memory, /r/fatpeoplehate was much more toxic than this at the time it was shut down.

[0] https://voat.co/v/fatpeoplehate/top?span=month

unholiness··on TypeScripts Type System Is Turing Complete
Turing complete systems are highly capable, and thus, are harder to prove anything about. The halting problem notwithstanding, there's first the "there are things that don't halt" problem: that is, you can write a valid TypeScript program that will never finish compiling.

Now, this really shouldn't be an issue unless someone is deliberately abusive. Java's generic types are also Turing complete[0], and it hasn't been problematic. Just because an abusive program exists doesn't mean it will be written.

But who am I kidding... this is the JavaScript community. I'll give it 2 weeks until someone releases a framework allowing you to write functions that don't compile unless their input is a prime number.

[0] https://arxiv.org/pdf/1605.05274.pdf

unholiness··on App sizes are out of control
It's true, Java bytecode was basically designed for small size. The goal was to transmit java apps quickly over the internet, a hope which mostly died off as JS took over, but which in some ways has been reborn with android (dalvik bytecode is somewhat different but is definitely small). The main tradeoff for the small size is a total lack of optimization until the JIT compilation stage.

But there's no way it's anything like a 10x difference. There's definitely something else going on here, like some quirk about how the app store is calculating the sizes of assets.

unholiness··on Discovering an Equation for Altruism Cost George Price Everything (2016)
The article is interesting and biographical, but for those not interested in biography:

The Price Equation[1] simply states that the change in a trait due to natural selection is proportional to the covariance between that trait and it's impact on "fitness" (survivability). The link to altruism is that the equation applies to a whole population, not just an individual. So, spending time and energy to help your kin can increase evolutionary pressure for your traits, so long as the gain in utility from the resource transfer is larger than the genetic difference between you.

The equation is useful and accurate, though not incredibly insightful. From the article: It is like a footballer who, when asked how their team will win the next match, says they will score more goals than the other team. By trying to explain the game at its most fundamental level, say the critics, the equation explains and predicts nothing about why certain traits should increase or decrease fitness.

[1] https://en.wikipedia.org/wiki/Price_equation

unholiness··on Password Typos and How to Correct Them Securely (2016) [pdf]
The friction isn't about the workflow when the system just works.

There are gains to be made in situations where I'm using another computer, or my phone, or the password manager isn't recognizing the site properly, or isn't finding the right the input fields.

But mostly the friction is in front of all those users who don't use password managers. There are gains to be made in making the setup process simple, secure, and predictable. There are gains in making it cross-browser, cross-platform, and well-integrated with the setup process for browsers and operating systems.

Users "don't want" most things, until a lot of thought and effort gets made to create a wholistic solutions that just work.

unholiness··on Password Typos and How to Correct Them Securely (2016) [pdf]
Real users have passwords that are simple mutations from passwords they used elsewhere. They'll change a 1 to a 2 to make it unique and safe, or change an o to a 0 to fulfill the next site's requirements.

I don't buy the idea that being typo tolerant only helps the real account owner if it's also opaquely increasing the amount of password reuse across sites. Not to mention that the code handling the typo comparison is a pretty large new surface area for attack, all in the name of optimizing the experience for typing passwords by hand (a practice we should actively reduce).

unholiness··on Harmony Explained: Progress Towards a Scientific Theory of Music (2014)
By "music theory books", I believe the author means "Literature which attempts to explain biologically why harmonies sound pleasant". My experience with this is that

1) Much of this literature is indeed in inside books which also discuss the "cookbook" parts of music theory, and

2) It's shocking how much incorrect, unscientific nonsense there is in these texts, and

3) There's nothing close to a scientific consensus about why humans and animals nearly universally feel good when hearing harmonious sounds.

The author is attempting to answer that question, and I think his initial complaints are perfectly valid.

unholiness··on Harmony Explained: Progress Towards a Scientific Theory of Music (2014)
There's a nature and a nurture to how we perceive music and harmony.

Nature is the aspects of harmony that independent societies have all agreed upon, likely due to an unknown biological reason harmony sounds pleasant. Nurture is the connotations society and culture put on top of that.

The author is only attempting to explain the nature part of things.

You wouldn't fault the theory of gravity for not explaining cell biology, so let's not fault this guy for ignoring culture.

unholiness··on Harmony Explained: Progress Towards a Scientific Theory of Music (2014)
True!

I won't risk getting out of my depth. My comment was simply saying there are unique nerve signals from unique points across the cochlea which uniquely convey the information "this frequency is currently being heard at this volume". To say that that information is what we perceive... that's not an argument I'd make. But it is a step along the process.

Everyone knows we "see" in rgb, but few people seem to know we "hear" in frequencies more than we "hear" in waveforms. That's my point.

unholiness··on Harmony Explained: Progress Towards a Scientific Theory of Music (2014)
Hypothesis is different from evidence. Your arguments roughly address the phrasing of my summary but don't back the full scope author's actual conjectures.

1, for instance, is not philosophical. He's literally carrying the metaphor down to additions and multiplications of waveform samples. There's no evidence that this is mechanistically similar to how our brain thinks, nor is there evidence that "easy" problems of addition are easy problems of our mind.

2 is an argument of strong evolutionary force... strong enough to overcome the fact that my emotional reactions to harmony will change my behavior, despite them not being a good signal of how to survive

And the rest is pure conjecture. I'm not saying it's a bad hypothesis. It's just not anything beyond hypothesis.

unholiness··on Harmony Explained: Progress Towards a Scientific Theory of Music (2014)
The author starts out by complaining that current music theory is not scientific. I completely agree. The field is astoundingly full of technical-seeming, well-accepted textbooks containing a biological "explanation" of harmony that is either totally unproven or trivially false.

But then he precedes to dive into a mountain of unsubstantiated conjecture, saying:

1. Our brains are just computers

2. Evolution motivates less computation

3. Finding the fundamental frequency of a sound is worthwhile

4. Doing that is computationally easier if all other frequencies are in harmony

5. That is what has lead to harmony giving us pleasure

(The rest is essentially fluff around this core argument)

It's a nice theory, but there's nothing to substantively back up any of these points. He comes the closest on point #4, but only by making strong assumptions about the flavor of #1. The whole thrust of his argument is just totally tangential to addressing his initial complaints about the lack of science and rigor within the subject of biological harmony.

-

One thing he does get right is avoiding most common mistake that textbooks and laymen alike think about hearing: Our ears do not perceive the waveform of sound directly (for the most part[1]). Rather, we perceive sympathy vibrations at different parts our cochlea, rather directly sending nerve signals according to the Fourier transform of the original waveform. This can be measured (scientifically)!

This Vi Hart video does a remarkably good job at giving a layman's tour of our some of the phenomena in our ears: https://www.youtube.com/watch?v=i_0DXxNeaQ0

[1] If this were totally true, we wouldn't be able to perceive phase at all! But it is the case that these sympathy vibrations are perceived with much more sensitivity than our perception of phase, and are linked more closely to peoples' idea of harmony.

unholiness··on Auto-Play Policy Changes for macOS
The article later clarifies: A video with a silent audio track will be blocked from autoplay. A video without an audio track or a muted video will not be blocked.
unholiness··on Fireflies
"Speeding up" would only happen when you turn nudging on, it wouldn't continuously keep getting faster.

But the algorithm described by the author has a bigger problem: It wouldn't actually sync the fireflies!

If EVERYONE nudged their clocks forward, then an out-of-sync firefly would be nudged the same as an in-sync firefly, and synchronization wouldn't increase over time!

Your rule avoids this problem:

> If you see a neighbour nearby flash, when you are not flashing, nudge your clock forward by a bit.

If you look in "show clocks" mode, it looks like this is exactly what is implemented.

unholiness··on Machine Learning Gender and Racial Biases from Language
Did you read the article on the study you're criticizing?

> The formula was particularly likely to falsely flag black defendants as future criminals, wrongly labeling them this way at almost twice the rate as white defendants.

The algorithm did not just say black people are more likely to arrested, it said black people were more likely to be arrested than the future data revealed. The algorithm was wrong, and it was wrong even if you take the demonstrably false position that being arrested is the same thing as committing a crime, ignoring the blatant and harmful biases in police behaviors already.

Given that this algorithm is being used to inform sentences by judges today, this is absolutely appalling.

The broader problem is that algorithms have imperfect signals to work with, and given those signals, it's easier to figure out someone's race than it is to figure out your attitude toward crime, so the algorithm overfits to the data it can see. This exacerbates the problem in a positive feedback loop, and we absolutely need to be cognizant of the damaging implications of this.

unholiness··on Ask HN: Do you still use browser bookmarks?
I'm surprised no one's mentioned the chrome feature that's mostly replaced bookmarks for me.

Just like aliasing commands in the terminal, you can alias web pages in Chrome's address bar. So, when I type "je" in my omnibar it has an autocomplete option "Jenkins", and pressing enter will take me to the URL I set for the Jenkins home page.

This feature is poorly named "search engines", and yes, it is extensible to putting extra strings at the end of that URL (which could be registered as a search term within that site), but I've been using it for years, and 99% of my use is simply mapping arbitrary strings to arbitrary URLs. It works amazingly for that. No mouse movement digging into bookmark folders required.

http://lifehacker.com/5815291/create-short-aliases-for-frequ...

unholiness··on How do you make programmers work 60-80 hours per week?
Yeah, I hear a lot of people saying essentially "40 hours is the most anyone can be productive for in a week". My more realistic rule of thumb is that people can tolerate maybe 20-30 hours of doing things they don't intrinsically care about.

So, if you give a shit about 20% of your job, and your job tolerates you doing personal stuff (slash miscellaneous browsing) for a few hours a week, then sure, 40 hours can be sustainable. On the other hand, if this job is your passion, work is stimulating, and you've got things you feel positive ownership over, then having 60-80 hour work weeks isn't necessarily unhealthy (so long as you're aware if and when those drives start to dwindle).

The other upshot of this theory is it dismantles argument that side projects hurt employees' productivity. The extra time spent pursuing your own passions simply isn't draining in the same way implementing others' ideas is. If anything, it adds motivation to the day-to-day stuff, knowing you'll learn skills at work that help the side project you really care about.

unholiness··on You have a right to know how much your coworkers are paid
Any attempt to "objectively" measure performance to influence salary will actively harm company culture. Unless your company is literally an assembly line, Godhart's law takes over so quickly and your employees are going to spend their time abusing the metric.

Just paying employees the market rate, while imperfect, is overwhelmingly preferable.

unholiness··on SHA-1 Collision Detection on GitHub.com
Interesting that it's hosted on GitHub. Everyone in this thread is wondering about the 2^-90 chance that a random commit will fail, but I wonder how these guys prevented their repo with test files from being rejected.
unholiness··on Windows 10 is bringing ads to File Explorer – how to turn them off
In browsers, ad blockers are being used more and more commonly for even non-technical folks.

In native apps mobile apps, there are some okay ad-blocking solutions.

But when the ads are baked into the operating system itself... I have a hard time seeing Microsoft or Apple losing the ad blocking battle.

So, instead of getting ads somewhat sandboxed inside a browser, in the future we may be getting ads inside the start menu, inside spotlight, on the toolbar... and instead of semi-directly funding content providers, the ad space will only ever be funneling money to the these same huge companies to spend as they see fit. Bleeech.

unholiness··on Snap Jumps in Debut After App Maker Raises $3.4B in IPO
Hmm. To me that just shifts the questions to the bankers.

If people (who don't know anything the bankers don't know) value the stock at $24, shouldn't there also be competing bankers willing to offer $20 a share for the whole lot, igniting a bidding war that converges roughly near the real price?

Obviously bankers need to make some money. But I don't see how this kind of deal has anywhere near a $1.4 billion dollar overhead, and I'm just boggled by the scale of the disparity.

unholiness··on Snap Jumps in Debut After App Maker Raises $3.4B in IPO
Economics novice here. How did we get such a huge difference (40%!) between the IPO price and the current price, when both sides had $3.4 billion at stake on getting that price "right"? Is there some huge information disparity here?

Moreover, if investors feel that $24 a share is a fair price, why weren't they swooping in before the IPO and, say, offering $20 a share for the whole chunk?

Sorry if this seems like a ridiculous question, but it seems to me like there should be some extremely large free market force (on the order of $1.4 billion) preventing the founders and employees from missing out on all that money. Am I wrong?

unholiness··on Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Reviews
A good thought!

My point was orthogonal, though. I don't want a reviewer directly making committed changes to my code, period. Giving me control isn't about preventing inadvertent calls to sedy. It's about handling when someone suggests a substitution that I don't agree with, or want to reword.

My mindset might be different from what Marmelab intends, but to me, code review is a conversation about the changes I'm responsible for making, not a google doc where anyone can change the content I'm about to push.

unholiness··on I am an Uber survivor
I agree, but for people to step up and complain, there needs to be a system around them that supports it.

The crazy part about these stories is not that Uber has a few awful people, and it's not that there aren't people who will speak up and complain. The crazy part about these stories is that HR seems to be systematically supporting the few awful people and antagonizing the people who speak up and complain.

unholiness··on Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Reviews
Cool! Looks like a genuinely useful tool, reducing some pretty common friction within the code review process.

Three features I'd want before using it:

1) Rather than triggering Sedy immediately on a reviewer comment, I'd like the trigger to be the original requester reacting to the comment with a thumbs-up. The requester knows what they're trying to say, and they should decide if the changes get made.

2) I wish there were an option to restrict it to comments for supported languages. Your examples are just changing markdown (not code), and I think rightfully so — I can easily see this tool becoming a way for a senior dev reviewer to attempt to avoid the back-and-forth with a junior dev by just posting some complex code substitutions... substitutions which could easily screw things up.

3) sed replacement actually seems too powerful for this job. For instance, if I want to make a replacement like:

    s/**bold** thing/**bold thing**/
...I really don't want to try escaping that without feedback. I'd rather have direct string replacement without regex than the full power of sed. This probably goes against your design goals, but for me it would be much more useful.
unholiness··on Why does e to pi i equal -1? (2015) [video]
The Maclaurin trick is what I'd call the "standard proof", and I think it's the source of a lot of the lack of intuition surrounding e^i... It's exactly what you call it, a "trick", where you prove two rabbits are identical by transforming them both into an infinite number of hats.

On the one hand, it's all sound logic and algebra, but on the other hand, I certainly don't blame Randall Munroe for seeing that proof in high school and going on to say "I have never been totally satisfied by the explanations for why e to the ix gives a sinusoidal wave."[0]

[0] https://xkcd.com/179/

unholiness··on Why does e to pi i equal -1? (2015) [video]
Of course! I think there's a good reason (1) is the first definition of e^x we get in school, though. I don't think it's the most "natural" definition, but I think it's the most grok-able. It's easy for high-schoolers to learn precisely _because_ each part of it is so intimately familiar that it's clear without hand-waving precisely what everyone's talking about.

When we then step into viewing real exponentials as "The thing that gets bigger at a rate proportional to where we're at", it's un-abstract, which is honestly important for intuition. Of course you're going to want to then view it with the calculus definition, or as a matrix, or as an operator... But I wouldn't start there.

So I feel the same about the complex version. There's another nice proof in this thread that starts with the calculus definition and follows a similar track. It's a much more beautiful proof! But I worry some will lose intuition when we start the conversation with "a complex exponential's rate of change is perpendicular to its position"...

That said, if I were to ever teach a math class on complex numbers, I think fleshed-out versions of these two 4-step proofs are the ones that together best build intuition for what "rotation in complex exponentials" really means. That rotational aspect is the foundation of much of the handwaving done in control theory, DSP, ASP, signals and systems, and really anything involving fourier and laplace transforms. So, it's important to grok it well.

unholiness··on Why does e to pi i equal -1? (2015) [video]
This explanation strikes me as a little too aggressive in throwing out the notation with the bathwater, only reaching its result by redefining the terms we already have intuition for into space-stretching operations that don't work like arithmetic does in my head.

In that sense I think I have the same problem with this proof that I do with the standard one, where you add the Maclaurin series of cos(θ) and i * sin(θ) and match term-by-term with the series for e^(i * θ). The problem is, at the point you can actually show equality, the things on one side aren't obviously a rotation and the things on the other side aren't obviously an exponential.

I'm not just hear to yell at clouds. I was given a proof that I truly love by a professor I adore, which I think really does give insight into what all these operators are doing. The best video I can find with it is here:

https://www.youtube.com/watch?v=-dhHrg-KbJ0 (Skip to 7:30 if you're already comfortable with the limit definition of e^x)

The basic summary is:

1) e^iθ is equal to (1 + iθ/n) ^ n for large n

2) That base, (1 + iθ/n), plotted as a complex number, has length approaching 1, angle approaching θ/n

3) The base squared, (1 + iθ/n)^2, by de moivre's theorem, forms another point as if the transformation from (0, 1) were repeated twice — that is, the length stays one, and another tiny angle is added for a total of 2θ/n

4) The full result is therefore n transformations, taking the path along the unit circle, traveling θ and arriving at cos(θ) + i * sin(θ)

unholiness··on The closest I've ever come to falling for a Gmail phishing attack
> Password managers really shine at times like these

I agree on some levels, but password managers can and have had vulnerabilities[0] that can allow the gmail password to be populated despite the wrong domain. Given that the autofill adds legitimacy and reduces friction, it could make this particular scenario go from bad to worse.

[0] https://labs.detectify.com/2016/07/27/how-i-made-lastpass-gi...

unholiness··on “The Depressed Person” by David Foster Wallace (1998) [pdf]
I literally bought a Kindle of the sake of reading Infinite Jest.

I independently highly recommend both.

unholiness··on Ask HN: I don't enjoy being a CTO. Now what?
On the other hand, as a coder, working with a manager with little or no code experience is ineffective and frustrating. Having a manager who can wrap her head around complex architectures, and argue/negotiate for one strategy over the other is extremely important. Yes, so are team skills, but I wouldn't call the the path from coding to manager coders fundamentally flawed.
← PreviousPage 9 of 11Next →