skysight-inc/HackerNews huggingface dataset:
There's a really simple solution that everyone is overlooking. Stop trying to make applications in browser and actually make applications that run native on an OS. And no, I don't mean running on some trimmed down JS engine.
I love Vagrant for dev environments, but I'm not a huge fan of using it in prod. I think it's just another layer of abstraction on top of the actual metal.

In general though, I'm with you. I fell out of love with Docker a couple of years ago and I've been a huge fan of vms since.
I think it has everything to do with the technology. Specifically the technology solves problems most (almost all) organizations don't have, yet their adoption is practically ubiquitous as is their requirement to appear on a resume to get past gatekeepers. If in the end the technology is used more as a means to "produce buzz, then busy engineers, then bills" than to solve problems for their legitimate use cases it hardly is an error to point it out.
> they instead decide to hardcode usernames and passwords, it's a huge red flag.

Why? That seems like an oddly specific thing to be a _huge_ red flag. Are you expecting random data to actually surface bugs - ie: making your tests non-deterministic? Or is there some other benefit you are looking for to make it such an important criteria?
I had a similar idea way back when:

https://slashdot.org/comments.pl?sid=2284292&cid=36623386

It's likely a pretty common thought process with open source internet devs.
> you can research growth stocks (e.g. pharmaceutical companies undergoing FDA trials) and pick the promising ones

Those FDA trials are expensive. Those companies have many experts in the field that believe those trials have a reasonable chance of success. Otherwise, they would not proceed with them. Even the FDA itself believes those trials have a good chance of success. There are plenty of Wall Street analysts who are also evaluating these trials. Regular Joe is not going to outsmart all those people.
That’s not correct. The actual bet was always for a “portfolio of funds of hedge funds.”[1]

If the bet had been for a single fund, Simons or Klarman or any other hedge fund manager who has been beating the market by a large margin for 20 - 30 years could have won easily. But that bet wouldn’t have been instructive, because the world really doesn’t need to be shown that there are a minority of funds capable of winning the bet - on the contrary, it’s helpful to show that a representative sample of them fares poorly on average. Moreover, being a fund manager himself, Buffett would have been silly and hypocritical to actually support the former type of bet.

___________________________

1. http://longbets.org/362/
in a world of unlimited resources... sure. However, I, as an independent software maker, want to target as many screens as possible with the least amount of friction. I am not overlooking anything nor are the companies and other indies that target the web... that is called choosing pragmatically.
Your anecdotes as a white man are not more valuable than his as a black man. This isn't the first time you've whitesplained to a minority on HN how their lived experience is invalid.
The people here seem to be presenting extreme positions. On the one side, you can't beat the market unless you're a hedge fund or big player with special knowledge and equipment, so buy index funds or you're a naughty gambler. On the other side, we degenerate into self-creating automated trading software.

There's absolutely a middle ground here, folks. One can have a portfolio of conservative picks (index funds), self-selected individual picks, cash, bonds, so on and so forth.

This should hopefully be picked up by n-gate to make a mockery of us.

Joking aside, I'm curious what some of you who are actually paid to write front office software by Wall St. think of all of these threads.
That paper refutes very little by using adult humans. Some facial expressions are universal among human cultures and even among primates, and yes, even among mammals.

Liking and disliking facial reactions to sweet or bitter water are universal among mammals.

https://pdfs.semanticscholar.org/a511/cb9d06d0f77132cad2ba5f...

And relevant to the topic of this post and the original article, human babies will in fact smile when given sweet tastes right after birth.
>> I fell out of love with Docker a couple of years ago

Why?
In my organization, github PR threads and JIRA comment threads tend to be ignored or forgotten after their inception, and chat gets results right now. We also use Trello, Confluence, google docs, and of course email for some things. I think this sort of thing is common.

They all have their strengths and weaknesses, but it strikes me that a bigger barrier to productivity and strong organizational memory than interruptions is the overall dilution of information.

