skysight-inc/HackerNews huggingface dataset:
Suppose ABNB shuts down tomorrow and all the owners decide to put their units on the long-term rental market instead. OK, you've got your 20% bump... for one week. The open house starts, an hour later those units are all rented, and how do you suppose prices look the next month? 2000 units of rental housing is 2000 units of rental housing. The right comparison is between the number of units used for short-term vs. long-term housing, not between the number of units used for short term rental and the number of long term rentals available right now.
What does the bleach do?

And she's a biomedical engineer and works with a lot of dangerous viruses both from humans and animals. So it's not just drugs that are getting put into the water sadly.
I think he's assuming the government will have a much harder time proving undeclared income. Probably not true in Uber's case, but contractors are pretty notorious for giving generous cash discounts.
So can pigz http://www.zlib.net/pigz/
Ownership and the resulting pride in workmanship makes a big difference.
QA Team is great if it is a team of developers who are interested in QA and test automation/tooling. Not so cool if it's a department full of people who make low hourly wages to execute manual tests and don't write code.
The article is not talking about Windows, so folks here aren't either. Why are you surprised that folks are uninterested in Windows?

I've preferred Mac systems for longer than most of the HN crowd has been alive, so I understand what it's like to feel ignored and in the minority. For years, Mac users were treated as pariahs. The tables have turned, and as someone who has been in your situation, I should have great empathy for your predicament.

And I do, but your tone in general -- and your last sentence in particular -- makes it very hard to empathize. Microsoft used its near-monopoly status to stifle innovation for years, and many of us have figurative scars that will never heal. You seem to think that they are making great strides (while I see them as half-hearted overtures), but either way I'm not about to "throw them a bone." Their decades of misdeeds, in my eyes, will not be expiated so easily.

Perhaps Microsoft will someday be worthy of forgiveness, either from the perspective of morality (e.g., Mozilla) or product excellence (e.g., Apple). Until that day, Microsoft will continue to reap what they have sown, given no more attention than they have earned.
Top 6 Excel Tricks Must for Every MAC User
But trivia is still worthy of knowing about, however tired and overdone, or dated and played-out. Just like, if it were XKCD yesterday, it was The Far Side twenty years ago.
This is why gzip rocks, the relatively low memory usage, in particular for compressing things on the fly.
Doesn't bzip2 have a concurrent mode that those others don't?
> Yes, because a private entity completely owning natural resources like lakes and forests, will completely prevent those resources from being ruthlessly exploited.

The statement was heavily sarcastic.
Small nursing homes are in the same boat. My wife works for one such small nursing home and they had to hire a contracting company to develop software for them to move everything from paper to electronic forms. None of the employees know how to write code and they have to have an electronic system to comply with federal laws.

I myself am disabled, but I used to work for a large law firm in developing apps and web apps for them. I wanted to develop software for small law firms, but it never went anywhere. There was never any interest in it and I assume most small law firms keep data in Excel sheets and use VBA macros to automate things. Stuff they wrote themselves. I tried to write a prototype app in Visual BASIC 6.0 in 2003 but never got any interest in it. I never modernized the app to modern technology either.

I've found that many small businesses exist that need solutions and might not be able to afford to pay to develop software for those solutions. Which is why I wanted to develop open source business apps and web apps so they at least have something they can download and customize for their use. But I never got around to it, been busy with real life stuff.
Telegram for PC
This isn't surprising.

Microsoft switched to this model a few months after Satya took over.

For the majority of Microsoft teams it worked really well and showed the kinds of results mentioned in this yahoo article. Look at many of our iOS apps as an example.

But for some parts of the Windows OS team apparently it didn't work well (according to anonymous reports leaked online to major news outlets by some Windows team folks) and they say it caused bugs.

First of all I think that argument is semi-BS and a cover up for those complainer's lack of competence in testing their code thus making them bad engineers because a good engineer knows how to design, implement, and test their product imo. But I digress.

I in no way want to sound like a dk but as an engineer it is your responsibility to practice test driven development but that's not enough.

Like reading an essay you usually can't catch all of your own bugs and thus peer editing or in this case cross testing is very useful.

You should write the Unit tests and integration tests for your feature

BUT

There should always be an additional level of end to end tests for your feature written by someone else who is not you.

Everyone should have a feature and design and implement it well including its Unit tests and integration tests BUT they should also be responsible for E2E tests for someone else's feature.

