skysight-inc/HackerNews huggingface dataset:
> It's considered unethical for doctors or lawyers to have their work supervised by anyone who isn't a doctor or lawyer. They enforce the rule through professional conduct rules and boards. the result is very high prestige, pay, and working conditions for people with similar skills and education to programmers.

I've supervised lawyers, though I'm not a lawyer. I know the same applies to other people with regards to doctors. The trade establishes rules they can't violate, but there are a ton of caveats on that. Regardless, those restrictions are actually needed by the organizations for specific roles. If a programmer was needed in a similar way for a specific role, it'd largely work out the same way. The main difference is there'd be no independent review board that has no idea what is going on in the day-to-day unless otherwise alerted.

The prestige/pay/working conditions thing is more a result of a trade group, and the consequent standards for people even being part of the trade, than due to supervision by those who lack skill expertise.

If you restrict yourself to the subset of programmers who have similar education, training, and professional validation processes as doctors & lawyers, I think you'll find a lot of prestige, pay, and quality work conditions (lawyers and doctors will tell you that it isn't quite as good as you imagine anyway).
What makes a rockstar? Their audience.

There are more web devs or web devs wannabes in the world ready to consume content from more experienced ones, making them "rockstars" as you call.
It's interesting that everyone assumes Apple's supply chain is superior to all of the auto companies. When looking at a Cost of Goods Sold basis, all of the big auto companies spend far more money on their products than Apple does (GM's COGS is several tens of billions higher than Apple's) -- and their margins are much smaller, so managing their suppliers and logistics matters much more to the auto companies' bottom line.

A single car has ~30,000 parts.. an iPhone has, what, a few hundred?

Why is it a given that Apple is going to be successful at doing something that they've shown no skill in actually doing?
Anyone can comment on its ability to scale? Not sure exactly what to ask about (I guess performance?), but do you think this could scale to say 200 million people?
AFAIK Chrome comes with its own NSS certificate store and doesn't respect the system certificates. Firefox does the same.
I'm not saying those studies you're referring to are wrong, but I do wonder if the way they framed their hypothesis led them to a false positive.

I agree with the 'mood amplifier' description that MLR gave before. It gives you some temporary courage to live more boldly. With this study, did they try and provoke a reaction from the drunk people?

I also think it misses the larger picture. For example, you mentioned about your friends who are adorable drunks, where are the studies that measure adorableness when drunk, or any other traits of inebriated individuals? Why does it always have to be about the negatives?

Don't get me wrong, I totally accept that our drinking culture has some hugely negative aspects, and I'll be glad if the upcoming generations enjoy socialising without it, but I also believe we shouldn't rush to see it without its merits too. Alcohol can make people do horrible things (hurting others being the main one), but it can make people do great things too (including being more compassionate), is this contradictory? At a stretch you could say courage/confidence is at the centre of both.
Call me an ahole, but I really think that web dev does not require nearly as much deep knowledge of computers as an engineer working on lower levels of the stack. Each web app usually solves the same tired problems again: interface with a db, present data, cache stuff, handle user accounts etc.. There is some meaty stuff - perhaps caching and serious performance optimization, but most of a web app is either front-end CSS stuff, or interfacing with a DB to fetch data.

Yes, there is definitely work to be done in making a web-app, and i don't think its easy at all to get a website to be really fast or get the styling right across 100s of devices, but its not always technically challenging work IMO. I am NOT saying that web devs are worse, but yes, I am saying that the job generally requires less deep technical knowledge, and perhaps more of other skills i know nothing about :p This is the rationale for why I choose not to go into webdev, because i love solving meaty problems. I would love to hear your perspective and be proven wrong though.
FT: Amateurs beat experts in predicting tech trends
I'm most productive at work before lunch. I like to get in before 8 am and leave around 4pm. This leaves a lot of time in the afternoon for whatever.
No, you prototype out the assembly line when you are working on it (actually not that different from how assembly lines are designed), though I guess in some cases you sell the assembly line itself, rather than the services it provides or the products it produces.
I don't really see how 6a is open for interpretation. If you use a library licensed under LGPL2.1 or higher the user must be able to replace the library with a modified copy, this is why Mono cannot be used on iOS or Android without a commercial license.

