skysight-inc/HackerNews huggingface dataset:
Great for the mice.

I don't understand this phrase "Turner said a “magic pill” that reverses ageing is several years away, partially due to the cost of the compound, which would be about $50,000 a day for a human." ?

$50,000 a day for a human ? What is the effect of a day of treatment ?
If they have fewer kids then where's the harm?
MITM issues are far more uhh... interesting ... as well.
> As for them pre-judging any copy and paste as inherently unfair, most people on the Internet copy and steal things without giving credit.

You're justifying their pre-judgment of people by pre-judging more people.

> I always cite material I copy from elsewhere manually, but now the script does it for me. In either case, it's a win.

Citing material by leaving the "\n\nRead more at http://something.somewhere/content.html" isn't a format I've ever seen anywhere, and seems like it would be incredibly annoying to parse.
> It's a strange disconnect. I know everyone is thinking what I'm thinking, but you never see this in the articles. Is it some kind of taboo?

Sure. It's ridiculously selfish.

As you age, you realize your success in all things eventually boils down to experience and ability to execute. Ability to execute wanes with age, as experience is accumulated, so it balances out. Now imagine a spry 20 year old with 60 years of experience? Not exactly fair to those actually 20 years old.

EDIT: To the old farts responding below me, regardless of how well you take care of yourself, you wither with age. By removing that, you are messing with the balance that has existed for millions of years. It has nothing to do with fair competition, it has everything to do with using technology to get ahead of the competition, in the same way that some athletes use performance enhancing drugs, and we as a society frown on that too.
Just a personal view, but my feeling about Lisp and SmallTalk is that they have opposing views of DSLs. Lisp culture seems to celebrate "bottom-up programming," While SmallTalk seems to celebrate writing programs that are unmistakably SmallTalk.
Actually, before we started to "poop in the hole", the rates of infectious diseases were way lower.
I'm not disagreeing with you, I'm just saying that one should bare this in mind while listening. Keep conflicts in mind and listen.
This product is aimed at fledgling entrepreneurs with an interest in accruing the benefits of technology, but without the expertise or in-house resources to leverage the FOSS chain.

Remember: From our perspective, MS is a bunch of evil-empire joykills: lock-in, licensing, lucifier. But for most businesspeople, especially the non-startup bootstrappers, they are promethean, stealing fire from the mandarins of software engineering and bestowing it on worthy dreamers. FOSS is hard; cross-platform is hard; Siena is easy.

Personal context: I flinch instinctively when I see or hear MS' products. However, I'm responsible for ops at my job and I know damned well that there are several generations of small businesses for whom 'business management' is spelled 'A-C-C-E-S-S'. You can criticize this, you can complain about this, you can pay a bunch of bright young things to rewrite it Node or whatever, but you are never going to convince the businessowner that Access is a bad idea.

That same businessowner started one day in his garage with an empty Access database and remembers both it and those days with justified fondness. He's still just getting over not being able to 'improve' your schema on his laptop on lunch break so it 'makes more sense'.

I predict in ten years there will be a huge market for consultants getting businessses OFF this thing. But there will also be a huge pool of new businesses it helped create, so on balance, let me be the first to say: Hello World, Siena, and welcome.
An alternative approach that I've implemented in the past [0] (and found quite useful) is client-driven server-side inlining of linked resources.

What this means in practice is that the client specifies (usually with a query parameter) what related resources they are interested in, and the server can pre-fetch those resources and include them in the response.

Obviously there's some upfront development costs and your API needs to have a well-linked taxonomy of resources, but it allows the client to create these 'flattened views' on the fly with no further work on your part.

Edit: Just wanted to clarify that IMO this is a RESTful design because you are still using links to navigate your API resources, you're just writing a "smarter" server that can reduce the number of requests.

[0] https://github.com/BetSmartMedia/lazorse-nesting

edit: fixed link
No. Survival is our strongest instinct. Besides, human population will plateau around 10 billion or so, and we're already seeing trends, from very early ones to pretty advanced ones (Japan), where people decide not to have kids anymore in modern societies, or even have sex with other humans.