Sometimes I think that the narrowing of the available tools (channels for information), whatever the weaknesses of the chosen tools might be, would be wise.
If you're thinking of interviewing your candidates with such methods, it's worth noting that their current employment agreement might prohibit them from participating due to IP clauses (more exactly, that they require permission to release any code that they've written, even in their spare time).

This can restrict your pool of candidates quite dramatically, as most US companies seem to have their engineers sign such agreements.
Buffett is essentially following the strategy - a diversified portfolio of long-term value assets. He's able to beat the market in part because the mere hint of his involvement in a stock causes it's value to go up.

You and I don't have that ability.
Thank you. I didn't recognize the reference because I never watched the full movie. It isn't anywhere near as good as the book and I think I turned it off after a few minutes.
Who said it's a "license for magic"? That's a silly strawman.

It is however a license for doubt over certainty.

>not a human limitation

Once again, no one is sure about this.
It was just a throwaway line. I should have said municipal, but given the target audience and all. I'm not even a deficit hawk, but i thought it was funny :)
Which of the two transactions you described is the win-win?
Does it put them in my normal client? That UX is valuable.

Also, I forgot about private channels - Slack does the same thing for private channels, synchronizing permissions to join the channel with permissions to read and search the logs, which putting them in a shared site-wide search index wouldn't do.

Also Slack does multi-person direct messages.
For a well established developer, this may be true, but for newer developers, they often have to jump through a lot of hoops to prove their skills first, especially if they come from a non-traditional background and do not have a CS degree.

Do you think this issue is less pronounced with the move toward companies providing compensation guidelines up front?
How long can the index fund advice be sound as index funds are moving from following the market to making the market?

The sheer magnitude of success of the various index funds that invest proportionally to the market cap of the top 500 stocks, in aggregate, could have the effect of perpetuating the status quo, masking indicators from non-index investor activity.
I'm not arguing anything. I'm just expressing an opinion that the comment you made is disingenuous since it's entirely centered around a claim around impossibility that no one made other than you.

The original comment that said "you will lose" is in jest, obviously. Someone who's confident that they wouldn't lose wouldn't be here reading a step by step plan to become a millionaire as they'd already be far beyond that.
This article seems miss the mark on reproducibility. It’s not, “Oh how do I run pip install?” It’s the data. It’s the cleaning. It’s knowing what little script you ran to massage the data a bit. It’s all the stuff that happens after you install software. Docker doesn’t help you with any of this, and none of this was even discussed.
Better non-paywalled article covering a larger set of new drugs
https://www.bloomberg.com/news/articles/2018-02-08/flu-relie...
>Your interpretation of the quote is that middle managers don't provide value, but I think that may be too broad. I understood it as "highly formalized process often rewards middle managers", which I do think is true.

I agree, but I don't think that's a bad thing - I think something that rewards management, rewards the team as a whole. If the PO/PM overcommits, it's the team as a whole who suffers. Likewise, if targets are smashed, the team gets recognition.

As such my interpretation wasn't that middle management is bad, but that formalised development processes are bad, which is what I fundamentally disagree with.

Businesses as they grow end up having abstractions on abstractions. Formalising development processes allows for the business to actually be aware of what it's doing, how effectively it's being done, and where opportunities lay for improvements.

Don't get me wrong - too much management creates warrantless red tape and frustrations, however standardising the development process through things like Jira (which the author was complaining about) doesn't fall into that bucket (in my opinion), especially when the author compares that the same can be done with a blank sheet of paper - if senior management want a rough understanding of the roadmap for the next 12 months, why would you "forecast" with some guessing on paper, over actual proven data of this is roughly how this team performs, this is the rough estimates on these initiatives, ergo, we can commit to these X projects.
Which only sells red things
Can you share your stack? The answer really depends: static blog/website, put it on github pages and you're good. AWS, build everything with autoscaling groups, set min=max=what is needed, but still you can easily scale up/down when needed. Etc.
I'd love to get into this kind of work (currently in webdev, but I'm a good debugger). My contact details are in my profile - can we chat?
Committee members started talking about criteria such as age and fields of study, even before suggesting nominees. Most thought that focusing on specific branches of mathematics was inadvisable. They entertained a range of potential age considerations, from an upper limit of 30 to a general principle that nominees should have made their mark in mathematics some time since the previous ICM in 1936. Bohr cryptically suggested that a cut-off of 42 “would be a rather natural limit of age”.

By the time the first set of nominees was in, Bohr’s cut-off seemed a lot less arbitrary. It became clear that the leading threat to Bohr’s designs for Schwartz was another French mathematician, André Weil, who turned 43 in May 1949. Everyone, Bohr and Morse included, agreed that Weil was the more accomplished mathematician. But Bohr used the question of age to try to ensure that he didn’t win.

Why let the committee argue whether the nuclear reactor needs to be built, when you can get them to argue about the color of the bikeshed. Stuff like that makes you wonder about the true significance of academic accolades.
I can see where you're coming from, and your point of view is certainly not baseless, but I just thought I'd point out that at least Google has pushed for the development and adoption of linked data formats like JSON-LD [0] and standardized vocabularies like schema.org [1]. They make use of it for "knowledge graph" [2] features, as well as in Gmail for what they call "actions and highlights" [3] (things like displaying flight reservation details, for instance).

[0] https://json-ld.org/

[1] https://schema.org/

[2] https://developers.google.com/knowledge-graph/

