skysight-inc/HackerNews huggingface dataset:
Saying something is beautiful or ugly is a value judgement, in this case a value judgement you're passing on what is usually an ethnicity's most common element: language. And this value judgement is upon a certain ethnicity. If you were to hear that Africans tend to be uglier than Swedes, wouldn't you consider that an uncomfortable value judgement to hear? Oh, but it's just your preference. There's nothing wrong with thinking that Swedes are prettier than Africans, and nobody should be considered racist or xenophobic for making such a claim.

Going back to language, if you're saying my language is ugly because of how it sounds to you, all I hear is that you don't know anything about it and you're referring to something unknown as ugly. It just seems like ignorance.

As to your second point, being unaware of one's accent and being unaware of one's own timbre are completely different things.
personalize their experience ... They will then be more likely to tell their friends about you. ... increase retention and conversions.

So this isn't for the user's benefit.

non-sequitur

If something is increasing retention; and creating more satisfied customers (so much so they are telling other people about you)... then it is benefiting the user. Actions clearly indicate it's benefiting the user.
Because buying things with gold is a huge pain in the ass, especially online.

Storing and transporting physical gold is a big security problem that even banks haven't solved perfectly.

A cryptocurrency backed by gold actually does solve these problems, assuming it's is actually backed by gold, and can keep that gold, and can be audited somehow.
Graduating in 2015? Click for perspective
I completely agree with your social justice agenda here. But as a historical matter, most forms of invidious discrimination have had to be be enforced by government regulations (for sure, that is the case for why gay marriage used to be illegal) rather than by the market. The market (as a historical matter) does tend to break down patterns of prejudice, because most producers would like to sell to as many customers as they can, and most buyers will shop for the producer who will treat them with respect. The former Jim Crow segregation laws in the south had to be vigorously enforced by the formal justice system and by terrorists like the Ku Klux Klan precisely because many businessmen there would have been happy to serve all their potential customers on an even-handed basis if the law had allowed them to do so.
I'm graphing this type of data, but it's too early to draw firm conclusions. I was mainly concerned that the upper, rear units might not fit within my desired thermal envelope, but so far it hasn't been an issue at all. This might make it into our follow-up post, which is intended to explore the design decisions behind the chassis.

If heat or airflow did become a problem, we could add fans to the chassis (either in the intake tunnel or along the exhaust vent). The ideal solution is probably to also attach a chimney to the rear of the rack, but so far it hasn't been necessary.
reminds me of http://zurb.com/playground/jquery-joyride-feature-tour-plugi... zurbs joyride for foundation
Can Algorithms Form Price-Fixing Cartels?
You do want to introduce your solution with "this has problems A, B and C, but we went with it because of X, Y and Z." It becomes much more interesting, because you're explaining not just your solution, but the problem space. Just the solution is usually less interesting than why the solution, even with its downsides, solves your problem.

By the way, thanks for clearly, completely and patiently responding to people in this thread.
I'd argue ambersons was a great film before being recut. Radio was his strong suit too.

He was a genius, but was unable to compromise to make commercial reality, and like many workaholics, his star burnt oh so brightly, but went out predictably fast.
More like an MBA. We really wanted to help out the non-technical folks on a technical team who are trying really hard to grok what we're saying. It really hit home when my co-host Venkat went to a meetup in and found people who wanted to go to dev bootcamps – not to become developers – but just to be able to share the language.

We're hoping to be sort of like the Lonely Planet for non-technical founders, designers, product managers, and so on.

Although that said, my sixty year old mother is currently learning to code herself. So I'm not sure what to expect. The wider the audience the better, but to ask better, more targeted questions we need to assume a certain level of knowledge.
They're also the ones who understand how things work!

As we've gotten more open source software out there and faster computers, programmers are naturally moving up the stack using higher and higher level languages. Where before you needed hand customized C++ (with some assembly!) to do something you often will now use a scripting language.

But in doing so a lot of hard core engineering and architecture understanding is dissipating.

People pick node because it's hot without knowing enough to know that it's going to be a problem for a large project, etc.

I've seen engineers toiling away with the wrong technology experiencing great deals of frustration but not even realizing that its' because they have the wrong tool.

I think a big part of the problem is that companies are too often run by business people who don't understand software. So the managers of programmers are often not programmers. (It should be engineers all the way up to the CEO, and including the CEO if you're a technology company.)

So we have business guys picking technology stacks and stuff like that.

Engineers have been commoditized, and they feel like we're interchangeable cogs, the certainly don't know enough tho tell the difference between a mediocre and good backend or fronted engineer.

And so, of course they don't value experience.

Over time people retire, some retire young, and so teams shouldn't have an even distribution of ages, but they do need wisdom. So, somebody should be wise on each team.
He probably wanted to post this [0], but it has nothing to do with paackage managers!

