skysight-inc/HackerNews huggingface dataset:
Sometime ago was posted here (I think) a pdf with the state of the art on psychology and one of the topics were the qualia and senses.

They seemed to agree that they were interpreted as an electrical signal and didn't have anything to do with the organ itself, as when you see in your dreams.

Based on that I disagree with you anything as being processed by the brain affected by tech outside our natural capabilities should qualify as sensory and not cognitive enhancement....

will search for the pdf... right now this just qualify as "expert logic fallacy"

update:
even when I'm extremely tempted to agree with you...

edit2:
pdf here http://open-mind.net/collection.pdf
The applicable tech is already under a patent license (see OATH and IETF documentation). The IETF patent literature seems particularly strong and particularly binding. (Which is good because a lot of the internet relies on IETF standards.) There's no greater risk with a Microsoft option than a Google option; it's open standards and all the options interoperate (regardless of what Google and other TOTP and HOTP apps have accidentally and intentionally told people and what confusion exists about the technology in general).

FreeOTP looks like a good option. It doesn't support every platform yet, and it doesn't have a mainstream recognizable brand name. Yes, it's a great fall-back option, though, for folks that want to "graduate" from the Google/Microsoft/other options.

I am just pointing out that of the mainstream brands that the public in general knows (and trusts to any degree) Microsoft's option has the best cross-platform reach and is the easiest to find in the respective app stores. That carries a lot of weight in getting a security feature that everyone should be using into more hands. I realize a lot of technical folks are still highly suspicious of Microsoft and feel there is a lot of risk in Microsoft's name.

Yes, it would be better if it were open source, but it is patent unencumbered, as much so as open standards typically get. I realize it might not be your preferred option. I was hoping, however, to point out to people that is a good option (not a perfect one, but a good one) to spread the gospel of Real Two-Factor Authentication.