You're thinking immortality would be a problem given the current conditions. But the conditions will be different in the future. The same will be true for food production, which should be vastly more efficient in the future, and enough to feed everyone.
50k at first, 5 bucks eventually, hopefully.
Currently, you can buy NADH, which seem different, or NAD+ precursors (Niacin, Niacinamide) or Niagen (https://chromadex.com/Ingredients/NIAGEN.html), which is proprietary and suppoedly increasing NAD+ levels. It's pretty expensive as of now compared to Niacin, but, still, $50/month isn't that much. Combining Niagen with Resveratrol should do the trick.
"It appears to be correlated with driving over rougher terrain."

Who'd have thought....
These carriers are the most powerful, expensive war asset any nation state has. The weakest, most vulnerable link is the soft fleshy things on board. Yet, they are the most essential component of the system. You cant replace them at sea, you cant replace or fix parts, they are finite and vulnerable. No people, no carrier. Therefor carrier crews are probably some of the best looked after people in the forces. Perhaps not out of humanity, but to protect that vital asset.

I'd go further. I would wager that a US nuclear powered carrier is one of the safest places on earth. After all, it is built to fight in an all out nuclear war and hopefully survive. Perhaps be the last hope if the mainland was devastatingly attacked. It can't possibly be that if its crew are, well, dead.

Also, carriers are kind of isolated. They are societies in themselves. The captains are probably more attached and sympathetic to their crews than many other parts of the military.
Not sure why you are being downvoted -- this is actually the paper in question, minus paywall. Thanks for the link.
Introducing the Grand C++ Error Explosion Competition
Personally, I probably do riskier things when I do feel old.

Tick... tick... tick....
I have a hunch this is a technology that will take very long to 'trickle down' the forbes list.
You just have to say something even if it doesn't make sense don't you?

TRIM isn't mentioned in what you call "the instructions" [1].

[1] https://help.ubuntu.com/community/Installation
> Now imagine a spry 20 year old with 60 years of experience? Not exactly fair to those actually 20 years old.

How is that "unfair"? You might as well criticize an old person who looks and acts young for taking good care of themselves.
Whatever you do, don't copy and paste the image URL into say, IRC, for example.

Big mistake.
Wait, how else does anyone else do this?
Managing a startup is different. In a startup you want as many people as possible to be "self managing". In an enterprise often you hire "commodity" workers who should be able to do what you ask, and do it when you ask, but aren't supposed to find more things to work on.

In a startup you want "motivated self starters" who will build the feature you asked for, and then solve the six problems that spawn from that, or at least say "hey these things are all going to break or look ugly with that change"

Startups also have to manage their "brain burn" very differently. At MSFT I could push employees hard then send them on a 2 week vacation. I can't do that at a startup.

At MSFT I had 5 people who could do any one task and I could shift loads to manage brain burn. In a startup I am lucky to have 5 people total, and likely I tried to round out my team so I don't have much over lap.

In short, Startups are different. If you manage the same as you do in enterprise you will fail.

Don't reinvent, there are plenty of places to learn how to manage at a startup, just don't think that managing in a fortune 500 and a "we raised $500k" is the same.
Hazel thinks George looks exhausted and urges him to lie down and rest his "handicap bag", 47 pounds (21 kg) of weight placed in a bag and locked around George's neck. He says he hardly notices the weight any more. Hazel suggests taking a few of the weights out of the bag, but he says if everyone broke the law, society would return to its old competitive ways. Hazel says she would hate that. A noise interrupts the conversation, and George cannot remember what they were talking about.

http://en.wikipedia.org/wiki/Harrison_Bergeron
PAL or NTSC MOD timing? :)
I wonder whether the researchers were tempted to try this on themselves. Or the lab costs of producing it[1] would effectively prevent it?

[1] quoted at $50k per day, not sure how many days a person needs...
Thanks for the links, I figured that the lack of compliance in the "tire" section of the wheels would be an issue but that is a bit more damage than I would expect. I am guessing that under some driving conditions you might get up to 50% of the rover weight on a wheel and if that was while the wheel was rolling over a rock, the tendency would be to cut into the aluminium. So one wonders why not titanium outer rims? or a compliance system that would allow the wheel to deform until enough weight had been distributed across enough surface area to keep it under the 'minimal damage' threshold.
This seems to be a pretty big deal, but the article gives off the impression that mithocondrial aging is the only reason that we age. In fact there are many other aging factors that have not been linked to mithocondrial aging (and have, agruably, no relationship).

Some other factors I recall studying are

- gradual DNA damage, which is quite inevitable

- collagen degradation, which affects the eyes and all cartilaginous tissues.
I don't think it's a taboo subject, it's just not really good journalistic form to employ relatively baseless speculation for more than a few sentences.

Basically, as a matter of principal they report on what the researchers are doing, and the researchers are (quite reasonably) going to try to beat Alzheimer's in patients who actually have it before they try to apply it to everyone. No sense in worrying about, Can this be globally administered, like a vaccine? before they even know for sure how to beat it.
Very small, as the second draft of the protocol is still in heavy revision.
I don't know, but if you hunt through my comments on HN you'll see what I do. Mostly it seems to have been successful - the guys on my teams are pretty good. Mostly I've only gone wrong when I've put too much faith in paper qualifications.

I ask people to code something trivial, on a whiteboard, in any pseudo-code they care to invent on the spot. Then we talk about the strengths and weaknesses of the code they wrote. We end up talking about algorithms, data structures, project management, quick hacks, technical debt, comments, function and method size, functional programming, and more.