VMWare is a pretty scummy company, thankfully open source virtualization has come a long way - it's not 100% yet but oVirt does a pretty good job at replacing vCenter IMO.
When that mistake might be very costly litigation-wise, and anything you say/do might be brought up in court, it's time to break out the business speak and obfuscate like there is no tomorrow.
That would depend on the nature of the language of the NDA. If you have no example language, you're right, there is nothing to dispute.
Maybe because similar things have already happened. Columbia has a small problem with escaped hippos originally brought in by Pablo Escobar.

http://www.bbc.com/news/magazine-27905743
Spread more slowly is an understatement, a critical gene is deleted so that the virus cannot replicate in healthy cells. Also, it's a virus that causes cold sores. Not something you want your family to get for no reason, but not really horrifying either.
>Don't mistake that for approval of what you did.

If Aaron can answer though, I am curious if he was planning to get back into YC with flymaids?
Totally agree with the "Every CPU cycle matters". It might be more easier to save cpu cycle by saving I/O, utilizing data locality (with in datacenter racks) or even better serialization (binary, columnar or indexed).

Reducing locking and using shorter data type seem inadequate for the "Big Data" scene.
That's a shame. Gravity looks like a clever app, and the UX in the reviewer video was pretty slick. The spoon + quarter calibration is great!

This sort of thing is why I'm increasingly disinterested in developing for iOS for fun (and why most of my recent side project work has been on web apps). App review is effectively a black box since the rules are applied so inconsistently, and working for weeks or months on something only to find out the Apple doesn't like it is a constant concern. Add in the the real and psychological barriers app review imposes when making bug fixes or updates, and it makes going back to the web rather attractive. It'd be nice to see Apple make some changes to the process.

(I know I could move over to Android dev, but since I use an iPhone it's not terribly interesting for side projects - though that's my problem, not Androids's.)
I was wondering the same thing about Stripe or any of the big credit card processors. That'd be shady.
> In this model, the results of the executions of programs are also mergeable.

Not all updates are commutative.

The ordering of events in (add 1, add 2, add 3) does not affect the outcome.

The order of events in (add 1, multiply 2, divide 3) does matter.

The problem of linearity exists as soon as you have a commutative operation in a relativistic universe where information cannot be simultaneously updated in two coordinates simultaneously.

Until now there have been heroic engineering efforts to hide this from software developers. Hardware has conspired to conceal that even in a space a few centimetres wide, values can become inconsistent.

Once you have independent memory spaces, all bets are off and you are forced to pay a high price for losing the abstraction.
Are they using stripe on the new site(s)? Looks like those have all been taken down.
Or, you know, film crews:

https://en.wikipedia.org/wiki/Catalina_Island_bison_herd
Largely true, but I recall actually isolating one chunk of code and compiling with g++ just to get halfway sane error messaging around a (IIRC) template-related error. I.e. you could do worse. The primary compiler for that code was the circa-2001 ARM tools suite. I wrote a few novels worth of feedback and bug reporting to them...
Managers are the ones responsible for setting the system. Systemic problems are their fault.
My guess is the account never changed hands. Stripe can't really prevent a legitimate owner of an account from doing something stupid with it. At least, not until after the fact.
Usually the Tor client runs on the same machine as the browser, so if you have a MITM, you probably already lost (e.g. the malware probably could have simply injected its own CA root cert into your browser).
Sure but the teller then has no vested interest in keeping the facts and the story from deviating from each other whereas a liar does have that interest. So the liar can't 'fix' the story but the person that tries to be truthful has no problem.
And this is precisely the problem with centralization. It forces a Yes or No when the appropriate answer is Wu.
The leading candidate for this extinction was the introduction of humans equipped with bows and arrows into its environment through the Bering land bridge.

The African versions of big species were able to co-evolve along with humans as we developed spears, fire, etc. The American ones did not. This is why the American versions of everything from horses to cheetahs disappeared.
There's an impressive amount of data.

The "Elections" page [0] - with the color-coded maps of each election - show some of the extreme shifts, the difference between 1932 and 1976 is incredible.

It's not obvious (they've put it at the bottom of the left navigation column) but some pages - such as "Documents > Messages and Papers of the Presidents" [1] - have a search feature to search the data by date/keyword.

