skysight-inc/HackerNews huggingface dataset:
> Truly exceptional (never documented) human ears might technically be capable of faintly hearing 23 or 24kHz tones, but that ability is likely to manifest and deteriorate over the course of (at most) a handful of contiguous years in their life and never return.

When I was in my twenties, I could easily identify sounds in the 23-26k range (tested using professional gear more than once). When I was younger it was quite painful to hear as my ears were so sensitive to it (as a young teen, I would wince in pain when a monitor was left on without an input signal even in a room of people yelling noisily at each other). Even now in my late 30s I can still readily hear in the low 20k hz easily.
> PAL is 50Hz interlaced, and NTSC is 60Hz interlaced.

Except for PAL-M, which is PAL but 60Hz interlaced (Brazil uses 60Hz mains frequency).
For me a major disconnect here - and this is always the case with management - is that what management means differs greatly from one organization to the next. For instance, I would consider all of those: "how one interacts with product managers, prioritizes features, determines architecture, distills architecture to actual tasks, and guarantees that those tasks get completed in a timely fashion." senior engineering tasks, not engineering management tasks. Of course, line managers often are going to be also senior engineers who do senior engineer things part of the time, so these aren't inappropriate per se, but engineering management, to me, is more about people and organization management. Employee evaluation, hiring, empowering, professional growth, organizational growth, that kind of stuff as opposed to making product/project/engineering decisions, which should primarily be steered towards product management, project management, and/or senior engineers. With that said, at a lot of places - and I think this is what every organization drifts towards if you don't try hard to fight it - engineering managers are expected to manage projects and provide technical leadership, with people management responsibilities merely being used to give engineering managers the stick to perform their primary duties.
The story of why parts of the US used 25 Hertz power instead of the standard 60 Hertz is interesting. Hydroelectric power was developed at Niagara Falls starting in 1886. To transmit power to Buffalo, Edison advocated DC, while Westinghouse pushed for polyphase AC. The plan in 1891 was to use DC for local distribution and (incredibly) compressed air to transmit power 20 miles to Buffalo, NY. By 1893, the power company decided to use AC, but used 25 Hertz due to the mechanical design of the turbines and various compromises.

In 1919, more than two thirds of power generation in New York was 25 Hertz and it wasn't until as late as 1952 that Buffalo used more 60 Hertz power than 25 Hertz power. The last 25 Hertz generator at Niagara Falls was shut down in 2006.

Details: http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=4412948
Game Artists should have imagination vivid enough!
Historic Tesla Achievement, First Model 3
From what I understand, most construction and other raw materials are all measured in metric units, then converted to imperial at final sale if needed.

For instance, a 4 x 8 foot sheet of plywood down at Home Depot isn't really 4 x 8 feet; it actually has an imperial measurement of 47.938 x 95.938 inches, which is approximately 1217 x 2437 mm - the standard metric size is 1220 x 2440 mm:

http://cwc.ca/wood-products/panel-products/plywood/sizes/

Thicknesses (as noted in the table too) have similar "whole" metric numbers. You see this also on some (not all) general materials sold to the American consumer public - the actual material is metric sized, but marketed with imperial measurements.

I think this is done both for cultural reasons, as well as just "momentum" and that the public is used to it. But the reality is (almost) everything is now metric, the public just isn't fully aware of it yet.
Only if you have cross-site referrers enabled.
I think this is a rather special usecase, this makes sense with inhouse applications where something like this might be common, but probably not something you want on the public api of a shop.
"A half liter is too small and a liter too much"- Why the UK still uses the pint in bars.
>The momentary RMS in some Moody Good tracks can actually hit _above_ 0dBFS.

It's about the dynamics (or lack thereof), not just about the distortion (if it's not clipping to just white noise 0dBFS is not the DAW limit anyways).
Testing the PCG random number generator
In tptacek's other post from two months ago:

> For almost every use I've seen in the real world, JWT is drastic overkill; often it's just an gussied-up means of expressing a trivial bearer token, the kind that could be expressed securely with virtually no risk of implementation flaws simply by hexifying 20 bytes of urandom.

This is then to say "generate a random number, give it to the client, accept that same random number in the future as evidence of the client's authorization". A familiar form of that would be a session cookie whose content was generated by a cryptographic random number generator. The session cookie is an index into a database that indicates the properties and authorities that that particular session does or does not have.

Now I guess the reason people may like JWT is that they don't have to have a database or store of tokens that they're issued and what authority each one connotes, because they can verify the signatures on the JWT and then believe the payload. And one system can issue authorizations that another system can consume without direct communication between the two. I think these believing-the-payload properties are a part of what Thomas doesn't like.
Basically, avoid literal (insecure direct object) references to resources where possible so you have fewer areas where a server can goof authorization checks. Preempt the possibility of a server expecting any direct reference and structure your API to only load resources from a backend, not the user's input.

This goes hand in hand with abstracting all authorization checks to a single gateway/middleware layer that each call inherits, rather than a spot check per call or a group of checks for different groups of calls.

(This is in addition to what 'lvh and 'tptacek have said already.)
> there may never be another version of "Is This It".

Which is a shame. Hell, their first three albums strike me as pretty poorly mastered with all of the clipping on some of the louder tracks.
Interesting you say this! Maybe a blog/medium post explaining the intricacies would help people? Are course notes available online?
Sure. The USPS has a monopoly on first class mail. Market share = 100%. The government prosecutes anyone else who tries to do it.

Up until a couple years ago, in Washington State, hard liquor could only be sold through state stores. 100% market share.

The plumber's union is a monopoly. It is illegal to hire a non-union plumber. 100% market share.

Anyone holding a patent, trademark, or copyright has a monopoly. 100% market share by law.
It seems like the algorithms aren't that complex, after all they have to be completed in one day. There might be more value in something like, 12 algorithms/side projects a year. Enough time is had in a month to actually develop something meaningful, not necessarily an entire side project but a deep understanding of a specific algorithm.
I think I see what you’re getting at. If I create an empty mutable list and send a reference to it to two different threads A and B, where A adds an integer to the list and B adds a string, then it’s nondeterministic which thread raises a type error.

And degrading the type to a union (int ∨ string) as I mentioned is still nondeterministic even though unions form a lattice—I can recover determinism when writing to the list in both A and B, but supposing A writes first, B writes second, and then A reads expecting only integers, it gets a type error because it hasn’t checked for the string case.

But I’d argue that 1. this is bad form and you want a type error somewhere and 2. you have this problem already with type-changing mutable references in a dynamically typed multithreaded language. (Say just “int” and “string” instead of “list of int” and “list of string”.)
I agree with both of you. One one hand, the writer does understand the words they are using and uses them correctly.

On the other hand the author clearly eschews words less than nine characters in length.

Random grab from middle of article:

"focusing too intently on quantifiable outcomes obscures what the essence of education, in prison or otherwise, is truly about."
I've filed a pull request to include a CSP technique I've started adding on some of my apis:

https://github.com/shieldfy/API-Security-Checklist/pull/5
I just had a stent. I stayed Friday night, Saturday Morning surgery, and left Sunday Morning. My bill was almost $100,000 USD (less than $2,000 short).
>With a high dynamic range, a headphones listener may feel the need to adjust the volume several times in a song to boost the clarity of softer sections or to make louder sections more comfortable to the ears, depending on the listening environment.

Softer sections are created and meant to sound softer though. Boosting the volume only in certain sections is more like making your own mix...
There was a time in the mid-1990s when certain models of vehicles had both metric and imperial fasteners on them; made wrenching on them a major pain. But today, though, everything is metric.

You're right that consumer marketing is still toward imperial. I think it's just going to be a slow process of gradual weaning away as older people pass on. I'm personally of a "in-the-middle" generation (X) - I tend to be more comfortable with imperial units, but if metric is required, or I think it might be a better measurement to use (depending on the purpose), then I'll use it instead.
Intel Inside was actually a tricky way for Intel to undercut their competitors.