[3] https://developers.google.com/gmail/markup/getting-started
None of those do interactive collaboration like debugging very well. You could copy the result of the collaboration into something like that, but actually getting people to do that is not trivial. If the collaboration happens on slack, you get at least some searchability.
I agree. Progamming languages give us so many ways to organize domains without increasing deployment complexity and rewrites like microservices do. I wonder why microservice components talk as if those approaches don't exist or aren't equally valid. There used to be this term called "refactoring" which has gone out of fashion.
Why does it matter if anything else does it too? Even if everything slack does is possible with irc, fact is slack is much easier to deploy at scale, much easier to get nontechnical people on, much easier to integrate with things like pagerduty or datadog.
"You will not see that in medical profession." - I work in public health, and this is manifestly not true.

Hell, there's even jokes about it, mostly involving Web MD and/or Holiday Inn Express.
It's the React ecosystem. People didn't come up with the term javascript fatigue for nothing.
Optimizely’s decision to ditch its free plan
Shirt, watch, haircut, jewelry, manicured nails, cleaner pressed pants, designer bag:glasses:whatever, favorite restaurants, shoes, phone, vacation stories, fraternity/sorority mentions, accent, colloquialisms, alma matter, hobbies, connections, and other off hand comments. The formerly poor are very attuned to it. We don't always know, but sometimes it's obvious.
> Half the time I let the compiler write the code by using ghc placeholders and playing type golf

Is this method documented anywhere? Sounds interesting.
I'm black and I agree with his comment. Is it more valid now? I've experienced racism living in progressive California. It happens.
Doubling the authoring workload is important, though: it ensures that everyone walks away from a long conversation with the same summary. Even if you're present in a conversation, you can think that someone agreed with something you said when they actually scrolled past it or forgot.

Traditional meetings have secretaries and a procedure for approving minutes for this very reason.
I don't think Pokepocalypse is wrong.

If two Senators time their investments right, they could easily make money by shorting the market before manufacturing a budget crisis. Just use a third rail issue that riles up your voters as an excuse ("This plan funds abortions/provides tax cuts to fracking operations") and you have a reasonable cover for your oddly timed transactions.

Disclaimer: I don't think this caused the current spate of shutdowns.
Um... it is hard. Really hard. Let us just hope you don't have WiFi turned on, and can revert your changes first!

