skysight-inc/HackerNews huggingface dataset:
The beautiful girl crunch

For most guys in the bay area, the beautiful girl crunch is a bigger problem than the Series A crunch (this somewhat applies to designers as well). The difference in difficulty between dating a beautiful girl and an unattractive one is remarkable--I frequently hear guys say that for unattractive girls they can find multiple great candidates without really looking but can't find a single beautiful girl for a dating role no matter how hard they look.

First, of all the canonical terrible advice advisors give, being cheap is among the worst. I have never seen a hardup guy regret being generous.

For most beautiful girls, this is as much about fairness and feeling valued as it is about the money. And of course, if girls are going to turn down the certainty of dating a handsome, confident sales guy, they should get a reward for taking that risk.

If you’re going to look outside of your network of friends from your Defense of the Ancients guild (usually a mistake, but sometimes there are truly no other options), focus on recruiting girls outside of the valley.

Finally, most engineers are not willing to spend the time it takes to develop a normal social life with regular non-technical people whereas they might develop normal personality traits and meet someone nice. You can't outsource this though--you have to do it yourself.

Footnote: * Every time someone from the government asks me what they can do to help hard-up engineers, I always say a version of "The only thing you need to do is fix immigration for beautiful girls." We need more beautiful, financially desperate girls from third world countries whose standards are not as high as American ones.
Selfie360 Turns Your Face Into A Gif
Why would Google care (in a negative way) if you've done design work for Aol?
Wow, thanks for responding!

I'll give the Docker install a spin. I'll give feedback on the Gentoo install and the Docker install when I am able to give both my full attention.

Your blog posts are frequently thought-provoking and inspirational and mercilessly bullshit-free. I'm so glad you've moved to Ruby on Rails and welcome you with open arms into the open-source world, you may not fully appreciate how much goodwill that move generated for you :)
Where are people getting DeflataDollar? You've pitched it as a nearly constant-yield zero-risk investment. Circulation quickly falls to nearly 0, and we're back to having just Dollars (plus people who could afford DeflataDollars are watching their net worth grow without the shared economic benefits of a normal investment).
Switching off ignition is usually also done in software.

Many ECUs store data (user settings, logging and fault codes) to non volatile memory before shutting down so the key only sends a signal. It's not a hard switch. But it could still help if all other ECUs except the faulty does shut down correctly.
As an AI academic who used to have a bunch of game-AI industry contacts at big companies, my anecdotal impression is that a lot of people are indeed taking this advice. Either that or I'm unlucky, because my contacts are disappearing about as fast as I can make them...

A few are still doing games now, in the indie scene. The most interesting of those, imo, is Richard Evans (formerly of Black & White and The Sims 3), who's building an interactive-fiction platform on top of a novel logic-based social-simulation engine (http://www.versu.com). But a lot are doing entirely different things: some moved to "regular" programming jobs, ranging from simulation programming for big engineering companies or defense contractors (somewhat related) to almost anything at all that provides a regular job. A number have gone back to grad school. A few have become freelance consultants.

Imo it really stunts the growth of game AI as well, because there are remarkably few experienced senior AI devs who actually stay in the field, long enough to develop a sense of how to architect systems, how to interface with designers, and actually improve things over time.
that's is not fractional reserve banking. on top of that, yo required another currency (another risk), a requirement you don't need with the current system
Fine, I'll grant you Ada, and it does seem like a good language for these kinds of things. But you have to acknowledge it's not going to become a popular language for regular software projects.
Yeah, for example: PHP's accidental broken support for octal numbers is definitely the fault of all the people who use PHP, not a problem with the language.
average life expectancy

Age at death has a bimodal distribution: a huge portion of humans die at or near birth. If you survive that you're pretty likely to live quite a while, living well past the mean. That's 'cause all the deaths at infancy bring down the mean quite a bit.
Oh, that's how it works right now, with a twist. There's "anarchy" and "democracy" modes. To quote the channel readme:

TwitchPlaysPokemon now has two modes, anarchy and democracy.

Anarchy mode is the "old" mode, where everyone's inputs are applied immediately.

Democracy mode is vote-based and has a more sophisticated input system.

In order to switch from one mode to the other, the mode that isn't active needs 75% of votes as indicated by the dotted line, the current percentage of votes is indicated by the black line.

In democracy mode you can compile a sequence of inputs. left2 will move left twice, left2down2 will move left twice and down twice.

The "dotted" and "solid" line referred to are two indicators moving in a progress bar between "democracy" and "anarchy"
In my use cases escape analysis does not elide these accesses out (and I was unable to reason about why not). Further, I had an immutable map that had ~hundreds of items in it that was generating hundreds of millions of objects. I found that weird and terrifying especially given that I was specifically asking it not to give me Options back.