You had to apply to the Intel Inside option. You don't need to do anything to avoid it. If you are accepted, you get a kickback from Intel for every chip. Part of the condition is you put a little sticker in plain site.

Any manufacturer could have shipped their machines without the Intel inside sticker, they just wouldn't get that moneyback.
Why would you need to introduce your co-workers to Emacs? I have recently got in touch with clojure and developed in atom with parinfer.
Was I missing out on something or is the difference between clojure and common lisp decisive?
Possibly part of the reason that other manufacturers did join the programme is that they thought it would help them sell more of their PCs. That was unlikely to be the case with Apple, who had their own marketing and didn't need a sticker to sell a laptop.
There is nothing in the OP that shows them fighting. Couldn't find anything on Google either, or on their website. If you have any actual specific evidence of what you claim, show it. Otherwise I'd have to conclude you're either delusional or deliberately defaming a humanitarian group.
Info on Chinese drilling techniques, though little on pipes.

http://csegrecorder.com/articles/view/ancient-chinese-drilli...
> cause a problem

The "problem" was that kerosene prices dropped 70% under SO.

The real problem was that Rockefeller was rich, and then (like today) a lot of people just can't stand the idea that others are rich.

If you're really interested in going beyond soundbites and understand what was happening, I really recommend Chernow's "Titan". Chernow actually agrees with you, so you can't argue his book is unfair. Chernow's opinions, however, are not congruent with his presented facts in the book. He's just so convinced of Rockefeller's evil nature that he is blinded by his own narrative :-)
ZIP Bombs Can Protect Websites from Getting Hacked
Money is fungible, so de facto you got a lower price.
Most of us left ms years ago. Whats the hold up?

Ubuntu is a fine OS.
Yeah the newest version of rebass uses styled-components[0] under the hood which does the same thing as axs does. (generate an actual stylesheet with classnames)

See my article about styles in JavaScript and the difference to inline styles here: https://mxstbr.blog/2016/11/inline-styles-vs-css-in-js/

[0]: https://styled-components.com
17th Century Shopping List Discovered Under Floorboards of English Home
> I approached him with my biggest concern: “Please tell me we won’t have to put the Intel Inside logo on our Macs.”

> With a big grin, Steve looked me in the eye and said, “Trust me, I made sure that’s in the contract.”

Isn't that all there is to it? If you don't want an "Intel Inside" sticker slapped on your computer, you negotiate it in the Contract.

Was Intel that aggressive that they wouldn't sell the chip unless you slapped their sticker on your computers?? What am I missing?
Personal Developer Can Beat Big Company with User Support
> So many crazy machines were built before there was either a need or an effective way to standardize anything power related.

One of my favorite, somewhat related, such machinery was those multi-pole "generators" that were used to create carrier waves for radio transmission between the thin era of spark-gaps and vacuum tube oscillators.
Note: The library rebass uses, styled-components, doesn't use inline styles. It takes your styling and injects it as an actual style.sheet with automatically generated class names! This means you have the full power of CSS at your fingertips without having to resort to component state for e.g. hover.

See this article for more information about the difference: mxstbr.blog/2016/11/inline-styles-vs-css-in-js/
Do they really use pints? Most new 'pint' glasses I see are marked 56 Centi-litres.
I easily put 30 hours a week in getting my 3 yr old dressed, to daycare, entertained while my wife makes dinner, and on weekends. My wife puts in similar time.
Best VPN for Kodi and Amazon Fire TV Stick
Yeah, in my experience a lack of centralized authorization checks is one of the most sinister issues in typical API construction. And I've seen pretty wonky reasons (relatively speaking) for not wanting it ("it would take a lot of refactoring", or "that presents a single point of failure").