The idea is to find their strengths, to make sure their weaknesses are covered by people we already have, and to see if we could work together. Sometimes we don't even agree, and it's the way they discuss the points that matters.

I'd love to see it made into a science, but I'm nowhere near clever enough to do that.
And of course, what you say about "country X" also applies to "individual Y," doesn't it? How convenient.
I think the Native Americans did the same thing with smoke. "Smoke" for 1, "no smoke" for zero. And they went way further than across the room.
I'm baffled by the idea that anyone was ever deluded that it was.
How To Generate Procedural Racetracks Without Noise
http://www.cyrilpereira.com/modplayer/
This comment must fall under some FAQ. Someone always brings it up in the "What if humans could live a lot longer."

I'm sure that it's trivial to answer and has been answered a million times.
Real estate agents aren't the problem. My mom is a real estate agent and I've known a lot of real estate agents in my life. The absolute scum of the earth in this industry are actually the members of the Board of Realtors that represent the individual agents across the country and rig everything like a cartel. It's a licensed procession with a lot of political influence nationwide, which gives them immense protection from market forces that would have drive the percentage they earn from sales down years ago.

Any shitty experiences you've had with real estate agents are probably better explained by Hanlon's Razor. There are a few exceptional real estate agents, but my experience has been that real estate is a profession for those incompetent at everything else. When they say prices are going to keep going up and that it's a great investment, they usually actually believe that fully. They have bought whole hog into the idea that real estate is the best investment and that prices keep going up. You can't even work as an agent if you don't really believe that since that is the only condition in the market that is really in your interest as a broker since it's the condition where liquidity is highest, and liquidity is the best thing for brokers. If you don't harbor that believe you either stay out of the market/profession entirely or you enter the speculative side of the market, buying low and selling high.

Those who can do, those who can't do anything, broker real estate.

FWIW, this largely applies to residential real estate. In commercial real estate, the brokers are a lot more like the banksters promoting a kleptocracy.
Bitcoin, obviously.
>like that it might be the last thing humans ever need to invent

Damn. Putting it like that is powerful.
>Demand peaks early morning and early evening, when solar is near its minimum. And in winter, solar is near zero at those times.

That might be true in some places, but neither point is true in Hawaii. Insolation is nearly the same all year, and grid loads peak midday with insolation (think AC): http://www.heco.com/vcmcontent/StaticFiles/Images/Articles/t...
20 year veteran here (although experience does not really equal the 'years in business', it is a multiple of years in business and ability to 'accumulate' and 'apply' the experience).

Interview is a negatives filter, not a 'successful employee' indicator.

As a filter, it should be adjusted depending on the job markets, salary/benefit brackets and the type of effort a company/team is willing to put into a hire.

A retained hire is a hire who passed the negative filter and then passed the 'successful hire' assessment, which should be done in a 3 month period.

A company that is not willing to let a bad hire go after 3 month assessment, will eventually accumulate a horrible baggage, that will bring their productivity and morale.

No interview (negative filter) can be good enough to avoid the 3 month assessment. If you do not accept this thinking, and still assume that you can construct an interview that will be good enough to avoid the 3 month assessment -- then you are a likely looking to hire candidates that mimic you, and in general (regardless how average/special you are) -- you will hard time finding the candidates, and actually scaling up your hiring effort.

Back the actual interview.

Programmers need to know which algorithms are sensitive to data sets and in which way (memory consumption, disk consumption, run time cost)

Programmers need to be able to find good implementations for the specified constrained. this is important -- they need to be able to find the existing solutions, not build them themselves (unless you are hiring researches to work out things that have not been done before).

So a good test would be to present a problem, and ask a candidate to do a quick internent research, and find analogies/approaches for a given problem. Asses which one of the found on the net solutions fit better to the problem space. And then describe how they would incorporate what they have found into an implementation, and how much effort they think it should take.

Programmers need to be able to reason about maintainability and testability of the code base, using both previous experience, and analogies from open source projects. Having references to popular books on this topic is helpful is well. This is largely non-formal topic based on empirical evidence or personal experiences. So they do not need to match interviewer's expectations, but must be well argued.

Programmers need to be able to articulate how they react to business decisions that require weighting various trade offs.

Finally, important to see how they relate to the team members that they worked with, from the company they are coming from.

The interview questions posted by the OP address not more than 10% of the criteria I outlined above, so in my view these are poor examples of the CS interview questions.
And the Mac equivalent to Access here is FileMaker. Entire kingdoms have been built by using one of these applications as a foundation.
That right there put me off upgrading. It's bad enough that to jailbreak my phone, I basically have to accept the fact that I'm running an operating system with known (and unpatched) security vulnerabilities. That evasi0n basically bundles spyware is completely unacceptable.
Yes, this is what I was thinking might have happened, but I wasn't certain.
It must be nice to have the option of solar panels, at present I have a metre of snow on my roof and that's on the south side.