[0] http://www.presidency.ucsb.edu/elections.php

[1] http://www.presidency.ucsb.edu/ws/
Is the analytics on the phone or would the user be trusting you with a recording of every private moment of their lives?
> I know I could move over to Android dev, but since I use an iPhone it's not terrible interesting for side projects

Fragmentation and the frequency of device- or vendor-specific bugs and other issues take a lot of the fun out of Android dev for me.
Yeah, I get your position (hopefully!), but I think I'd rather hear from a lawyer whether this is OK or not, my guess is that it is OK.

The snippet you pasted says also:

... regulatory, and/or business requirements

A business that is going out of business may treat this data as a business asset and may need to retain it for a certain period even when they are inactive.

Most terms of service do allow for transfer of account information to third parties, and have contingencies for what happens to the data if the company goes under, and as far as I'm aware, selling that customer data is an option unless they've explicitly said they won't.

As long as the credit card data is transferred in a PCI compliant way, it's legal.

You're absolutely right that it would be a serious violation if they were to charge someone without their knowledge, it doesn't look like that's happened yet.

It's also quite possible the underlying business entity is still Homejoy with a name change. ZenPayroll* didn't have to get people's permission to charge them when they changed their name to Gusto, but it obviously helps to communicate that change very clearly!

I am pretty sure we generally agree, though, it's very clear that there are dozens of egregiously bad things being done by Aaron and his team that can only hurt them and their desired future customers.