[0] https://github.com/elburz/awesome-space
There's something pretty wrong with that example. Times from my RPi2:

time ./pixie-vm ./examples/hello-world.pxi
Hello, World!

real	0m1.167s
user	0m1.160s
sys	0m0.000s
Hrm...

Not sure I have any specific sources to share (others might) but after working with all types of hardware, languages, business realms and what not... you start to see patterns. Human behavior patterns, mostly; the same sorts of needs were there 30 years ago as are here today. People need stuff done yesterday, don't know how to describe what they want, oversold a client on something, etc. The numbers may be bigger, the gigahertz faster, and the memory far greater than people could have imagined, but the problems of translating what people say in to what they want via code is ... fundamentally still the same.

A 16k RAM module was ... $200 in my early days. Then a few years later I got 512k for only $150. Today I can get a 16 gig USB stick for $10, at at a local grocery store checkout aisle no less.

No doubt technology has changed and become more ubiquitous. Peoples' expectations of what's possible and what's normal are somewhat different today than 10-20-30 years ago, but the communication problems are still largely the same. Who's in charge of a project? What are the parameters? What defines "success"?

I'm not sure there's any real silver bullet here - most of the "mythical man month" stuff (from even before my time!) is still largely true (speaking in generalities because I can't think of every single line right now).

Learn to figure out how to communicate better - emails, phone, IM, paper, phone, f2f, etc - they all require different skills, and have different impacts on different teams.

Happy to answer more specific questions here or via email - mgkimsal@gmail.com - not sure if I'm just rambling now or not.
ThinkPads encourage end-user repairs/modifications.

For example, If your HDD fails under warranty, they'll ship you a new one with the simple instructions to replace it. Only tool needed is a small Philips screwdriver. :-)
Why is `1000000000000000 in range(1000000000000001)` so fast?
Git is a distributed revision control system and designed as such. The fact it can be used as a back-up tool doesn't mean it should be used as a back-up tool, especially when there are back-up solutions designed from the ground to do just that.
When I'm interviewing a developer, I'm less concerned with what they've been learning and more concerned with if they've been learning. As long as you've accepted that being a developer means constant change and constantly learning, you'll be able to make up your own mind about whether new fad X is worthwhile or whether your organization should skip it. But if you get to the point where you stop learning, you'll be stuck with a certain set of tools/skills that eventually stop becoming adaptable.

I like to think of it like evolution. Most mutations are not advantageous and die off quickly. The ones that are allow you to outcompete competitors. I've learned 3 new languages this year, toyed with 2 new data stores, and played with/read about countless frameworks and libraries. Most of these technologies took up less than an hour of my time. Some I devoted a half day of hacking with. Others I stuck with for longer. From all of this, I've filtered it down to a handful of tools that I'd consider using in specific situations. This is what I consider staying current. I consider this to be between 10% and 20% of my job as a leader in my engineering org. And it's what I feel that I need to do so that when it's decided that we need to use something other than what we're using now, I feel that I can come up to speed on that new technology quickly.

It gets frustrating interviewing developers who, for the past 20 years, have programmed nothing but Java. Sure, they know a few libraries within the Java ecosystem but, for the most part, all their learning from the past decade was domain-specific knowledge from their last job. And then they want to be rewarded for that "experience" at a new employer. Sorry, that's not going to happen. I can hire a newly-graduated university hire who's more willing and able to put in the time to learn for half what I'd have to pay you. That's not ageism, that's common sense. On the other hand, when I encounter a developer with 20 years experience under their belt that has used that time wisely and has enough tools in their utility belt to make Batman jealous, I'm more than willing to bring them on and pay them accordingly. They'll be a great mentor to all the younger hires I'm forced to make.

The key point of contention that I have with you is that I don't consider time spent learning to be wasted. Ever. Learning itself is a skill that needs to be practiced, even if that means learning something that you'll never use.
Blind Gamers Are Embracing Developers Who Have an Eye for Accessibility
This is really a very important reason to do drugs in the first place, especially psychedelics. They show you how much of your reality/perception is based on a temporary chemical/biological state, not what you previously thought of as 'reality.' It also teaches you to 'ride it out' in the event of a bad trip (also a valuable experience). Ironically to some, doing drugs like this can make you more sane.
Tom Wheeler tells cable industry to stop complaining, start competing
> That's because I think, in the long term, it'll play out better for me to have spent my 30s well than to have ratcheted up my salary but not really know anything.

Maybe, but it's far from an obvious conclusion. From a purely economic/financial perspective, it's much preferable to increase your salary as early as possible. Since in most organizations pay raises have a ceiling expressed as a percentage of comp (eg, 10%--either implicit or explicit), the base level of your salary early on in your career has a huge effect on your total lifetime earnings--similar in effect to investing a sum of money at age 35 vs 25. Sometimes having a high salary history/requirement can even give you instant credibility ("a person making $400k must know what they're doing")--some people can bluff through their entire careers that way.

That said, it's probably best to balance pure financial opportunism with "soft" concerns like actually enjoying your day to day work and growing as a person/professional.
You need a reality check - you're placing blame on outside factors (like your parents) for not being where YOU'd like to be in life.

Owning up to that is the first step toward recognizing how incompetent you are at being happy.

I used to be a moping ball of negativity myself once upon a time - it just doesn't work. Sooner or later you have to recognize that the way you are isn't working and take steps to change that.

Today sounds like a good day to start.
It's pretty trivial to fix the default locations that Pixie looks for files. Create an issue on our github page and I'll help you get it working.
I was trying to make point that one of the major reasons income is so g loaded is that education allows the poor-but-smart to rise out of their poverty (and vice versa) via things like the old SAT. Block this and you end up with something like the Middle Ages where the nobility and peasants had the same mean g.

I should say that changes like this are going to have most effect in the middle rather than the extremes. If you are born with a g in the 99.9 percentile band then you will still be likely to escape poverty. It is people born with a g say in the 80th percentile band that will be affected the most by these changes.
Nonsense. Users of free and open source software have every right to point out flaws in the design and implementation of that software. And this is an invaluable service to the authors and community. While finding and fixing an issue is nice, it's certainly not required, and not everyone capable of identifying issues has the time, ability, and inclination to fix those issues.

Furthermore, the conversation at issue was initiated by a community member asking why Weave's authors chose to implement their own security mechanism. The point of this kind of question is to assess whether the authors had good reasons, bad reasons, or no reason at all behind a questionable decision. This helps determine whether the effort to resolve the issue would be well-spent. If the authors aren't convinced that other solutions would be superior, they may be unwilling to accept a contribution, and you are potentially wasting your time producing a patch.
2014 had the most 200m+ tall buildings completed
go get google.golang.org/cloud/bigtable
If the money is instead going to save 80% of the patients waiting for some other treatment, then good. If it's going to be used for other means, then your problem is not the machine decision, it's the person who allocated the money in that way.
I imagine more advanced things like face recognition and such are not so simple, but from my experience writing a raw converter, a lot of image processing is far simpler than you'd expect.
Actually spanner and Bigtable have different and complementary use cases
I've been following Dave for a long while, and I find he excels at leading you towards interesting ideas, starting conversations, discovering and inspiring interesting work by others, experimenting with cool stuff, occasionally just inventing influential technologies. Blogging, RSS, MP3 sharing, podcasting, HTML UIs, sites as apps, REST APIs/Web RPC...

I used Frontier in 1998 as a static site generator, and later as an RSS reader and a blogging tool. Frontier was a very interesting technology, and it was probably part of what made Dave so productive. Imagine a single program that is a web server and a database, a system scripting tool, a scheduler (like cron or Jenkins), an editor and an outliner and a scripting language runtime and an IDE... That's what Frontier was, and building each part of it leveraged the rest, accreting functionality to itself as it grew like coral.

Frontier's integrated approach went against the prevailing attitude in software development, that of UNIX, Open Source and the Web, of worse-is-better, loosely-coupled, modular and specialized tools. But by embracing the web's open protocols and loosely-specified text-based APIs, Dave got more than a decade of remarkably productive extra mileage out of it.
"While the monetary system of Yap appears to use these giant stones as tokens, in fact it relies on an oral history of ownership. Being too large to move, buying an item with these stones is as easy as saying it no longer belongs to you. As long as the transaction is recorded in the oral history, it will now be owned by the person you passed it on to—no physical movement of the stone is required."

That quote reminded me of Bitcoin's block chain.
> The members of a group currency all mint cryptographic tokens (coins, shares, what-have-you) at an equal rate.

So what you're saying is that I can get value that someone else has paid for with their hardware and electricity bills, without having to do anything except be on a list? Sign me up!
It's very clear that this is not a technical problem, but a political one. Dart could be the second coming of Knuth and still nobody but Google would implement it in a major browser.
Haven't yet used it.
Your statement about salary is right. In early funding the founders and employees should get salary bumps that bring them closer to market rates, depending on the stage of funding.

So maybe A&B rounds result in salary bumps.

When the company starts being worth something significant, like over $20M valuation, during funding founders should take some money off of the table-- if they want. It's prudent financial planning (don't have all your retirement in the stock of one company) and while they are giving up potential upside they are ensuring long term security for their family against failure of the company combine with an economic downturn. (A combination I've seen twice in my lifetime.)

And when your company is in the billions you should have the option to take some off so that you can start angel investing on the side.
Php
Advantages/disadvantages between building pure PHP vs. a MVC PHP Framework?
You seem to be thinking about having "nothing to lose" as being like having a magical credit card that you never have to pay back. Since it never has to be paid back, one is now "free" to buy whatever they want. This could indeed be a liberating experience.

However, depression can manifest in feeling like the only thing that is available for purchase is nothingness. If you "know" that whatever you buy will turn out to be an box full of nothingness then having a magical credit card isn't very exciting.
Maybe you are thinking of the 0.01%. The 1% income threshold in the U.S. is about $380K. That's wealthy but it's not empire-building. Most senior software engineers are probably in the top 5% of income earners in the U.S. already, they could easily be in the top 1% with a high earning spouse.
You forgot to include inflation.

This gives you %6 per year. That's great compared to CDs and Bonds but it's not a great return compared to stocks historically. (I think since WWII it was %10 for broader indexes?)
Had this idea before.
I search on this internet, if recall properly, it's because to get into orbit, you mainly need a good horizontal (parallel to the earth) speed, and the ballon only give a vertical speed.

Plus a ballon have lots of frictions and also cannot lift weight rocket.

I hope it help a bit. (If a rocket scientist could answer, that would be awesome)
> One time I simply couldn't find my car keys and almost rage quite life. The car was in the shop.

This is one of the most terrifying aspects of depression for me. I can be functioning perfectly normally (obviously just on the surface), and then one morning I stub my toe or spill a glass of water and I just breakdown. All the frustration, anger, sadness, or whatever that I've been holding in just floods out and I want it all to be over. This is why I used to never drink (and now wish I'd never started), and also why I won't consider owning a gun. When you get depressed you may not be able to control yourself, but you can try to instill good habits in yourself when you're of a sounder mind. Or at least control your environment so you have fewer tools to harm yourself with.
With Video Launch, Reddit Is Officially a Media Company
Application template: isomorphic widgets using RxJS and React
I disagree. I believe his narration of "War of the worlds" was incredible and the opening sequence of "Touch of Evil" is one of the best ever.