I frequently hear that memory/performance are "implementation" details and don't have bearing on functionality. For my use cases that isn't true.

Even if it was, the surprising upside down nature of that API (de reference the option, instead of wrap the reference) is of itself weird.

This is just the most terse example of oddities in the library I've encountered. Other's include streams being created (and not GC'd) when they weren't necessary, collections losing performance characteristics due to the monadic calls (IndexedSeq's passed into functions as Seq's use LinkedLists for builders instead of Vectors), etc.

Finally, I fundamentally disagree with the idea that eager evaluation should be the default in the collection library. Views mitigated this somewhat, but after working with more sane libraries, have to remember that every time is tedious (though I'll grant that is a debatable point).

If your software is not performance critical, or you aren't implementing your own collections libraries, maybe you don't encounter these problems. But for the standard library, it is a problem.
If you read between the lines, it's the classic case of investors knowing it's the best time to cash out for their ROI.
fractional reserve banking != loans
> But that manufacturing innovation hasn't been matched on the basic research side; it's been over a decade since the last time anyone set a new efficiency record for silicon cells.

> The material in question is gallium arsenide, which can be fashioned into solar cells with efficiencies twice those of silicon

What about this breakthrough doubling the typical solar panel efficiency to 44.7%? Isn't it based on silicon solar panels, too?

http://www.ise.fraunhofer.de/en/press-and-media/press-releas...
For some companies the standards are not entirely meaningful. Must have 3.9 GPA from an Ivy League school, know [obscure library] in detail, have experience in Scala and Lua and OCaml and Julia, as well as a deep passion for cricket. Then, once this person is found, they put them to work building a Rails CRUD app... There is some hyperbole here, but not too much.
We revoked those keys after making the video. :)
I tried that route to no success. My problem, back when I actually wanted to work in SV, was I found it to be an impenetrable bubble. There seems to be a serious delusion that any engineer worth a damn will move to SV of their own volition, so the only reason to look outside is to try to snatch the top talent from the top schools elsewhere.
Given the existence of a choice between deflating and a hypothetical alternative of a universally accepted stable risk-free store of value, it would be rational to prefer to receive the latter. It is still however, in my rational interest to prefer the latter to not exist at all. Being one of the large majority of people who aren't the unproductive uber-rich, I prefer that those that have far more dollars than me are more inclined to circulate them, creating far more opportunity for me to grow my share of national wealth (and absolute national wealth) than would exist if dollars were to be spent only when absolutely necessary. The corollary of your argument is that if we frame it the other way round, with StableDollar and other non-depreciating capital holders tending to hold more bargaining power than the general labour supply, they will be able to get away with paying only InflataDollars to the point where the level of StableDollars actually circulating in the economy will tend towards zero asymptotically...

In our actual system the ability to deposit InflataDollars into accounts with fixed risk-free positive returns (backed by expected and potential supplies of InflataDollars), the government keeping inflation low, and the government requiring you to pay tax on 30-40% of your income solely in InflataDollars ensures the demand for InflataDollars will never approach zero. In fact, it's much less likely to reach zero than the demand for Bitcoins, Freicoins or tulip bulbs, none of which anybody is obliged to use in any circumstances (at least not until Bitcoin-denominated debts become widespread and readily enforceable. If I wanted to design a cryptocurrency I'd focus on that aspect)
True. Any complaints are already the tip of an iceberg you can't see.

And the people complaining should be treated like your best friends: they cared enough to complain. Nobody else cared.
Meant? Meant by who? The people that use currency certainly don't want it to lose value. That's a cost to them. Something that loses value is never going to catch on.
That was implemented earlier today. Not quite like that but as a voting system to let the most voted command get inputted after 5-10 seconds. They can also vote to switch between modes which I think has definitely biased things to being a little less random, but it's made some users angry and had them voting "start9" to halt all progress by hitting the start button 9 times.
Indeed, the community contributed a screenshot based walkthrough here:

https://meta.discourse.org/t/beginners-guide-to-deploy-disco...
Angular.js: Introduction to unit test
You've said it more eloquently than I can, but I want to bring up that:

"results in many false negatives..." is not some universal truth.

Is there evidence that shows current software interviews turn down way too many great candidates?

There should exist a large enough group of developers who have been rejected a number of times[0], who have gone on to be very successful[1] in their careers. Does this data exist?

I agree that the current process isn't perfect, and it does produce some false negatives and some false positives. The amount which, has yet to deter me from beliving that the system works, as intended. Certainly there are some fringe candidates, who are turned away, but I don't think it's as onerous as people are making it out to be.

Also, most companies didn't start out with unlimited piles of cash, nor could they have their pick of employees. They had to work at it, and I don't believe the culture of their hiring has changed significantly.