*I said Zenefits :( :(
Maybe. That sort of nonsense may decrease the odds of losing a lawsuit. But you increase your odds of having a lawsuit, because you leave more people mad at you.

That might be a good choice for a large company, as they already have lawyers on staff, can afford to pay for a lawsuit, and have enough money to advertise away the reputational stain.

I'm not sure it's a good idea for a startup, though. Unless you are well funded, just dealing with a lawsuit could be fatal given the reputational cost, the legal bills, and the amount of founder time that will get soaked up. Personally, I'd try to be human and humane about it.
And keeping it clean!
I notice you didn't address my question:

"So, it would be acceptable to you if Google put your Google Account login and password in URI-encoded plain text in the URL of your search results? Why or why not?"

This is actually a pretty important question.

> Looking at my history 50-60% of the URL's in it aren't humanly readable and are 10 miles long...

It doesn't matter how long the URL is. It doesn't matter if you can easily read it. The Web works through URLs. URLs (and URIs) are how you access resources.

* Data in the href attribute of the a tag? A URI.

* Data in the src attribute of the img tag? A URI.

* Data in the src attribute of the script tag? A URI.

* Data in the 200 response to an HTTP GET request? A URI.

* Data in the 30[1|2] HTTP response? A URI.

* Data in the address bar of your User Agent? A URI.

> [T]he history API... has been deprecated and turned into the App Activities API...

No. It has not.

> ...my back button works just fine and there isn't a single request made when i click it...

Right. That's what the History API does. It's a strictly client-side thing. I guess you're dreadfully confused. Here's [0] the first result for "History API". It also happens to describe exactly what I'm talking about.

> this isn't even an info leak if you start a completely new query it resets the original query variable ... you'll get ?q set to query and ?oq set to query ...

> you search for query history it will set ?q to query history and keep ?oq set to query

Cannot repro. Here's what I see:

* Use omnibox to search for "thing": o=thing&oq=thing

* Use google search page that loads with results for "thing" to search for "things": o=thing&oq=thing#q=things

* Use that same page to search for "dingus dongus": o=thing&oq=thing#q=dingus+dongus

Chrome 46, using the default Omnibox settings.

[0] https://developer.mozilla.org/en-US/docs/Web/API/History_API
We still don't know how that would have worked in practice. Even skilled people have trouble making trust decisions reliably for everything and while we'd avoid the compromised CA threat I'm certain we'd start seeing equivalents like dishonest or incompetent notaries – and those might last longer because fewer people see the dodgy results since not everyone is using the same set of notaries.

If it became popular, it's really easy to imagine something like the Great Firewall being configured to block outside notaries to encourage people to use local notaries which are still under the control of the local authorities.

That's not to say it's not interesting work or potentially a solid improvement, only that I would be extremely hesitant to make absolute statements about an untested internet-scale security protocol. The approaches we're seeing work now do so because they're adding to well-understood protocols (e.g. HSTS, key-pinning, etc.) or don't change the trust model (if Google goes rogue, Chrome users are already screwed).
No, its not. This problem detected by a third-party due to a recent industry initiative (Certificate Transparency). Now Google has doled out appropriate punitive measures which will greatly reduce chances of this happening again.

The industry is moving forward and doing lots to improve.

Lets also not forget a hugely important point that there is no evidence of harm from Symantec's action. They were just embarrassingly stupid and irresponsible.
While I understand why people are irked (to say the least) by this, I can understand the technical reasoning behind it.

The hash part of the URL, (#andmorestuff) is not sent to the server by the browser, however the query string is. (?var=stuff&another=otherstuff)

Using this to send the search to the server is smart, since the server can respond with data without an additional round-trip AJAX request. However, everything in the URL, other than the hash is read-only by client-side scripts. So, if you want the URL to reflect the search, you can either a) reload the page using the query string, or b) follow the single page app methodology, and manipulate the query string with the data, and change it using an AJAX request.

Google's interactivity, with the smoother feel of not seeing an entire page refresh (plus potentially less data being sent over the wire after the initial load) could be simply stored in an internal state. However, should the user refresh, the search would be lost. If you try going to a Google search with a search query hash, you'll notice a brief delay before the search results are displayed.

For example, in this link: https://www.google.com/search?q=original#q=newsearch

The page loads, but there's an AJAX request to the /search route with the hash-specified query, with query string parameters to specify how the data should be served. Still, the client-side script cannot strip the query string of the previous search without a full page reload.

While the info leakage is annoying, it's unavoidable in this strategy.

Note: The browser history, and subsequently the URL can be manipulated through the History API's pushState, which could be a direction Google could go in, but IMHO, the hash approach is viable as well.

https://developer.mozilla.org/en-US/docs/Web/API/History_API
With all of the conservatives crying foul over "hyperinflation" as the US pushes QE just a little bit to get us over the financial crisis... we will virtually never have a political environment that will explicitly devalue currency to encourage job growth here in America.

Just saying, not enough support to do what you want to do.
I'm new here what's this site all about?
Signed up because the website has little to no css which is kinda funny but genius in a way.
They probably just exported a database of credit card tokens into a PCI-compliant system (Stripe, Braintree or the like.) The motives and method are equally shitty, but at least get some solace in assuming that your credit card number is just not out in the open.

Now... how secure this transfer of tokens was, no idea. So there could be a DB dump somewhere with a token to my credit card, and anyone can use it to start charging from it. I'll keep an eye on my bills.
There are still lions in the Americas today, just most people don't think of them[1][2][3] as such despite being nearly as large as their African counterparts. Same subfamily as cheetahs[4].

[1] https://en.wikipedia.org/wiki/Cougar

[2] https://en.wikipedia.org/wiki/Jaguar

[3] https://en.wikipedia.org/wiki/Florida_panther

[4] https://en.wikipedia.org/wiki/Felinae
This isn't theoretical, I've implemented this system already in code: https://github.com/amark/gun . Just spoke on it in London, Germany, and the USA.

I think people need to know that this discussion is no longer happening only in the hands of academics, this is now available to developers - with or without the academic side.
Most likely they just have the same API keys
I was also thinking through which rules would apply here. (What entity owns a Stripe account? What constitutes a transfer of data? How does this case differ from say, an acquisition?)

The medium article only shows info you can get from a Stripe card_id request. Not using https on that page is troublesome, but I don't think there's any evidence to suggest FlyMaids (or even HomeJoy) ever had access to actual CC information.

It seems more likely that this depends on Homejoy's ToS/Privacy Policy. (Although it's certainly possible the transfer was done in a way that violates Stripe's policies, I'm just not familiar with those)