That way everyone has feature tasks and test tasks and no one feels like they are only doing one thing or stuck in a dead end career.
How Facebook and Reddit users solved 20-year-old mystery of a missing teenager
It's not a problem for me since I mostly use Java. However, you can probably just pipe in your data from the lz4 CLI then use that InputStream for whatever python parser you're using and you should be fine.

The biggest problem is using a parser that can do 600MB/s streaming parsing. If you use a command line parser don't try jq even with gnu parallel.
Penetration testing course: 0x01 Introduction
I wonder whether "a human in the loop" is some kind of illusion; for longer than we have had recorded history, we have killed our neighbours because an authority have told us to. In the latter half of the 20th century we nearly perfected the conditioning needed to make soldiers shoot to kill when told to. I wonder whether it will make a difference if the order is given by a human a or an AI. And if the soldier is going to shoot to kill regardless, why not just have an AI do that as well.
Also making sure you have a good automated build,test,deploy structure is important too.

It's all the little details that will determine if this system will succeed or not.

Not the overall "big idea".

Implementation of this system and the competence and willingness to adapt of the team members is key imo. At least for this issue.
It has been noted elsewhere in this thread that Martin Winterkorn was 'hands-on to the point of being a control-freak' and that there was no way in which he would not have been aware of this. Note the amount of technical knowledge present in the VW boards and at the C level is such that they could have cut through all the secrecy and other red tape if they had wanted to. It would have also been impossible to hide this from the auditors if they had simply been of the 'trust but verify' mentality that one would expect of seasoned auditors and I find it hard to believe that a company like VW (which apparently has been caught cheating before when it comes to emissions testing) would be so incompetent at this that it could have gone on for so long. All this besides the fact that 'miracles' simply don't exist and if there is one thing that sets an auditor off it is 'too good to be true'.