He never got the same creative freedom as he got while creating Citizen Kane. Citizen Kane wasn't a blockbuster of it's time as many theaters refused to play when they came under pressure from Hearst. Following which he spent his time in England.

His battle with Hearst has been documented in quite a few places[0].

[0] http://www.pbs.org/wgbh/amex/kane2/
Show HN: 4m-accuracy Indoor Location with Beacons
The 4 Types of Canvas: Business, Lean, Social and NGO's
Was really hoping to see video of the descent!
"No."? Jules' thoughtful comment deserved better than that terse derision.

And, the attitude of simplifying all of this to "get professional help asap" is not very productive. For one, not everyone can afford or access that kind of help. Two, pronto professional help can sometimes yield to bad choices very quickly. Blowing it up risks violating a depressed individual's privacy, they might see that as an action of offense. When a friend of mine was suicidal some odd years ago, I didn't just dial the phone for some professionals to get him, I tried to make it clear to him how much I valued his friendship and what it would do to me if he were to go away -- the guy is rocking life these days. Of course that's definitely not to say don't call for help, rather that this sort of thing demands a more considered response.
The 5 pillars for a healthy startup community in Latin America
This is basically what stock options are. The mechanism of allocation is usually a bit different, but the basic concept is the same.
Sure, I'm not generalizing to all military people, one of the people on the team was also ex military, and I've worked with ex military in the past. This was just a bad hiring decision.

