skysight-inc/HackerNews huggingface dataset:
Hi, thanks for this response! I think actually it's #2 that is the big one. See, I live in Istanbul province, in a European quarter rather up north by the Bosphorus, so nowhere near the city centre, but when I go to the centre of my quarter, I can easily do all of the things you list there in about half an hour, the time spent at each place included, only by walking from one place to another. And my quarter is part of a comune (tr: ilçe) with a population of slightly more than a hundred thousand people (the province itself counts upwards of 15 million people). I guess what is different between here and the usual US city/suburb is that there shops and stuff are more laid out, where here instead they're congregated in the central areas. So once you're there often you can get all the things done, and catch the bus back home.

Also, because urban trains and busses are frequent enough, we seldom need to think about the wait times. Except for the villages you can get hold of a bus in at the worst case about ten minutes everywhere. I do have to walk quite a bit to the bus stop, but that's because my part is like a little instance of a suburb between the Belgrad forests and the strait, thus scarcely populated and an exception to the general situation with the bus network. But after a 10 minute walk to the main street, it'll take less than 5 minutes to get a bus or minibüs (a private/cooperative alternative to the council's busses, pricier but more frequent) to the closest metro station. But I guess the general density of the population helps keep all this network in service, and get it to be built in the first place.
The proposal is to build public infrastructure and lease it to private firms, not to pay private firms with public money to build and own infrastructure.
It's not "disorders" but anything that affects math ability. This is plain regression to the mean. If half your cells would make you capable of being an IMO gold medalist, if the whole brain were made from them, but the other half would make relatively stupid so that you could only barely qualify for the USAMO (~top 300 in USA or so), guess what making a brain from the combination of the two will get you.
How to Snap Your Awesome (Haskell) App
People don't judge you openly or likely even consciously. But fitting in is fairly difficult.

Rubbing elbows with rich investors and CEOs from affluent backgrounds is definitely more difficult for someone from a lower class background.
He's missing the third foundation:
Have sufficiently good monitoring to support your frictionless deployments with an immune system that can automatically roll back deploys that seem questionable, and easily diagnose the cause of changes.
I wasn't implying that it was progressive.
> Apple's implementation of sandboxing actually makes computer users less secure. All the good software is distributed away from the App Store, because sandboxed apps are far too limited (especially regarding the filesystem).

Nonsense. The vast majority of users don't need software that does wacky stuff with the file system. They need software that opens documents they made, which all software in the app store can do. I'm a pro (the kind that currently owns the Mac Pro and will likely own the next one or the iMac Pro next), and I basically avoid all software that's not from the App Store. Your ranting sounds delusional to me.
There are 3 primary types of documentation that a growing organization needs :

1. Onboarding
2. Runbook / Troubleshooting
3. Notes and ongoing developer wisdom

Slack helps with #3, but is not what #1 and #2 require.

New hires should not be digging through slack to get up to speed, and ops or engs trying to deal with catastrophe in the wee hours should have playbooks, not try to dig up what worked last time in slack.
How Myanmar forces burned, looted and killed in a remote village
This should be exhibit number one why you should always favor open source libraries rather than writing your own plumbing functionality, especially around authentication and authorization. The onus should be on the developer to explain why the open source library isn't a fit, rather than defaulting to 'roll your own'.

The edge cases discussed don't pop up that often unless you have lots of folks using your software or are really diligent about fuzzing and testing edge cases. If you roll your own, say, username system, you probably aren't going to fall into either of those two cases. Which means you're vulnerable.
I'd bet few people will turn down an opportunity because of a couple hours spent working on a project. If they got this far in the interview process they should already know if it's a place where they wanna work. This is needless elitism. We hire tons of senior devs and small programming challenges are miles better then white-boarding.
Yep, and that was a disgrace for everyone involved, and screwed the consumer. There's two pretty big indicators that we're doing it wrong. First, with few exceptions, USA pays among the most for internet data, at middling speed. Secondly, those providers are consistently ranked among the least liked by customers. Why this doesn't scream monopoly/oligopoly needing intervention is beyond me. I personally believe these companies are so disliked that even the biggest pro capitalists would not even care if it were nationalized.
Ironic that you accuse me of whitesplaining.

Also, adding context is not invalidating.
Shameless plug, our startup makes a video-calling-in-Chrome application. Our goals are being super-reliable, simple, and free: https://daily.co
The Tripartite Identity Pattern (2008)
cmder is quite nice, reminds me of terminal.app
Quantum computing DOES NOT WORK by taking every path simultaneously. This is an incredibly misleading analogy.
I think basing the followup interview on the homework task is pretty standard.

You can always have someone else do the "homework" for you, but when you keep working on the same code base you have to show a real understanding of both the problem and your code, and it's quite close to a real work situation.

In hindsight I agree that telling people that will happen would level the playing field a bit.
Easy to say Slack, JIRA, Trello suck, but what are the alternatives? I used IRC at two 1000 person companies. It was useful, but didn't replace email like slack does now. Likely due to lack of persistence, absence on phones and hard to setup integrations.

Echoing a lot of the comments, you can blame tools for altering the culture. Phones disrupted memos, email ended vacuum tube delivery, computers killed the file cabinet. Slack is a reflection of our short attention spans. No one wants to read long emails. People need an easy way to message and get notified on all screens. People pass screen shots across their devices. It solves problems. I've seen people who abuse @mentions and @here, but ultimately you develop filters and need to take responsibility for one's own workflow.

I do hear how Slack isn't good at making organizational events searchable and good at archiving in corporate memory. Problem space is: need to search, recall, store and archive better. Maybe tools to record this into some record or doc, (i.e. readthedocs). You can argue Facebook/Yammer style status posts is a better way to broadcast and save announcements. Slack can innovate on UX, but they seeme focused on growth and quality of service. They're not looking to solve small issues at this time.
How exactly is that a problem? You can open an open file dialog that is in the user's home directory and you can even select ".bash_profile" for them. All they have to do is click "OK" to start editing it. This gives them the security that your app can't just go and erase or overwrite or add malicious stuff to their .bash_profile without their consent, which seems like a really good idea!
WhatsApp has launched person-to-person payments into beta in India
Death by redesign... https://www.alexkras.com/death-by-redesign/
Yeah I've heard about the hygiene problem in New York metro, and that was really surprising to be honest. I guess, for all three of your points, it takes government operation to run a nice public transit system because only that can afford to not profit or to lose money. Capitalism won't ever get you there in this particular area because there's no economical interest in running a nice public transit system.
Certainly. I think it's an interesting article as well. I am specifically interested in the feedback of the person who submitted it, however.
Continuous deployment means you are never in a state where you cannot deploy. Yes, this requires significant effort. API agility, schema agility, cache agility, ... Lots of things need to be solved!
(Imagine storing a serialized cached entity from a later version, abd getting a cache hit in the concurrently operating previous version, for example.)

It's similar to how continuous integration means your master is always stable (all builds work and all tests pass.)

If you can't do a 1% (or 10%) canaried deploy, you're not yet ready for continuous deployment.
I would propose doing essentially the exact opposite; commodify the entire spectrum using a high-frequency rolling regional auction system, so anyone and their dog can become a wireless carrier. This would be vastly more cost-effective for rural areas, and would offload the effort of organizing fiber leases onto random small (regional) businesses providing bandwidth.
Sorry I couldn't find the paper in github page. Can you give a link?
but then again, open source does not mean its good software, obviously. there should be some way quickly check if a library meets security best-practices. like a some sort of "vetted software" reference
This is a solvable problem but you have to solve it with markets not with standards committees.
shrug offering pay isn't meant as an insult, but to show we value your time. If we can't afford your hourly rates, we probably can't afford to offer you a salary you'd be happy with.
New Zealand is currently in the process of rolling out fibre connections in almost every urban area of the country (target is 87% of households) and the amazing thing is that a basic fibre connection is now the same price as an ADSL/VDSL connection.

The government put together a technical specification (e.g. minimum speeds, networking standards, API for service providers) and set a series of coverage targets; then they solicited bids from the private sector to build and operate the network in each region. Funding was in the form of an interest-free loan, and the network operators are required to offer wholesale access to any retail provider. The operators are also prohibited from offering their own retail services.

So in the end, once the loans are paid back, the net cost to the taxpayer is likely going to be less than NZ$1.5bn -- that's gigabit fibre to the home for every non-rural household at a cost of less than NZ$1,000 each!
Switched to what though?
> Uniqueness is harder than you think

Discord has a very interesting solution to this. They have user names and user ids. User IDs are tied to emails and the user's name seems to just be a random text identity for displaying to users. I assume most of their backend code used a unique, sequential or random, integer ID to identify and talk about users while their frontend just makes the ID to a "user name". As long as you slap account creation behind a verification email and don't mind one user being able to sign up for multiple accounts you side step many of the larger problems that come from choosing user names because, in effect, you are choosing the "Real" username and you can make any guarantees that make writing all of your other software easy.
Yeah, maybe Slack is bad in OP's workplace. But in mine, it's been great for increasing communication in an all-remote developer company. JIRA is used for task management, docs are stored in the same repo as the code, and Slack is used just to talk to people or solicit opinions. No one ever uses @here because none of us want to be bothered either.

I feel like most of the complaints on Slack are either because people use it as something other than logged IRC, or because it's getting misblamed for other company culture problems.
We are experimenting with Nix (https://nixos.org/nix/) to create reproducible "containers" of the tools used to build a model. Nix allows to pin versions of R, python, R/Python packages, etc. and all the underlying c++/fortran/etc. libraries all the way down to (but excluding) the kernel. Deployment (or sharing with other team members, Nix works on both Linux and MacOS) of such "derivations" is also very easy if Nix is installed everywhere since the dependencies are not visible by other derivations and I can deploy e.g. R models requiring different versions of dplyr package on the same node. It looks very promising, here (https://blog.wearewizards.io/why-docker-is-not-the-answer-to...) is a blog post which I found very helpful.
Depends on renters. You can be lucky and get some nice couple or young professionals who will take care of the property and when they leave the property will be in fine condition and will only need small repairs.

On the other hand, you could get some party animals that will trash the property and when they leave you will have to spend lot of money to repair the damage. They might also cause other problems like annoying neighbours etc.
Are there any open source alternatives to Optimizely? If not, would an experienced SWE comment on an estimated difficulty level to get an MVP together?
Even after reading several of the github linked specs and examples, I still struggle to understand what this intends to be, how it will work with e.g. CORS, or how anything will be able to flexibly work with other things playing in the same data-sandbox.

Like, we already have XML DTDs and schema.org and whatnot. Everything appears to be in place to build everything that I can see this doing, and has been for decades. But it hasn't turned into anything because the problem isn't how to store the data, it's how to use it, and allowing everyone to manipulate all data seems to repeatedly be demonstrated as a failure.

Is it really just "let websites manipulate my data, stored on my machines"? What would possibly incentivize websites to do so, rather than pull in data and subtly break it for others (intentionally or by accident)? Users are absolutely not going to understand why site X broke site Y, only that site Y is broken.

Or am I missing something fundamental? Entirely possible, I can't figure much out at all.
I'm going to wager that very few (if any) illegal marketplaces trusted a codebase they didn't write entirely in-house, but that is just conjecture.
Your picture fairly accurately describes Facebook.

It's not as accurate for Twitter, and is totally off mark (fortunately) for things like Mastodon or Dreamwidth.
Which also has potential for abuse and failure
I don't follow the initial premise.

>Well, it’s easy until we start thinking about case. If you’re registered as john_doe, what happens if I register as JOHN_DOE? It’s a different username, but could I cause people to think I’m you? Could I get people to accept friend requests or share sensitive information with me because they don’t realize case matters to a computer?

Just this month we fixed this issue by using a citext column in postgres. So yes, it is easy. Maybe I'm missing an edge case here?

https://www.postgresql.org/docs/9.1/static/citext.html
Minimal code delta means the isolation of any bugs is much easier than if you have to read through six months of patches.

Ability to get user or system feedback on code today, rather than in three months, is often quite helpful. That is, if your company depends on listening to customers or studying customer behavior. (I know of no company that isn't, though, except monopolies like Comcast.)
Matt Levine's article reads like a dinosaur whining that a meteor that has hit his environment, and now everything is changing. I must have missed the point.

It's strange, because Matt's articles are usually worth reading slowly and digesting.
So basically the wireless companies don't want to pay for all of the real estate they need for the new base stations they have to deploy and so they want to use eminent domain. The free market is great till you have to buy something I guess.
These "battle hardened" articles are fascinating. It is the output of years of experience and learning from real problems. It's building the best practices guides, and building the tools to scan for the edge cases. A great read!
There's a docs dir. https://github.com/graalvm/sulong/blob/master/docs/PUBLICATI...
Do you have any experience with openshift? It seems the OpenShift Origin functionality is very mature, but I do not have any experience. Have you ever made a comparison?
If we’re saying that the free market isn’t capable of delivering the infrastructure that underpins much of our modern economy, then where does that leave the idea of capitalism?
VLC changelog
Out of curiosity, is there a good reason for Netflix to do this? I.e., why would they be interested in providing 1080p to Safari but not Chrome, even if Chrome can do 1080p?
This isn't really about Slack, it's about the whole paradigm. Maybe it's even OPs fault that he phrases it this way, but anyhow, if it really would be about Slack it would imply that something like Facebook Workplace is any better, but in reality it's infinitely worse on about every possible aspect and beyond. Even by OPs own metrics.

So it's more about how "emails would be better", and surely not about "how to replace them". Not sure if I agree or disagree though.
Not that I'm happy with it, but I am not surprised by this claim.
That papers use of modeled faces makes me skeptical. The data proves their conclusion but they also made the facial models and didn’t use real faces experiencing emotions
You're both right. There are traders who beat the market in a way that's clearly statistically significant and doesn't involve selling tail risk or other cheats. However, they can stop being successful at any time.

To give a concrete example, GETCO circa 2009 was the premiere HFT firm trading 19% of US equities market volume and earned high 9 figures in trading profits on a tiny capital base. They were doing millions of little trades daily and made profits almost every day, if not every day. The odds of someone doing that due to chance are infinitesimally small.

They had been doing this since the early 2000s, quietly building an empire, and the people there were incredibly bright. They had their pick of the litter from every top school and one of the toughest interview processes. Retention was impressive, too, as the firm made many employees into millionaires in their early 20s and gave them plenty of autonomy. You'd look at this operation and expect it'd never end.

But it did, and quite quickly. Competitors eventually learned what they were doing and saturated the market. Their market share plummeted, as did profits, while the cost base grew. High speed data and microwave lines became a new cost of doing business. Layoffs happened. Once loyal employees defected and with them went even more of the firm's ideas.

Eventually they got a soft landing by buying out KCG, and the entire operation was later acquired by Virtu, but from what I understand, few of the original GETCO trades still exist or make any profits.

So I believe they won due to skill at the time, not luck, but more skillful competition came along to replace them. Some small group will always beat the market, but I'd need more evidence to believe one group would do it for a long time. Brain power and guarding IP are necessary but not sufficient.
> when interrupting people becomes the preferred mechanism over RTFM

Oh god, this is the bane of my existence. Slack, skype, even in-person. Some people will never read the docs. They will seek out people who "know" and disturb them. Earlier they would fire off an email. Now I'll get a message at 2am when I just want to get this last commit in and go to sleep.
> I also disliked was how they don't explain how to get it working without a build-environment like webpack

Your comment is a bit mystifying. Go to https://vuejs.org/. Click "Get Started". There is literally an example right there on the page, the first thing they show you is a frameworkless Vuejs app with nothing but a script tag.

if anything this is one of VueJS's advantages over most other similar frameworks.
I just scan the titles on Feedly, Open the titles I find interesting. Read the ones I really find interesting and bounce out of the ones where the titles were interesting by the item is actually boring.

But I can't catch up if I miss even one day. So there are periods where I have a 1000 unread items and I just skip them.
New York Fashion Week 2018 Interesting Facts
From my understanding Slack at large organizations (10+ employees) don't make organizations more productive at all. At the place that I work slack is relatively manageable for the most part. For me to make slack useful I just turned off all of the chatrooms and everything and make it so that I only check if it I get @ notified.

There are weird parts of slack by default that seem to be designed to make you less productive. Why does the #random channel exist at all? Sure it should cordon off off topic conversations and its designed by slack to increase engagement but is that what should be there by default?

For the most part though I see Slack as making me more productive. It is much easier to use than other alternatives. It has a great UI as long as you use the browser version (all of the native apps for linux are largely broken for me). If you are a large organization I think you would want to consider discord (yes I know its targeted for gamers) but it the react community uses it well in this regard.
Two take home "challenges" I've done in the recent past stand out for me:

1) I spent 6 hours on it. I didn't do some of the "optional" parts (unit tests specifically) because I felt like 6 hours was enough to "show I can program" i.e. what it was supposed to do worked. Result: I got grilled over why the optional parts weren't there and didn't get an offer.

2) I spent 15 hours on it. I did everything I could think of on it including 50ish unit tests and more than what was asked for. Result: I got and accepted the job. (note: I had laid out my salary requirements before hand).

Is this "great"? I have an active github/open source profile. To me in both cases they basically wanted to waste my time and mental effort, and see if I would do it. That.. can't be ideal.
If you are going to use New Zealand an example of what to do, then use Australia as an example of what NOT to do. Previous discussions about it https://news.ycombinator.com/item?id=14320121 https://www.nytimes.com/2017/05/11/world/australia/australia...
I would be very, very upset if I were forced to pay 750 USD for a fiber connection that didn't even benefit rural households.
Also, nobody can ever find again, even if they remember. And then they will create a whole new page for the same thing plus a small addition. Then 6 months later some poor soul will notice that you have 10 pages on how to do X and he will delete everything and consolidate them all into one page. Then the cycle begins again. Wikis are fucking useless.
Lagrange Multipliers Without Permanent Scarring [pdf]