If you don't set up centralized auth checks and instead prescribe !!!CONSTANT VIGILANCE!!!, you're just setting yourself up for an auth bug in a hastily submitted pull request at 4 pm on a Friday afternoon, when someone is lethargic and ready to head out for the weekend. The code is going to get committed, then pushed to production after three people write a quick "LGTM!" Three months later a bug bounty is going to come in with a snazzy report for you (hopefully).

The better thing to do is 1) abstract all authorization checks to a central source of authority and 2) require the presence of this inheritance for tests to pass before deployment.
The original paper of LISP by John McCarthy
http://www-formal.stanford.edu/jmc/recursive.html

Or the more accessible explanation by Paul Graham
http://www.paulgraham.com/rootsoflisp.html

There are only few primitives and no such things as RPLACA, RPLACD, and NCONC.
Google Cloud Developer Advocate here.

Go for it as long as you understand the downside. It's possible that all instances get preempted at once (especially at the 24hr mark), that there isn't capacity to spin up new preemptible nodes in the selected zone once the old instance is deleted, etc. New VMs also take time to boot and join the cluster.

If you are just doing dev/test stuff, I'd recommend using a namespace in your production cluster or spinning up and down test clusters on demand (which can be preemptible).

If you have long running tasks (like a database) or are serving production traffic, using 100% preemptible nodes is not a good idea.

Preemptible can be great for burst traffic and batch jobs, or you can do a mix of preemptible and standard to get the right mix of stability and cost.
True but think about this though, Hunter S. Thompson started out as a sports writer. Sports is a big area where this is used currently. Gonzo journalism wouldn't have even been a thing if it was all robo-writing at the time.

I think it comes down to flavor/style. Even in food for instance, yes a robot can make a meal but a chef can make a dish (maybe later reproduced by robots but still). There will always be a need for style, which is really hard to automate.
If any Back-end and Mobile engineers from SoundCloud is looking to make a transition into healthcare. do get in touch jobs[at]outcomes4me[dot]com or visit this landing page outcomes4me.com to see our open positions.

Short term contract-based jobs can also be arranged if you are just looking for something to generate a little income while you explore the market.
There's more to the history of DirectX and OpenGL than you may be aware of.

Personally, I believe Microsoft helped to engineer the downfall of SGI, via the whole Fahrenheit graphics "co-operation" - which also led to SGI making Windows NT workstations (in place of Irix).

That isn't to say that SGI didn't have some bumbling management of the time, but I do think that Microsoft took advantage of the situation to get them to chase a red herring to accelerate their demise, while also gaining a lot of new knowledge and IP via the sharing agreements they had for Fahrenheit.

Then again, had SGI not imploded, we wouldn't have NVidia today...
So I'm developing a simple SAAS with little to no private info and where failure isn't critical.

For initial release I build a page that uses html buttons and basic javascript to GET pages, passes a key as a parameter, and uses web.py on the backend.

It seems like it would be a lot of work to implement the suggestions here. At what point does it make sense?
I prefer to read books where the author tries to prove me wrong. Books that agree with me are boring :-)
They are in the Lisp 1 Programmer's Manual, also dated 1960.