For the record, I struggle with traditional coding puzzle interviews. But I also know coding on the whiteboard is a skill, which can be practiced, and with time, improved upon, such that if you are a really good developer, but struggle with passing interviews, you can deal with that problem by becoming better at interviewing.

Or you know, create something awesome, and never have to worry about interviewing again.

[0] Failing one or two interviews isn't really indicative of anything. So this group would require consistently failing multiple standard coding interviews.

[1] How to measure success? I say gone to be a major contributor to the success of a company, or built their own company that is considered "successful."
I've hired a number of engineers through agencies. It's a PITA because our incentives aren't aligned but I've found a few things to help. One is to be firm with recruiters and not to care about your relationship with them. In a place like NYC where there are hundreds of firms constantly trying to work with me I make it very clear what I expect of the recruiters. If they don't give it to me I move on.
Yeah, Phusion oversells their case when they say this is the "right way" to do it. It's one way to do it, and this methodology probably addresses customer support issues they are having. Many of their customers likely misunderstand what's actually going in a container by default.

I'd rather see a more balanced approach that shows a range of options, without opining so much about how Docker containers should or should not be used. Better to fit the solution to a particular use case.
Doesn't really affect this case though. Why does the numbers_to_ family need to produce HTML?
Cuff Blends Jewelry With a Wearable Alert System
I don't know if Matasano is a nice place to work at (well, friends there have been happy, so I guess I do have some information), but it sounds like a wonderful place to interview for. Enjoyable instead of actively painful and stress-inducing.

If someone doesn't make the cut, what does Matasano say? Do you say what didn't work out, or is it the industry standard and horribly antiseptic "we have decided not to move forward at this time"? I'd understand the latter, but if there's a place breaking that mold, I think it might be you guys.
tl;dr:

There's no engineering crunch, just companies that don't want to pay market rates.

The Free Market from startup/VC perspective: It works when we profit, but when we want to hire cheap labor it's because there's not enough people.
Well, a treaty is between nations and the Native American had agreements between tribes (and trade) before the Europeans showed up. The European (and later US) treaties were not a new concept, just a new form and some new, particularly scummy, tactics.
I have never seen a startup regret being generous with equity for their early employees.

A few years ago, Zynga told some early employees with lots of shares that they had to give back some of their stock or they'd be fired:

http://news.cnet.com/8301-13506_3-57322150-17/zynga-to-emplo...

http://finance.fortune.cnn.com/2011/11/10/zynga-stock-scanda...

I'm not sure if that qualifies as "regret", or if it's just greed, but it's one very public example of a company deciding they've given too many options to early employees.
The casual users I know who have been exposed to Windows 8 have uniformly had the reaction "WTF?", often violently and expletiveladenly expressed.
There's a beautiful irony there, the best thing that bitcoin has going for it is the very same thing that's keeping it from being useful as an actual currency.

Maybe the speculative "hold to hoard/invest/speculate" thing is just a phase.
Yup, or some of the so-called trolling isn't trolling.
Are salaries actually rising so much ? From survey below, they've risen 2.3% last year, 2.1% the year before ... my memory of other surveys is similar ... doesn't even seem to be rising faster in SV ...