An ECU is not a 'big complicated thing', there is a ton of software in a car but the ECU itself happens to be one of the more easily understood parts where anything that does not have an obvious and direct function stands out like a sore tooth. There is also a very distinct point in time where the problems magically disappeared and of course it would be a simple thing to review the changes committed around and prior to that time. (Let's at least assume they have some kind of source code control system.)

If anything the auditors are more trusted than the programmers and they would definitely have had insight into the ECU code.

It is not conceivable that there is some kind of 'the cube' like conspiracy where the parts each individually look clean because one fairly large chunk of code was contributed by the Bosch company and contained a fairly explicit piece of code to detect the test cycle. If it's labeled 'process bananas' and an auditor is not able to figure out what it does it is their duty to actually dig until they understand that piece, that is what they are paid for.

So I believe that you are principally right that besides one exec and a bunch of people down from there in the org chart they kept the number of people as limited as they could but there is no way the compliance department was this incompetent unless a rookie was specifically tasked with auditing that particular engine to make sure the cheating stayed hidden. A seasoned auditor would spot this in a heartbeat and no rookie should have been able to sign off on these changes on their own.

And 'plausible deniability' is a very very thin fig leaf away from being culpable, all it takes is a single email or confession to pierce that veil and with the number of people VW is throwing under the bus (and at ever higher levels) it is a matter of time before someone decides to come clean about the whole thing.
Decompression of xz is slow and quite memory intense. I'd argue that the light memory footprint of gz decompression is better suited to the web, particularly mobile where you need to balance battery v bandwidth.
Sorry, autocorrect. That was supposed to be limited by the zero lower bound. You can't get below zero (or not much below anyway).
Proxy Check and Report – new free online tool
For this project, we were using Flask, which is a pretty lightweight framework. Even with Rails I wouldn't mind hiring somebody who didn't know it. My teams are closely collaborative and often do a fair bit of pair programming, so I don't mind learning on the job.

As to the mobile question, it would depend on the team composition. If I'm hiring the first mobile developer, then yeah, I'm going to look for somebody with a lot of experience. Probably the second as well. But for the third and after, I wouldn't put it as a requirement. As long as there are people around who can mentor, then I'd rather hire a strong developer with little mobile experience than a not-so-great developer with plenty of mobile experience.
>When going to an area with elevated tension, security, and crazed guards the gap between "weird" and "threatening" is quickly closed.

Yeah, that's kind of my point. Incidents like this aren't about safety, they are about conformity.
Definitely. My goal was for people to feel informed, but definitely not for them to feel scared off.
exactly. Wonder when Blogger is getting can'd.
The second, from the evidence available to date.
Scott Aaronson clarifies my first paragraph: http://www.scottaaronson.com/blog/?p=2586
I think that's a reasonable heuristic. But I'd still be unlikely to put the salary in the ad. Especially for this position, which was at a non-profit with a strong mission focus, we wanted people who cared about the purpose. People whose first question is, "How much can I make?" have never worked out well for me in mission-oriented environments.

When I was working in finance, on the other hand, I likely would have put the salary in if we had enough size and data to give firm salary bands.
Two people in a basement might make significant advances in AI research. So from the start, AI appears to be impossible to regulate. If an AGI is possible, then it is inevitable.

Not necessarily. AGI might be possible but it's not necessarily possible for two people in a basement. AGI might require some exotic computer architecture which hasn't been invented yet, for example. This would put it a lot closer to nuclear weapons in terms of barriers to existence.
Summary: Compatibility and decompression speed is more important than compression ratios for many use cases. Gzip is nearly universal, where lz4, xz, and parallel bzip2 are not.

The challenge of sharing internet-wide scan data has unearthed a few issues with creating and processing large datasets.

The IC12 project[1] used zpaq, which ended up compressing to almost half the size of gzip. The downside is that it took nearly two weeks and 16 cores to convert the zpaq data to a format other tools could use.

The Critical.IO project[2] used pbzip2, which worked amazingly well, except when processing the data with Java-based tool chains (Hadoop, etc). The Java BZ2 libraries had trouble with the parallel version of bzip2.

We chose gzip with Project Sonar[3], and although the compression isn't great, it was widely compatible with the tools people used to crunch the data, and we get parallel compression/decompression via pigz.

In the latest example, the Censys.io[4] project switched to LZ4 and threw data processing compatibility to the wind (in favor of bandwith and a hosted search engine).

-HD

1. http://internetcensus2012.bitbucket.org/images.html
2. https://scans.io/study/sonar.cio
3. https://sonar.labs.rapid7.com/
4. https://censys.io/
I'm one of the Keywhiz developers, and we've been considering writing such a page, though I've been hesitant to do so because I'm not totally familiar with the alternatives: I have no operational experience with Vault or alternatives, and haven't put a ton of thought into this comparison.

From my limited perspective:
Keywhiz is a system to take secrets, stored in a database, decrypt them with an HSM backed key, and expose them as files on a server. Because the secrets are exposed as a fuse filesystem, they require zero special code in your applications. Most other secrets stores just provide you with an API that requires custom integration work. You could probably even modify keywhiz-fs to talk to a Vault server.

On the other hand, Keywhiz doesn't know anything about the secrets inside it, so there's not much out of the box for secrets revocation, and other operations like that. There's also minimal secrets generation: We just provide an API to handle that. The biggest sources of secrets for us are service-to-service TLS certs, generated from our deploy system, which just calls the automation API to put the certs it gets from our internal CA. Keywhiz has a plugin system for generating secrets, but it's quite simple compared to what Vault has.

Vault also has some operational decisions that seem scary to me. They have a scheme for "unsealing" a vault with a set of secrets an operator has to input. This seems quite likely to cause an outage, while defending against an attacker you've noticed but who hasn't managed to steal the secrets out of your unsealed vault. While operating, your vault is unsealed, so an attacker who gets root has your secrets in both Keywhiz and Vault, but a service restart causes an outage. If you could somehow (via physical access, perhaps) boot a malicious OS onto a Keywhiz server, and your HSM doesn't defend against that, you could read secrets. For Vault, you also need to steal the keys to unseal. But those are accessible to humans, so that's probably easy.

As for lifetime, we don't expect Keywhiz to go anywhere. It's a crucial part of running Square. We've been using it for years now (though only open-sourced it earlier this year), and will probably continue to exist as long as the company does.

I'm happy to answer any other questions, too.
Andrew Gelman is a wizard
Right. As I've heard it discussed, they've borrowed the term "honey-potting" for this in an almost exact analogue of how it is done on dating sites.
If my experience is any guide, the difference is that there are a lot of very junior people on the market now. For every qualified applicant I got, I got at least one applicant fresh out of one code school or another. The posting was very clear that I wanted somebody with minimum 3 years experience and who could mentor junior developers, but they applied anyhow.

So if there is a smaller number of positions advertised, I think it's just because they don't have to advertise to find junior people. But personally I'd encourage you to teach your friends, as my hiring strategy in the future is to build teams that are really good at taking junior people and leveling them up.
pbzip2 output isn't universally readable by third-party bz2 decompressors (Hadoop, for example).
Not sure that it matters for the sake of argument, but the weapon system used in question was a human-piloted, human-manned AC-130 gunship, not a drone / remote platform
Latency arbitrageurs do not provide the value you claim they provide.

They consume liquidity by identifying that one individual is willing to buy at $10.02 at point A and one who is willing to sell at $10.00 at point B. These individuals would discover each other naturally in (literally) the blink of an eye; but HFTs pay to colo everywhere, they pay for 40Gb connects and ASICs. They pay for the fastest possible connections between those colos.

This means that instead of those individuals who truly create liquidity and who truly drive the market finding each other; the HFTs are able to wedge themselves into the middle of the transactions. This works because the NBBO system is slower than their systems. It works because of complex order types that benefit only HFTs (no actual investor requires a hide not slide... that's just a tool for HFTs to cut the line).

HFT does not create liquidity. It does not even out price differences. It is an entirely predatory tool to extract value that was generated by other, better men.

HFT is a place where self-righteous nerds pick everyone's pockets.

HFT is useless trash.

The only place I agree with you is that HFT-based theft, like car radio theft, is a relatively minor crime and one that is declining over time.

True market making is often algorithmic and automated, and it operates quickly. But it is completely different from the nonsense that is HFT.
Is there actual progress on this? Anyone seen it live? Because the video and site are from May 2015.
hello Janne,

You keep making these grand claims about the constitution and the law and this whole VW affair that have absolutely no basis in fact. Please stop that it is just throwing up a huge smokescreen and it measurably devalues the discussion.

I'm sure that it fits your worldview but fwiw no matter how hard and how often you write this stuff it does not make it true. The constitution has absolutely nothing to do with this, VW was not 'singled out' and you are actively harming your reputation on HN. As a German student I understand that you feel that VW has been treated 'unfair' but they brought this on themselves, BMW was tested as well and passed the test even though they too emitted more NOx than they should have depending on the circumstances, they did not use a 'test defeat device'.

From what we have in terms of evidence to date no other company has engaged in such blatant fraud in this respect as VW has. If you have evidence (as in hard evidence, not just hunches) that another manufacturer also employs a cheating device then you could make headlines the world over by sharing that proof and I for one would be very supportive of you.

But all these statements that defend VW and even suggest that VW could recover their losses because they've been treated unfairly are not based in fact and make it seem like you are of good intentions but other than that do not appear to have much knowledge of how these things work. So a word to the wise: you have but one reputation, you build it up slowly over the years and you can lose and/or damage that reputation quickly.

Please don't let your sense of indignation get the better of you and hurt your interests in the longer term.
Yeah. Especially at a startup I think you should be optimizing for engineering growth. A company that a) has very specialized language needs, and b) isn't set up to mentor doesn't sound well set up to grow quickly.
It was said below (https://news.ycombinator.com/item?id=10719751) but it's worth a top-level comment: the TPP may ruin the public domain for countries currently enjoying annual PD growth.
Wow, channels...I will just go and learn go. But for other reasons too. I dont like django anymore, because I kept continuously fighting with the framework. Its fast to work with, if you do exactly what the developers had in mind, but it gets in your way all the time, if you use your own brain.
The trouble with this is that, as a software author, it doesn't really matter if it takes 70 seconds instead of 33 to install my software. 70 seconds is fast enough, for someone who's already decided to start downloading something as involved as Meteor; even if it took one second it wouldn't get me more users. And it would have to take over 5-10 minutes before I start losing users.

On the other hand, having to deal with support requests from users who don't have any decompressor other than gzip will cost me both users and my time. Some complicated "download this one if you have xz" or "here's how to install xz-utils on Debian, on RHEL, on ..." will definitely cost me users, compared to "if you're on a UNIXish system, run this command".

From a pure programming point of view, sure, xz is better. But there's nothing convincing me to make the engineering decision to adopt it. The practical benefits are unnoticeable, and the practical downsides are concrete.
Brother MFC6490CW Driver Download
It's possible to compress and index a file at the same time, gaining both a size and speed advantage over the original. For example: https://en.wikipedia.org/wiki/FM-index
Still better to steer clear of .NET.
Yeah that is an interesting paradox. It feels wrong for an algorithm to decide whether to kill a human, but what is so much better about that decision being made by a human?

If that seems extreme, consider the self-driving car problem. 30,000 people in the US alone are killed per year in car accidents involving human drivers. What is the acceptable number of motor vehicle related deaths per year when all cars are self-driving?
Why can't the LED controller circuits come with a calibration feature that detects (with user help) the minimum level the dimmer will support, and makes that the all-black point?