(«I don't use these products at all.» You probably should be using at least one by now, if not several. OATH TOTP (RFC 6238) and OATH HOTP (RFC 4226) are the best options we have right now for Real Two-Factor...)
From Isaacson's biography of Jobs:

> An early showdown came over employee badge numbers. Scott assigned #1 to Wozniak and #2 to Jobs. Not surprisingly, Jobs demanded to be #1. “I wouldn’t let him have it, because that would stoke his ego even more,” said Scott. Jobs threw a tantrum, even cried. Finally, he proposed a solution. He would have badge #0. Scott relented, at least for the purpose of the badge, but the Bank of America required a positive integer for its payroll system and Jobs’s remained #2.

Isaacson, Walter (2011-10-24). Steve Jobs (p. 83). Simon & Schuster. Kindle Edition.
SQL Server needs a couple hits with a cluebat to even satisfy the basic three requirements for a database system they listed (I'm talking about the MVCC line of course).

Honestly, if a commercial database provides what you require and you have the budget? Sure, why not. But I'd always try to avoid that myself, because the serious players (MS, Oracle, is anyone still using DB2?) are really, really expensive.
>My head was spinning (literally)

What would that even look like? On what access can a human head literally spin?
Percona to the rescue [1]. Works flawlessly, at least in our case.

[1] https://www.percona.com/doc/percona-toolkit/2.1/pt-online-sc...
You don't need to close the database connection to not have an open transaction, right?
I can't say I expected this, but it makes a lot of sense. The Wii U was well loved but didn't sell well. With this kind of set up, they get to provide the same kind of experience to their home console users with a fraction of the development resources, while making their bread and butter mobile users happy with more powerful hardware. Meanwhile NVIDIA has hemorrhaged money on their mobile chipsets for years, and now they finally have a committed customer that can take advantage of their graphics expertise, ramp up production and maybe even lead to them becoming more competitive in the smart phone and tablet markets. Nintendo gets the kind of leverage Sony and Microsoft had over AMD when they were desperate for customers for their APUs, NVIDIA gets to take back a slice of the console pie.
Even more interesting is how they were brought together largely by parents making decisions to learn technical skills and then being adept enough to obtain employment at a top company, choosing to live in the neighborhood they lived in near other technical people with access to surplus parts, and then making enough money to provide their children with the space, time and security to tinker.
This challenge has room for tech, ag, finance, and supply chain innovation.

From the site

SAWIT seeks solutions that address these questions and at least one of the following needs:
- Access to quality inputs such as seeds, fertilizer, labor technology and extension services for improved and sustainable production
- Access to up-to-date market and pricing information services
- Access to finance for farmers who do not have formal banking services
- Geographic mapping and demographic data that clarifies informal land ownership for farmers, and could lead to legal title and sustainability certifications
- Ability to trace crops to specific plantations and assure buyers that smallholder crops were produced legally and without deforestation activities
- A fast and cost-effective way to transport farmers’ palm fruit to mills in less than 24 hours
That's not up to Let's Encrypt, Baseline Requirements created by the CA/B Forum only permit EV for *.onion.
nah. R is actually not bad. i would go for nodejs. or any sort of dependency injection, so no one would ever know what method behind an interface is being called. not to mention kdb+, which is write-only by design.
On the contrary, SSD lifespans have actually decreased. Smaller transistors considerably reduce lifespan, and the advent of storing 2 (MLC) and 3 (TLC) bits per cell has hastened the trend.

3D-NAND uses different physics, but as of now hasn't yet matched legacy NAND's endurance (lifespan)
"Differences in groups are real" doesn't mean anything, everyone agrees that differences between groups is a thing, that is the entire purpose of groupings, what you've failed to prove is that racial groupings represent anything other than "what the eyes see". The bottom line is that it doesn't matter what your eyes tell you because "eyes" are not a sufficient tool for genetic analysis, otherwise something like a paternity test would never be necessary because it would be apparent by looking at a father and child that they are directly related. Your eyes provide a crude signal for some genetic traits, not a definitive description. Your reasoning is akin to sorting boxes into groups based on their weight and then suggesting that weight classes are sufficient to describe the content of boxes because years of analysis based on weight has yielded statistical trends about particular weight class groupings.
Show HN: README badge that tells you the percent of PRs merged in 24 hours
I always liked this story, also from Andy Hertzfeld: http://www.folklore.org/StoryView.py?story=Negative_2000_Lin...
Bill himself says he was #4

Happily, I was given my old employee number (number 4), and my new title was “Member of Technical Staff”.

http://www.storiesofapple.net/jack-of-all-apple-trades-inter...
A quick skim of the abstract reminded me of GMS from the 90s (http://homes.cs.washington.edu/~levy/gms/index.html).
You can still do it in one transaction, sort of. Replace "send email" with "queue email" and then either eliminate the step that writes the success to the database (pushing that off to the queue processor, who will open or already have open a database connection) or instead write to the DB that you queued the item.

The advantage you gain is that the queue is a nice buffer if something gets held up with email sending, and also, the queue processor can work in bulk, say sending 100 emails, and then opening a connection to the DB and writing them all in one statement.
I heartily agree. This view is actually supported mathematically. See "Large Limits to Software Estimation" (http://scribblethink.org/Work/Softestim/kcsest.pdf) by J.P. Lewis. Supplementary materials: http://scribblethink.org/Work/Softestim/softestim.html
I envision a concierge service, with a low monthly fee or high one-time usage fee, for road side legal and technical counsel.

If the car is already driving, why should a a passenger know which rule the car was following at the time an officer said a moving violation occurred.

The concierge could access the car's driving records on the fly and provide specific reference to traffic laws at that specific jurisdiction. The officer and the concierge could hash out the entire interaction roadside and it could recorded.

Meanwhile, the passenger/"driver" would be sitting there mouth shut, hands on wheel, and hopefully not attracting any attention beyond the moving violation.
Is writing "the average bizapp" as an SPA a bad trade off? Depends on the circumstances and the people involved, but it's certainly not clear to me that this is going to take more time, or entail more risk, than writing an "old school webapp".

Doctors are expected to stay up-to-date too, and at least keep an open mind about new treatments and procedures.
Well, that fact combined with me saying they are not both managers must mean that Andy is not a manager.

Seems unfair to claim "Elizabeth's post makes it sound like she's a manager-type" when she literally says she is a manager in the post.
I wasn't arguing that it was their atheism that they committed atrocities in the name of - rather that you don't need religion to commit atrocities. That article and, I think, your position are pursuing the same fallacy but in the opposite direction.

Hitler had his ideology, Stalin his manifestos etc - they all had their own, unique 'holy book' or similar that justified their crimes and it would be a mistake as you've said to somehow link them all as being from a common position.

And yet Hitchens and possibly you do the same thing in the opposite direction: despite the average ISIS member having as much in common as your, say, average US muslim as a nazi might have to a 1917-era russian communist (next to nothing) - you are arguing that their religion, not their idealogy is at fault.

You might argue that the various holy books of faiths cause a problem: for as much as the bible and the (far better written) quran espouse love and joy etc etc they both also include a fair amount of violence. But these books have been rewritten, multiple times, and are constantly being reinterpreted. Blaming the text for the actions of the reader seems harsh.

I guess ultimately the problem I have is that people who say religion is the problem and it should be banned seem to me to be worryingly similar to those that said computer games should be banned in the 90s. A very small amount of people committed atrocities, and all of a sudden it was the games 'promoting violence and hatred' that needed to be stopped, rather than people confronting the more nebulous and difficult issue of culture surrounding the criminals that made them more susceptible to hate and sociopathy.
Experience with Mysql replication (even simple master/slave) leads me to believe Uber is going to have some rather nasty surprises at some point.
This is quite fascinating in terms of "one-click to build projects". The engineering-complexity required to build so many different projects with "1-click" must have been a really fun challenge for the Koding and Gitlab teams.

Although I suspect that not every project is 1-click buildable, so maybe it's just ones that support Docker/containers?
ORMs have mostly been just painful at ever shop I've been at. I've used ActiveRecord, Squirl, Hibernate, django.db .. they're all various level of suck.

The one huge advantage of an ORM is the ability to support multiple databases, but that only really works if you can do everything using the ORM. The moment you have a function too complex that you need to write some SQL, now you need some case statements and multiple integration tests for all the database your product needs to support.

They remove some boiler plate while adding others. In one of my own projects, I just created several files (pgsql.commands, mysql.commands, etc.), a basic set of classes around them and a base set of commands that will work for all the DBs I wanted to support (so the command files had an inheritance model, albeit only one layer).

With all that being said, most ORMs I've used do have explicit transaction support. I know Squirl had a `transaction {}` block you could wrap commands around. Transactions shouldn't be an excuse. They should be off by default and explicit added around blocks of things that need to be atomic.

> Try enforcing this on teams that use ORMs like hibernate with 500 developers.

I realize this is a hyperbole (I hope) because you really shouldn't have 500 developers all on the same monolithic project (unless you're developing like...the Linux kernel). Getting your team to at least try to implement best practices does take some effort, but with things like weekly demos and code reviewed commits, it's do-able.
Personal Project: Active Wort Chiller
>building all the infrastructure

What infrastructure? Some cloud BI solutions let you drop an iframe to integrate and done. Same is true for the rest apis.

Still not seeing the differentiation, however I honestly wish you success. Congrats.
Don't see a link here, but Techcrunch posted about it in an article:

https://techcrunch.com/2016/07/26/a-hack-by-any-other-name/
This opinion needs to fucking die in a fire already.
A single population group (South Korean women) with an average height increase of 20.2cm over 100 years is absolutely astounding (that's 8 inches for those of you using freedom units). That signifies an enormous improvement in nutrition and healthcare in a relatively short amount of time.
Which sucks because a data center that doesn't support IPv6 is the 2016 version of a data center that only does Token Ring networking.
It's more expensive to die it yellow than bleach it white. And yellow paper is less recyclable.

Some say yellow is better because it doesn't change color over time. I personally prefer yellow, but it's certainly odd.

My law firm in the USA uses white now.
Man that'd be awesome, if I didn't delete the e-mail address used with that username :(
Ha, got me! By literally, I meant in the medical sense (is it called "vertigo"?), not as an idiom (meaning to confuse or overwhelm).
Not exactly, because someone who explores other technologies unrelated to his/her "work" field will inevitably pick up experience and knowledge - which the employer can grab for free without sending the employee to expensive courses or having to hire highly specialized freelancers.

I have done a lot of weird things as "hobby" projects with even weirder technologies, including interfacing with smartcards in PHP (don't ask), working with cheap-ass Chinese thermoprinters, electronic chips, devkits, FPGAs, operating a mixed OpenLDAP/AD stack,... and I very often have profited at my job from the knowledge I gained while developing.

Oh, and someone who never heard of Apache rewrite rules please shouldn't call himself a full-stack developer. Ops (and being able to formulate ops requirements to a hoster!) are a part of the stack, too, not just deploying some nodejs stuff to a container in the cloud.
I assume that the article title is a euphemism for "farting".
Quick note - the link to your website is broken in the article
No you don't. But depending on the ORM, some of them batch writes unless you explicitly tell them not to, but will flush when you close the connection. So some programmers will just close the connection because they don't understand the difference or because they've learned that closing the connection guarantees that the data is written.
You can turn off transparency in the system preferences.
Looks great! I've just gotten a single instance up and running. Really simple to set up. It seems almost exactly what We've been looking for!
Some background: We have been evaluating different time series databases for use with sensor readings (We probably need to ingest something on the order of 100,000-200,000 samples/s per cluster). The data is from physical sensors like temperature, level, pressure etc. Where all the data is in the form of tag(string)|datetime(ms)|value(decimal).

Have you done any comparisons to other similar software like influxdb, Cassandra, etc? Especially ingestion rate and disk usage.

What kind of pricing can we expect on Managed Hosting?

We are currently leaning towards Influxdb but the cluster licensing stuff they are doing really made us think twice.
What Goes into a Great Convention Speech
How does it compare to Clickhouse, recently released from Yandex [0]?

[0] https://clickhouse.yandex/
For me, an interesting take-away from this survey is that people assumed that _scientists_ would jump the gun, that "...scientists would rush to offer each of the technologies before they had adequately tested or even understood them."

In their minds, it is the doctors/scientists that are most excited about the possibilities / opportunities afforded by offering something as soon as possible to the public, as if we could all be further guinea pigs for them, or as if it would make them rich personally, or that they are motivated primarily by the satisfaction of knowing the fruits of their labor were put to use.

Those are certainly some of many valid motivations for people working in intellectual fields. But it is interesting the public does not understand that doctors/scientists are more likely to be reluctant to turn findings into products, instead preferring to follow the new research opportunities and/or building a community or consensus.

It is a different kind of professional that turns scientific innovation into potential products (engineers, entrepreneurs, marketers, bad journalists), and along that spectrum is the increased rushed, cavalier attitude.

This distinction is lost on those surveyed.
Medicine's been a work in progress for centuries, doctors have done and believed all kinds of stuff we can call crazy today to figure out what works.

Your sore knee analogy... probably really did end in wholesale unnecessary amputation and death until we shot and hacked up enough people during wars to learn more accurate ways to treat a sore leg. We learned a lot from crude, violent and deadly experiments by Nazi doctors doing stuff that would be intuitively recognized as illegal in most countries today.

Programming is also in a state of evolution. Maybe one day we'll look back at SPAs and everyone will agree they were as crap as java apps in browsers. We used to think asbestos, lead, oil, cigarettes, opium etc were great solutions too.
Honestly, I know things can't stay the same forever, particularly in the design department, but to me Aqua still looks way better than current OSX (granted, I only use OSX very sporadically for educational purposes). I have to admit though that I'm not a huge fan of the flat designs that are currently "in" where you can't easily tell when one UI element ends and the other begins. I don't think that's very easy on the eyes generally but it seems that I'm the only one that sees it that way. Whatever.
The lf version comes with red mx switches. It's not just the keys though, as the position of the keys helps immensely.
Notably, a lot of the people I know who report depression-inducing pain have distracting, breakthrough pain.

Even with chronic pain, it's probably not the end of the world when it's "an ache in my knee when I move in this direction" or even "a mild ache in my knee always". But if it's "at random, frequent times, my back hurts too badly to stand or function", that's super hard to ignore or get used to, and I can see being incredibly upset by it. Cluster headaches come to mind as following this sporadic + devastating pattern, and indeed they do cause a fair bit of suicide.

"Can't escape it" and "can't get used to it" are an ugly combination.
How do you deal with human error?
> do you really want to be in a machine that you have no control over

Yes. I regularly fly in planes, which I have no control over, and which spend most of their time on autopilot. I also regularly deal with machines that do their jobs far better than I could, and I feel no desire to take over and do those jobs worse. Why should that answer change when the stakes get higher and the cost of a mistake goes up?

(That doesn't mean I want to beta-test an experimental driverless car; it does mean I'm eager for a non-experimental one.)

> But people will still want to intervene when it doing something dumb like driving into a pond, or gets stuck on a median and cannot figure out how to get off.

A vehicle that did any of those things would be considered broken in a deadly way. The solution isn't to hand people broken vehicles that they sometimes need to take over from; the solution is to not call a car driverless until it handles those situations (generally by not getting into such situations in the first place).

> Driverless cars will probably not be magic pods that whisk you around.

Yet.
Jobs might've been butthurt and it might've made better incentive but nobody likes to sole-source critical technology elements.
> basic three requirements

SQL Server works just fine and has lots of concurrency control to do whatever they need. And the way they're using the database doesn't seem to really make this an issue outside of their replication.

> are really, really expensive

This whole janky setup they have sounds even worse. None of the commercial relational databases are really that expensive considering what they offer, and we're talking about Uber here. We're a small startup that pays for both.

Money for (a better) working product with support is the right call, not build it yourself. This is just poor tech decision (outside of using a RDBMS in the first place).
Good stuff.

Tip: Rather than repeating .append several times,
concatenate your result in a variable, then at the end append the complete result. That way you just make one append call (performance).
Referring to: https://github.com/surbhioberoi/github-widget/blob/master/sr...
Sorry, but I don't see it. While they are busy buying up IPv4 addresses, I'll just be over here moving everything to IPv6 only and not have to care about any of that.
I like the reddit /r/bodyweightfitness recommended routine.
Oracle ???
Let's start:

- No transactions for DDL changes.

- Oldschool commandline client. auto commit disabled by default. no history.

- Weird sql syntax + semantics. f.e. null == empty string.
I talk to a lot of people who think lack of NAT "exposes everything" and is a big security problem. I try to explain that firewall is not NAT and NAT is not firewall but people do not seem to be willing to hear or understand this. "NAT equals firewall equals security" is tattooed on the inner eyelids of an entire generation of developers and IT people. It borders on religion.

On a deeper level this is because almost nobody actually understands how networks work. In my experience even really top developers often have absolutely no idea what happens on the wire. As a result they basically cargo cult netsec. Since they don't understand it, anything that deviates from "standard practice" gives them security FUD willies because they don't see the implications.
https://m.signalvnoise.com/feedback-just-in-time-may-well-be...
This is a fair summary. I suspect that the author might disagree about how strange the basic urge to suicide is, but I completely agree that the really interesting category is "internally suicidal but not acting on it".