Edit: It might even be the same business entity with different d.b.a names. Good discussion here: https://news.ycombinator.com/item?id=10468161
I don't think the distinction is the one you're making it. The original intentions of languages are accidents of history (Java was originally for set-top boxes), and the likes of Python and Ruby are perfectly legitimate languages. The best options on the JVM happen to be typed, but there are good untyped languages and bad typed languages, and parochial typed languages and general-purpose untyped languages too.
You could do Django without a DB, but the framework kind of assumes you will have one.
> It's considered unethical for doctors or lawyers to have their work supervised by anyone who isn't a doctor or lawyer.

With lawyers (more familiar there than with doctors) I don't think that's usually the case; the ABA model rules don't prohibit lawyers from being supervised by non-lawyers (though they do prohibit lawyers from co-owning law firms with non-lawyers, or sharing legal fees with non-lawyers, and they do prohibit lawyers from allowing their employer to "to direct or regulate the lawyer's professional judgment" in providing legal services -- whether or not the employer is a lawyer; this doesn't prevent supervision of the lawyer as an employee, it just essentially means that the lawyer doesn't have a Nuremberg defense of "just following orders" for professional nonfeasance or misconduct.)

http://www.americanbar.org/groups/professional_responsibilit...
I would naively expect running a tunnel boring machine 1 mile to cost a lot more per mile than running it 2 miles.
An unfortunate name clash with https://github.com/openstack-infra/zuul really threw me there for a bit.
Kinda off tangent, I thought it looked super familiar, and then realized that example painting of the guy raising a glass is based off this:

http://www.c-ville.com/wp-content/uploads/2013/05/GATSBY.png
Not all updates are commutative, but there exists an entire class of algorithms that solve for each of these scenarios - see CRDTs, DAGs, even linked lists.
I second the mentioning and advocating of this feature. For my main Chrome user, I have StayFocusd installed, and its workings make themselves known in various debug outputs, so I switch to a stub user setup on Chrome when doing dev work. I also switch the theme so that I subconsciously associate the non-logged-in, green-colored browser with "hey, it's work time". On a separate user instance, I'm logged into Facebook but have otherwise thrown away the password...it's amazing how the friction of a simple clicks (it only takes a right-click to pop-open the available Chrome users, then left-click to select one) can almost by itself break the reflexive whim to check social media accounts.
This entire comment is just nonsense. Web development is equivalent to any other level of the computing stack. That is, there are good developers working on solving complex problems, and bad developers churning out mediocre software that doesn't really do anything "meaty".

I see absolutely no evidence that web development is any less technically challenging than any other field – the fact that there are loads of developers churning out cookie-cutter CRUD apps doesn't mean that's the whole field.
Really cool app, and a shame Apple rejected it. Using a spoon was a very clever idea.

Why did you choose to display weight in grams to 3 decimal points when the measurements are only accurate to within 3g? It would be better to not display the values after the decimal point, so you don't give your users a false sense of accuracy.
Then why big data land is dominated by JVM-based frameworks?