And that's after I spent three hours shovelling off as much as I could before the ice storm hit us today.

It snow 15cm before the ice storm now I'm back to square one.

I'd like to have solar panels but I can't see how I could keep them from being covered in snow without shovelling them off off at least once per week Dec to Feb.
How is an open source browser like Firefox supposed to implement Encrypted Media Extensions without leaking the keys to anyone who decides to grab the source code?
Just played around with it for an hour or so. I really like the UI, it's very basic yet quite powerful. I like how they used Win8 UX concepts for a complex app, it works much better than I would've expected. I find myself using my laptop's touch screen as a matter of course.

It's quite powerful even without the using the function reference, because common actions have dedicated UI, and all fields have great autocomplete. I also realized that a modern HyperCard is really just all I wanted, and it seems that this may be it.

That said, it really lacks on the documentation side. The function reference is a start, but without understanding the concepts, getting something real to work feels a little impossible. (Example: `Remove` removes an "item", but how is an "item" identified? Does a screen have a "current item"? How does this work?)

Still, a very nice start. I hope this gets better fast and then I'll want to be a power user.

I also hope they won't start charging Access-style prices for it.
Vector of vectors, as I wrote; quoting cdecl "declare x as array 100 of array 83 of int".
The thing is, the answer to how all of this will end is blindingly obvious. Assuming technology continues to improve, then CLEARLY people will find it useful to turn themselves into walking computers/phones/cameras. Yes, society as we know it will change as a result, but it's been doing that since the dawn of time.

Sorry, but I still don't buy the inevitability argument here. You are considering only the potential upsides of new technology. If there weren't potential downsides with serious adverse consequences as well, there wouldn't be so many of us who are concerned about things like the erosion of privacy.

The difficulty with this particular issue is that it is hard to predict exactly what the adverse effects might be, because we've never had the technology to surveil and record the general population on this scale before, but by the time we know, it may be too late to do anything about it if the answer is a very bad one.

Sure, society might eventually evolve to forgive youthful indiscretions while conducting job interviews, and to avoid insurance-based systems where the insurers have a clear interest in not dealing with anyone who is actually likely to make a claim, and to understand that the former pop star who's been on the BBC News home page in recent days because he has the same legal name as another musician who just got sent down for decades for committing some very nasty crimes is not the same person even if his picture was shown alongside the relevant headline by Google.

However, right now, none of those things is even close to true, and having privacy that allows people to segment their lives and share different parts with different other people is how we deal with that problem. Even if we do eventually reach that level of maturity as a society, which is far from certain in itself, it will surely take several generations to get there.

So no, I don't think the outcome here is blindingly obvious at all. People might find it useful to have permanent recordings of their own lives and anything they encounter in it, but this cuts both ways, and they might find the disadvantages of having anyone else being able to just look them up far outweighed the benefits of being able to (legally and socially acceptably) use always-on, covert recording devices themselves.
Unfortunately, it's not just small business. There are some very, very large players that still use Access that I'm aware of. Every thing you said still applies though.
But report: right clicked to access context menu, but it kept playing a short buffer instead of progressing through the song. Closing the context menu goes back to normal.
Some Additional Ones:

FUD: Unless using mined bitcoin's people will never purchase anything with BTC unless the current trading price market price is over the price they paid for it and this will make put a bitcoin based economy in peril

FUD: If the price is over the user's purchase price they will be in a constant cycle of buyers remorse or else waiting for a better price for goods because of the potential speculative return from an increase in price and this will make put a bitcoin based economy in peril

Oh wait, both of those are true.

Bitcoin in a fantastic disrupter of the old transaction fee hungry financial systems, it will be ground zero for change.

In that it is revolutionary.

But it will will most likely fail to become a viable currency unless the volatility vanishes and it goes into a consolidatory sideways pattern. This is unfortunately not very probable either.
Another reason is that this style of programming makes it very difficult to improve your TTFB (time to first byte). If the entire document can be manipulated at any time, you can't start sending anything to the browser until all your processing is done. This means a lot of unnecessary buffering on the server side and ultimately a delay in pushing data to the client. Modern browsers do pretty well at rendering incomplete HTML, so the faster you can start sending data, the faster the page load will be perceived.
if they are successful (which I hope they are) then we're talking about pushing back retirement until 90 or maybe 95 right?

Which I would be totally OK with. Imagine how much more scientific progress we could make if we had 70-year veterans of their field with the sharp mind of a 27-year-old!
> tests will be run

> The maximum source size is 256 bytes.

256 bytes C++ busy beavers are going to run longer than the universe has existed. Expecting to run the tests seems like a misguided way to do the judging.