(http://www.computerworld.com/s/article/9237985/IT_gets_its_g...)
The WRT54 was released in 2002, it had 16MB of ram and 4MB of flash running @ 125Mhz. There is absolutely no reason that the ECU couldn't have been running something similar.

The WRT54 also runs in a comfy corner of your living room, fails every few years, and crashes.
This might be obvious to those with more sales experience, but can you explain what exactly you're looking for in regards to "how many minutes they spend on the phone"?

In other words, is the success of the sales people about spending more time on the phone in total? Or is it about spending more or less time per call?

Thanks in advance!
enterprise consulting teams face a perverse incentive to be less efficient than product teams - a consultancy can actually kill itself by being too efficient
Yes but now there is a record of every single thing you've ever bought. Of course for most people this probably doesn't matter too much. But some people do value privacy.
Unless banks are able to think ahead far enough to factor inflation into the loan rates.
That depends on the contract. Be sure to read the fine print.
I think another way to put it is you need to pay them for the risk they are taking. That's why you can't do a one-to-one swap. If they get the same total amount of money that they would in a more stable position, they have no reason to take the risk.
The streamer tried that. It would poll for a few seconds, then execute the majority command. A large number of people opposed this and began to spam start in protest, and actually killed all progress until the streamer reverted it. At the moment there's a slider that allows the chat to vote between 'democracy' and 'anarchy'.
Is egd not sufficient here?
This is all I need to know. Now I am absolutely sure you don't know what you're talking about.
If you ever wonder why complaints about Metro rarely involve system administrators it is because Microsoft started the interface redesign at the command line with PowerShell.

And for a GUI, Metro provides significant and logical access from the keyboard.
This blanket surveillance reminds me of this interview with Pete Seeger:

RetroBites: Pete Seeger - Black List

https://www.youtube.com/watch?v=Y0_IME9WsHQ
Pretty sure publications just do that to make it look like they contributed to stories they outright steal.
Surprised at the lack of hate for Ken at this dick move.
Theo is against virtualisation, and there is no support for it (you can of course do it anyway with full hardware emulation).

"You've been smoking something really mind altering, and I think you should share it.

x86 virtualization is about basically placing another nearly full kernel, full of new bugs, on top of a nasty x86 architecture which barely has correct page protection. Then running your operating system on the other side of this brand new pile of shit.

You are absolutely deluded, if not stupid, if you think that a worldwide collection of software engineers who can't write operating systems or applications without security holes, can then turn around and suddenly write virtualization layers without security holes."
I would hope so.

But with the number of "underwater" homes, subprime mortgages, and so forth that were handed out through the early 2000s, it is clear to me that mortgage holders probably have negative net worth, especially if they were lower or middle class families.

People were buying homes they couldn't afford. In these cases, inflating their debt away is only a benefit.
Introducing ASP.NET Project “Helios”
I was always under the assumption that Gallium Arsenide was the future after silicon.

What's the difference between GaAs and CIGS?
Yes, but "below radar range" in this context means below the horizon, which even from the top of a ship is only 15 km away or so. At mach 4 a Sunburn can cover that distance pretty quickly. I'm sure the low radar visibility make a big difference when hiding from AWACs on the approach, but since radar returns scale with the fourth power of distance I don't see how a missile could possibly have such a low cross section as to be invisible at as close a range as 15 km.
And yet the whole first part of his talk was problems with scala that are not problems in haskell. And many of those problems exist precisely because of java compatibility, which he acknowledges and says is not a good enough reason to do things poorly. By his own measure it seems like he should be using haskell.
From a theoretical perspective, date formatting is a behavior that can be accomplished in a number of different ways. While the pre-Java 8 API only provides SimpleDateFormat, JodaTime provides a similar class and a slew of formatters based upon ISO8601 that don't use patterns at all.

From a practical standpoint, SimpleDateFormat and its analogues don't operate directly on the format string you supply, but instead compile it into a form that is easier to process. If Date.format was the only way to format a date, then the format pattern would have to be recompiled on every call (or else cached, which would affect thread safety).

Now, String.split exists, despite having to recompile the regular expression every time it is called (except for certain optimized cases), so presumably Date.format could also exist, but DateFormat would still be preferable for many cases.
I personally don't think an iceberg can do that

Oppose the creation of the Fed? Icebergs are very persuasive. You should stop listening to whatever conspiracy nonsense you're listening to and go talk with an iceberg instead.
I can't get it to work, can someone tell me what it's supposed to do?
I think I lost one job because I used emacs and they used vi.

I'm not wholly disappointed, because 1) I finally got around to using vi, spending a solid week using it and only it, as my homework[1] for the company, and 2) you don't want to work someone that only hires clones of themselves.

[1] They didn't assign it to me, but I'm always looking for something interesting to do, and since I was serious about wanting to work for them I did it to ease my eventual on-boarding.
Seems he still works there according TFA:

"CNET contacted Microsoft to verify the identify of the self-dubbed Windows UX designer. A Microsoft spokeswoman confirmed that Miller does work for the company but declined to reveal any details about his specific role."
It would be stupid of me to disagree. One should always leave headroom for bugfixes, future expansion and so on; it's only mindlessly throwing hardware at problems that I disagree with, not futureproof engineering.
Let's say in SF you get $150k and put 10% away with a 5% match. That's $22,500 per year you're socking away into your 401k. If you live in Orlando and you're making $90k/yr and put 10% away with a 5% match that's $13,500, a net loss of $9k every year in early retirement savings. After compound growth over 40 years of maturity that's going to be a TON of cash. As long as you don't plan on RETIRING in SF, you're much better off working there.
Yes it does.

I think maybe you are talking about the money creation that a central bank can do. That involves more than just fractional reserve banking, but it often is done in the context of fractional reserve banking.
Could it be that the specialization you are working with ends up actually be a benefit with regards to finding new hires?

From my perspective, I'm probably not going to go out of my way to apply to a typical startup unless there is some reason to believe the renumeration is remarkable. However, I might be interested in applying to a company like yours as a challenge to myself.
It depends on how you measure great.

You can be great as an above average developer, and you can be less than great as an excellent developer.

I'd prefer to measure the complete package.
So to summarize the collections library has "weird and terrifying behaviour" because there are cases where the performance is not quite as good you expected?

You might be interested in the AnyRefMap work being done here:
https://groups.google.com/forum/#!topic/scala-internals/R4fT...
Perhaps you could add your voice to the discussion if you have concerns around performance.