IT's sad that you have to start your own thing-- I would have switched over to people management quite awhile ago if I could. I effectively did it here because nobody respected or listened to the official boss. So I had to lead without authority... I'm totally ready for that role.

The problem is, in my experience, companies are looking for MBAs or business people to lead engineers, not engineers. Too often anyway.

No problem with drinks, we did like to drink outside of work. Just did't like him interrupting us in our work screaming at us to start drinking. (And the "don't be a pussy drink more" attitude was not compatible with the culture.)
I think those are fine, as long as you can skip them.
I have used Pitest at work, it is very good and on more than one occasion it unearthed wanting tests.

Unfortunately, we had to remove it from our build. Our CI pipeline uses VM's that were not provisioned with this type of testing in mind and pitest ended up slowing the build enough to make it painful. If we could get past this, I would turn it on in the morning.
How many of the greatest films of all time was he supposed to make to be considered a genius? Also, he was pretty accomplished in radio and theatre in addition to film.
The lawyer I spoke to was Dutch. There is some unclarity about EULA's sold to consumers, I think the general idea of the consumer protection is that the consumer should have seen the EULA before they paid for the product.

That said, it says on the box that the software is only for Apple hardware, and I think even only as an upgrade for an existing OSX install.

If you're a company, then EULAs are definitely binding, no matter where you are.