In our case, we have a tombstone delete method. So as long as every peer that saved your data (and people aren't gonna just save it for free) comes online at some point, after you've nulled/tombstoned the data, then it will be deleted.

This is only true because of our CRDT system that lets you update/mutate data. It is not true or a general property of other decentralized systems though.
The Code Theoretic Axiom the Third Ontology – Klee Irwin (2017)
As with all carriers that offer US (and Canadian) numbers, they are required by law to let you port your number away. So you can always bring your number elsewhere if they decide to close up shop.

And if that happens, likely someone will setup another instance and keep the same service running. That's another great advantage of JMP over Google Voice: all the code is free and open source, so anyone is free to run their own instance if they like. In fact, you could run your own instance right from the start and then be in complete control of whether JMP keeps working for you.
What was your web browser?

What were the features of your, and/or others' web browsers, that distinguished them from TBL's work?

Mind: there were several other alternatives out there, with Viola being amongst the more interesting -- it aimed at becoming a suite of web-related tools and capabilities, based on what I've seen.

http://www.viola.org/
It's a high-quality product. My current employer uses Bitbucket for compliance reasons (I wrote the compliance tooling for my previous employer to use Slack) and while it works great, it's just worse in several small papercutty ways.

Having a pleasant product causes people to be more likely to use it during the initial migration phase, which increases network effects, which is important for a successful communication system.
4. unsafe.

the biggest reason I know of for people not wanting to take public transit is safety. In the SF Bay Area, MUNI has not always had the best track record for safety and recently BART has had some unfortunate incidents of groups of criminals getting on a train car at one station, robbing everyone in the car, and getting off (and away..) at the next station.
And then there's always the stereotypical intoxicated/homeless/mentally unstable individual that poses a safety threat. Sadly something I personally witnessed on BART more than once.
I don't mean to come off pessimistic either, I think we are doing better about it. My poor experiences have been distasteful, but not definitive of all my experiences. There will always be bad apples and such...
I am not sure why people are still not able to figure out what this is, maybe everyone stopped at the home page and never followed the github links from Tim's github.

There is still ugliness all over the place but it looks interesting. 504 errors, bad certs, servers not function properly (or offline). I think as a professor at Oxford and backed by Mastercard, maybe this should have been delayed until things worked right, the documentation is also pretty slack.

https://github.com/timbl/pad
https://github.com/linkeddata/solid-ui

-- edit --
Trying to install dependencies to get this working I hit so many snags I gave up, this just isn't compatible with up-to-date (Linux/Ubuntu) systems.
This is silly and infantilizing. You can walk down any street in any of the many non-depressed area of the US and see a parade of bad financial decisions driving by in the form of newish $30k+ cars, along with a number of $50k+ pickup trucks, doubtless financed with debt. No one here is talking about people who can't afford food, he's talking about a much larger percentage of the population that makes an objectively large amount of money and still doesn't save nearly any of it.

People in the US are, on average, not nearly as frugal as they should be, and the sorry state of savings in this country is at least partly due to those habits. Even people with 6 figure take home salaries frequently are only a few months of savings away from financial ruin or tapping their retirement savings, if they lose their job. For them, it's a planning and discipline problem, not a problem of some evil system keeping them down.
I've been closing this very closely for a few months. I think he thought he could arbitrage and benefit from the increase in BTC's price and get away with it somehow. The market came crashing down, XRB got listed on Binance and Kucoin and a lot of shadiness happened right around the same time.

I was expecting this "hack" to be announced and founder to exit-scam just based on his behaviour and actions he was taking.

I wouldn't be surprised at all if he ended up in jail.
While it's true that Google and the like benefit from closed or partially closed data ecosystems and formats, as I've pointed out in another comment elsewhere in this thread [0], they've at least been pushing for the development and adoption of linked data formats like JSON-LD and vocabularies like schema.org, and they're using both of those pretty extensively in products like search and Gmail.

It's a far cry from things like Solid's vision of a fully decentralized web of linked data, but at least it's something.

[0] https://news.ycombinator.com/item?id=16356193
Given that we just left a period of very low rates, paying off a low interest mortgage might not make the best financial sense if you can put the money to work elsewhere.

There is also a diversification problem. Paying off a mortgage could tie up a large part of someone's wealth in their house.

Related to the point right above, paying off a mortgage ties up a large portion of cash in a fairly non-liquid investment.
There's tons of evidence. You can google as easily as I can.

The hard part is not the evidence, it's dealing with the social result. Do we as a culture decide "Yes, it might be true, but it's too harmful, so we will act as if it's false?"

Give extra tutoring to those lower on the scale, and withhold it from those higher, to try to even the balance?

Give special advantage to those lower? Is there a way to do that without disadvantaging others? What sort of advantage?

Something else?

Each of those options has pros and cons.

It should be discussed, but like I said, it's politically difficult, so people try not to talk about it.
You are partially right. Some RNA viruses are hard to vaccinate against because of their mutation rate, but it's not the sole arbiter of whether or not it's doable.

There are other issues, like the existence (and lack thereof) of highly conserved antigenic targets.
Even if an antibody was eliminated, and managed to bind to an antigen, what good is it if it doesn’t have a complementary immune system to act on it
> move your internal “how do I do X” chatter from Slack to email lists and maybe a StackExchange installation, and you end up with multiple indexable, searchable sources of long-form documentation.

Really, those stores of "long term" documentation complement chat rather than replace it (whether it's Slack, IRC, or whatever). Over time, you should be developing that documentation, so when you have repeated "how do I do X" type of questions in chat, you can often direct people straight to the docs.

But documentation is never foolproof. It's inevitably incomplete, it goes out of date, etc. And for the information that the docs don't cover, you want a real time asynchronous discussion that's not as heavy-weight as a meeting or as slow as email, which is a good fit for chat.
That actually sounds pretty conclusive to me.
There is not a decreasing trend in the efficacy of the flu vaccine over time.
tl;dr: we're having too much internet, we should start limiting it out of our lives back where it was in 1993, as a mail and info lookup tool.

Wanting toothpaste back into the tube may feel natural, but is quite unlikely to happen.

Nothing interesting here, move along.
> where the back-and-forth is much slower.

This is a feature. Slower back and forth means people put more thought into it and communicate better.
Do you have a suggestion to make our UX work better for you?
Agree, this just looks like a subset of JIRA with a snappier UI. Atlassian would do well to pay attention.
Too many people would use the term "refactor" when they really mean "rewrite".

As far as microservices, one benefit is that it makes blurring the lines between domains much harder. A mediocre developer can easily go into a well designed code base and make a mess of it quickly. In a microservice setup, their mess is mostly contained to one domain at a time.
Upload the serialized model to S3/GS, configure the URL to be re-pulled--treat model versions like feature flags
Why Ubuntu Snap will win – Part 1
No problem, I’m glad to help. I also strongly agree that the book was superior in every important respect.
[shameless plug]

This is exactly why we at FastMail made Topicbox! Email is your personal memory, and it made sense to extend that to organizational memory by making mailing lists not suck.

And we switched from IRC to Slack for our internal comms a while back, so we know the pros and cons :) Chat's great for real time, but not for long-term memory.

https://www.topicbox.com/

[/shameless plug]