The white paper doesn't reproduce the entire reference manual; what are the odds?
Each Google K80s is one GPU or 1/2 of a K80 board, so technically you are correct that a Google K80 GPU is half of a K80 board. However, they are offered in passthrough mode and achieve full performance. If you want a whole K80 board, attach 2 K80 GPUs to a single VM. You can have 1, 2, 4 or 8 K80 GPUs attached to each VM in GCP. (I'm one of the GPU product managers at Google Cloud).
If you're single 105k in DC is amazing. If you have a family, you will have everything you NEED, but you won't be living by most peoples' definitions of "very comfortably".
>"No, it's because, to properly do "science" you can (generally) meaningfully only ask a single question at a time."

I have never heard this before and do not see why that would be the case... it sounds like something a person unfamiliar with science would make up.

>"This is an observational finding, not an investigative one. That means these specific scientists are there to observe and document the event, not tell us why it happened. That's someone else's paper, which is probably being written right now."

This seems to presume the "observing" scientists are less familiar with the literature on their topic of expertise than all the random internet posters who have already linked it to climate change.

It is either that or everyone has somehow avoided looking at the relationship between the breakup of the ice shelf and climate change (which I find totally implausible, if that is true I will suspect there is some type of mischief involved here).
Money is fungible, so de facto I got a lower price on my house by eating cheap ramen noodles for lunch.
> The team say they have no evidence to link the growth of this rift, and the eventual calving, to climate change

So? No single event can ever be definitively linked to climate change. Glaciers calve, sometimes dramatically, with or without climate change. Climate change just makes it happen more often. (Until, of course, all the glaciers melt completely. Then calving will happen less often.) So the fact that a team of scientists can't find evidence linking one event to climate change is wholly unsurprising. That doesn't mean that climate change isn't happening, or that this event should not serve as a reminder that it is happening, it is caused by humans, it is an existential threat to civilization, and that we could stop it (or at least mitigate it) a lot more effectively if there were fewer people burying their heads in the sand and raising specious arguments.
I try to limit it to the following:

US Gamer: https://www.usgamer.net

Giant Bomb: https://www.giantbomb.com (I'm premium subscriber)

Ars Technica: https://arstechnica.com

NeoGAF: https://www.neogaf.com (I try not to sometimes as it's a time sink, but it's fun, mindless and stressless.)

and

Hacker News of course.

I try to stay away from Reddit and as it's a time sink for me and I find can stress me mentally.
Undersea cable has been HVDC for a while, using [1]mercury arc rectifiers and inverters to do the conversion.

The interisland hvdc link in New Zealand[2] was still using some mercury arc equipment as late as 2012

[1] https://en.wikipedia.org/wiki/Mercury-arc_valve
[2] https://en.wikipedia.org/wiki/HVDC_Inter-Island
No picture. Saved you a click
Have you looked at expected lifetime medical cost data? Please do so. It's not "a small amount". And where do we draw the line? We could spend an arbitrary amount of money pushing medicine down the diminishing returns curve until we bankrupt the entire society.
http://www.metafilter.com/

http://lesswrong.com/

http://www.econlib.org/, https://www.cato.org/, https://mises.org/ (disclaimer: austrian econ slant)
I have no information on the voltages used in the early AC grid but. In the US distribution is 15kV. So the turn down even for 240VAC is 60 to 1. Some experience with pre WWII house wiring says 20-50 amp service was common. The difference between the economics of AC vs DC might have not been so stark when people were running a couple of 60W lights.

[1]Seen three old houses run off two 20amp fused circuits.
Ah, I see you're of the much more enlightened opinion that everything you earn is due to and owned by the government, and anything they let you have is due to their own benevolence and good grace.
Extensive discussion of original article: https://news.ycombinator.com/item?id=14707674
Car culture forms a positive feedback loop and perpetuates itself just like many other things. Everyone has a car. So you build a lot of parking and don't worry if campus is miles away and not connected to transit. So everyone has to have a car. And so on.

As long as it's the predominant style and no one minds the costs it'll go on indefinitely. From other areas of the country (Washington DC, Los Angeles) it can be really bad for a really long time...people will complain but they won't change.

This being such an American cultural thing too, the pain threshold is very high.

Most people take jobs despite bad commutes and inaccessibility without a car. So people are actively voting their priorities and this isn't one of them. Bad for time, money, and environment, but hey life is busy, most everyone has other fish to fry.
Ex claims ‘Manhattan lifestyle’ corrupted her doting husband
Maybe you didn't read the GP's comment but that's not what we're talking about.
Of course, the contract says you pay a higher price if you don't have the sticker.
Apple has more market power than you think -- they focus on a few models, those models sell like hot cakes and Apple pays for guarantees to get inventory. For Intel that means their factories keep pumping out chips like clockwork and inventory is low.

Dell or HP sells more units, but in 300 or more SKUs each. Apple is different enough to get better terms.