skysight-inc/HackerNews huggingface dataset:
You forgot trains. Suspension bridges can't handle trains well.

What about buckling though? With all that force from the cables pulling the bridge deck toward the towers, it seems like a bit of unexpected bending or weakness (breeze, earthquake, minor damage) could cause the deck to travel inward to the tower while being crushed.

I do have to agree that I am tired of cable-stay bridges. They are a distant third for looks, behind suspension and obviously the stone arch. More stone arches please! Do a big one, a mile or two in height.
Freedom doesn't necessarily have anything to do with dealing unless you redefine it with extremist libertarian ideology.

The freedom to make fair and reasonable contracts among parties that all fully understand the terms and do not have a massively imbalanced power dynamic is certainly one I, and many others support and think is fundamental.

The ability to force people into unfair contracts with you under duress by abusing your economic power is not and has never been "freedom" in any sense of the word (rather, it's the opposite of freedom, slavery or indentured servitude) unless you have some kind of sick Ayn Rand redefinition of it where it is nothing more than a code word for the notion that the people who happen to currently have wealth should not be questioned, stopped, or denied anything they wish no matter the consequences.
I built justalgorithms.com with node.js
> but the actual protocol is not very robust. It's pretty easy to jam or overwhelm the system without trying if the software running the transmitter shits a brick.

Yeah that definitely is an issue -- there's no fancy multiple access provisions on 1090MHz.

Limited TX power needs to happen anyway for ADS-B to live on those battery-powered UAVs, along with along with implementing the protocol inside an ASIC that monitors/decodes its own RF output (and bricks itself if it's transmitting inappropriately) would likely be enough to avoid accidental disruption.

I wonder if there's going to be additional spectrum and RF standards for position reporting systems specifically meant for UAVs.
Different RAM, more soft errors the older a system gets. Heh, the system should auto over clock until it starts to get correctable soft errors and then back off. Or reduce refresh until soft errors and then bump it up. Max speed at the lowest power.
https://magic.io/blog/uvloop-blazing-fast-python-networking/... from the makers of uvloop (for a toy example)

it seems the main bottleneck when using aiohttp is aiohttp itself, which practically makes the use of uvloop irrelevant
"It was the shortest civil defence in the history of law. No experts. No witnesses. He simply stood up and proclaimed 'Pot, kettle, black, the defense rests.' ""
So you are asking for cloudron?
Here's Keynes with another perspective:

> When the accumulation of wealth is no longer of high social importance, there will be great changes in the code of morals. We shall be able to rid ourselves of many of the pseudo-moral principles which have hag-ridden us for two hundred years, by which we have exalted some of the most distasteful of human qualities into the position of the highest virtues. We shall be able to afford to dare to assess the money-motive at its true value. The love of money as a possession — as distinguished from the love of money as a means to the enjoyments and realities of life — will be recognised for what it is, a somewhat disgusting morbidity, one of those semi-criminal, semi-pathological propensities which one hands over with a shudder to the specialists in mental disease.
Also, in a mugging, the mugged is deprived of whatever was stolen. With IP theft the victim still has use of their IP
A lot more easily when you realize what a Y-class economy fare costs (Boston to Hawaii next week? $2700+)...

Vouchers are typically only valid for full fare unrestricted economy fares or better, not V-class discount fares (display details when you browse your next flight).
Care to elaborate? I've never had any trouble going over country lines, let alone state lines, in a rental car.
No, it's really not about this one incident. United's customer service record has just fallen apart over the past several years, and many of us have had miserable experiences flying United. Every single one of my nightmare travel stories has been on United. Their CEO took as his mission to improve morale and build it back up, and ended up throwing gasoline on the smoldering fire instead.

So when we heard the news, we didn't just say "How could an airline do that?" Instead we said "An airline knocked out a passenger and dragged him off a plane so a stewardess could have his seat? Let me guess... was this on United?"

(Spirit would have an equally good guess, but at least they don't pretend to be on par with the other carriers.)
In a way it might be a good thing if you have worked in the same place for years and wanted to browse around the industry picking up new skills. You have built in reasons why you left each position so that shouldn't work against you when looking for a new job. Hopefully you had some payout each time that could earn you more than you would have during that period. Hopefully you had a chance to retool and reinvent yourself.
Not that this is particularly relevant, but this was written by my high-school ex-girlfriend and she turned the article into a book: https://www.amazon.com/Building-Better-Teacher-Teaching-Ever...

She now runs a non-profit educational news network called Chalkbeat: https://www.chalkbeat.com/

She's pretty smart regarding journalism and media stuff generally so if you're working on something related shoot me an email (in profile) and I'll try to make an intro if it seems interesting.
You might want to try a Pixel phone. I'm on my third generation of Google phones and this one has the best battery life of all.
My $0.02 is that people who submit such bug reports need to be fired. They're adding negative value to the company.

I get such bug reports for my open source project. People get offended when I point out that the message says what they need to do.
How to join your linux server to the NTP pool project
> What will it take to build this? 6 months x 3 smart devs who understand the linux kernel. So like $600k.

It seems like PaaSes are the new JavaScript frameworks[0]. Kubernetes now has most of the "critical pieces" mentioned and Helm addresses the "rigid" config criticism. It's not newbie proof yet but I doubt your 1.5 man-year project would get anywhere close to K8s is in terms of maturity and stability. Please do your homework and consider contributing to an existing project before re-inventing the wheel.

[0] https://github.com/search?q=paas
Suburbia started at Aldgate, which is just outside the city walls ;-)

A good rule of thumb is (or was): Does it have black cabs?
> then surprise everyone with their awesome services

...if they were at all able, as an organization, to provide awesome services, then they wouldn't be in the mess that they're in.
Many trade school disciplines.
Non-competes are a different issue. They are generally unenforceable in California, though exceptions may possibly be made for executives (I'm not sure, and IANAL anyway).

As far as the side-project policy goes, as you say, you have to avoid using company time or equipment. But that's the easy part. The tough one, as nostrademons mentions, is the requirement that the project not be related to the company's R&D ("actual or demonstrably anticipated" I think is the phrase). In the case of Google, almost nothing involving computers will get by that clause.
Has anyone ever tried a “make your own interview process” with job applicants?
I think it would be really interesting if companies would have a completely open ended interview process. Just have candidates come in for 1-3 hours and tell them to impress you. Let them show off projects, talk about interesting CS and programming concepts, live code, or whatever they want. Make them really sell you on why they should be hired. It couldn't be any worse than asking them to whiteboard contrived algorithms that have nothing to do with what they're really going to be doing.
Yeah, even when told it's a full flight, watch single passengers sit Aisle, Window, all the way down the plane, leaving groups behind them to be spread across middle seats over several rows.

Would be better just to file people in, next seat, next seat, with exceptions for groups to go to the next row. "First available seat or seat group that will seat your group".
Surprised to see no talk of Paper on this thread. Sure, Dropbox has visibly tried and failed to build other offerings - Carousel and Mailbox - but Paper seems like the most well-reasoned attempt so far, and something a lot of their customers probably need. It reminds me a lot of Quip which Salesforce thought was worth $750M.
GM Software Development Kit
> This one bad incident makes the news (the definition of news) and everyone thinks United is horrible and they will never fly them again.

The flaw in your argument: it's not just this one bad incident. United has been in the news repeatedly for poor customer service, and many many people have their own horror stories of dealing with them—just read around in this thread. This isn't "one bad incident", this is more like "the straw that broke the camel's back".
I've owned the book and it's just been sitting there for years. Recently I just gave in and got it on audible and I find it much more palatable.
He's talking about contract work, for which the quoted sum is reasonable.
This is probably a better link: https://fbnewsroomus.files.wordpress.com/2017/04/facebook-an...
Those points are polite.

If people get resentful when you ask for data, the solution is to have a discussion about their poor attitude.

Most large companies I've been at are terrible at this. They want "professionalism", which tends to mean "superficially polite, even if the questions are utterly retarded". They don't like "unprofessional" behavior, which tends to mean "you got frustrated that someone else wasn't doing his job".

The effect is that management pushed people to be incompetent, in the guise of "getting along". The competent technical people tend to leave such organizations.
Vanilla Recurrent Neural Networks
I can better that. In the early 90s I (12) and a schoolmate (17) were flying vancouver-toronto-london with BA. I as an unaccompanied minor, him no so. The toronto-london flight was delayed overnight due to mechanical issues. They probably wouldn't have helped my friend so much but when I mentioned there was an older student on the flight from the same school they tracked him down. We got two hotel rooms and, this sounds strange but true, a stewardess. She took us to visit the University of Toronto, to which my friend was applying, and then the CN tower before our flight the following night.
United Airlines reaches settlement with passenger who was dragged off plane
I think the algorithm would show which photo the "most" users would like is. What if you're someone who loves cats like no other and puts a cat on your shoulder (or wears a cat t-shirt or something). You're probably going to have a lot less "likes" than a "normal" picture of you, but the odds of you getting along might be much lower (I'm sure the average individual likes cat people less than the person who picked a person with cats in their picture).
I'm bound by my credit card rewards. As much as I don't like how United handled the issue, I'll still fly United.
> The odds of being involved in an incident are essentially 0

Involved in what kind of incident? United getting the police to throw me off the plane? Yeah, that's probably around 0 right now. But an incident involving poor customer service? That's definitely a lot higher than 0.
>First, legal problems: you can't have a unisex multi-stall bathroom in the USA. I'm not sure if it's actually illegal (it probably is in many states)

As far as I can tell, as long as the toilets themselves are separated, there's no issues (Youtube Space LA uses this format).
Granted, lifetime syntax has no analogue in the languages the comment I was replying to mentioned. That doesn't seem to be enough to qualify as "so different" though. But maybe it is?
That's only ambiguous if you didn't contact IARC. I can't speak to before IARC was a thing. But after IARC you had a way to get an unambiguous answer as to how Google would view your side project. Whether by form or email that is still pretty easy.
Actually, I would, if my needs were simple enough. Rarely is it necessary to have much more in embedded fields. Have a look at MDOS, a modern reimplementation of DOS used in many modern embedded cases.

Edit: which is apparently now called adelian.
Looks awesome. Code-signing your app is important for a first impression ;)
This exactly hits the problem with containers (and especially Docker and Kubernetes, but to a lesser extent CoreOS's model as well). The crows that seems to like/use it seem to be the people that aren't responsible for maintenance, security etc. and may not want to become the responsible party either. It's often developers that are either simply a lone wolf or part of a team that is big enough that release management falls on one or two people and 'the rest' just wants to churn out code in 'their way' and have that 'way' magically work in production too. Sadly, that is not how the world works.

You will always need some form of configuration management, release management, infrastructure and operations, no matter how compartmentalised and 'serverless' the software coders think they are. Right now, the idea seems to be that if you stick your code and practically a complete user land in a container, you don't have to do those things, as if old style deployments were the reason for those practises to be in place. Obviously, it is the other way around, and by trying to bypass them, you will run into the exact problems they are meant to prevent. (i.e. not knowing what is available/what is released, not knowing the configuration within the infrastructure in a global scale, not knowing the side-effects of two opposing configurations because you have no management for that, not knowing what versions are used because it is spread out over different/many unmanaged files inside containers somewhere, not knowing what is secure/patched, not knowing what else is influencing your environment, no control over parameters that should be globally overridden...)

We take a different approach: you get do write your software, and may only configure requirements within its context. Those have to be defined in a SaltStack Formula with sane defaults, that has to run in a local environment, but also DTAP-style chains of environments with no changes to the app. You don't get a say in what it will run on, but your required facilities will be available. If it doesn't pass automated testing (i.e. sticking it in a VM, running a highstate and expecting a working app) it doesn't get passed to DevOps and you're stuck until you fixed your stuff. With regards to scaling, we make sure that a few calls are always available to the app and/or it's formula, so that we can register where it is and connect it to the correct balancing pools (i.e. incoming requests, but also FS, DB, queue pools). When it's up, it registers, and as long as the automatic health checks pass it gets requests sent to it. If the load is too high, we scale up, if it's been idle too long it scales down. But the app/software/code isn't aware of that nor does it need to be, and using the reactor system, we don't need 'extra' management software to make that happen. You set your KPI's and health checks where you need them, just like you would on any other setup, and you're golden.
And then you might just end up using setcap on it anyhow, perhaps to load privileged ports, which is treated like suid, making it so that the linker won't look at LD_LIBRARY_PATH, in which case you have to create a conf file with your paths and feed it to ldconfig after using ldd on the program because you're confused about why it suddenly doesn't load its libraries.

And there's another fun security restriction in there where chown erases any setcap permissions you had applied, just in case you had to adjust something and didn't understand why you suddenly lost your setcap permissions.
A couple of years back, I installed Windows Vista on a Lenovo something (no idea what). Took me three days to find most of the drivers and get it all running, and about an hour to do the actual install. I ran it for a few weeks, then the software I was using had a Linux release, so I threw on Kubuntu (15.04 I think it was). Took me no effort to get drivers, as everything (bar the ancient Geforce 3D drivers) just worked out of the box. The system prompted me to install the 3D drivers, and I was done in under an hour.

Windows Licensing had a funny issue, though - I typed the number in, it rejected it, so I typed it in again, verified every character, it rejected it, typed it in a third time, it accepted it. Installed, booted up, and then it told me that I didn't have a genuine Vista (although the sticker on the system was genuine). I used it for a bit, intending to fix it later, and then one day it popped up telling me I needed to activate the system with a genuine number, which it did without asking for a new one, told me happy things and enjoy my Windows experience.

It's enough to drive you to drink...
It could be a lot worse.

Interviews are trying to answer the question, "Is this person someone I want to do this job?"

Is the job going to be writing out code on a whiteboard in front of people? No, so don't do that.

Is the job going to be free-form impressing people with programming? No, so don't do that either.

The best interview is having someone work for you on a contract basis for a few weeks or a month. It lets you assess the person's fit, and it also doesn't put them in a position of having to do work (like homework) for you for free.
I would love to hear more about this, including any specific examples if you can give them.
There must exists a module like `ijson` which could incrementally generate JSON.
I just booked a return flight for two and paid a $200 premium to avoid United.
> How is going for the cheapest ticket an "irrational spending habit"?

Because there are costs beyond merely the ticket price.
GCs are nondeterministic amongst other issues. Baking one into the core of a systems language likely isn't a good idea.
So if your machine/os/whatever does not run properly you might either fix it yourself or pay somebody else to fix it.

But really, no need to complain about the nice things that you got for free.
There are two sides to this coin. You can be good as in, you know fundamentals very well and can make connections with familiar concepts, or good as in, readily employable because your skill sets check the right boxes of keywords and names for a recruiter or HR person.

The former doesn't necessarily guarantee the latter. I'm gonna answer with the path less traveled in this thread with regards to your question. When you mention competitiveness, do you actually mean in terms of the job market? If so, unfortunately most people that are your first eyes to your resume when you hit that submit button are not as technically inclined as a programmer. Which is why it's often better to directly reach out to a team lead of the programmer department. Fundamental concepts don't work with 3rd party recruiters either, as most of them are not very language agnostic when it comes to matching you with job opportunities. The exception is with the largest of companies. They'll value fundamental skills more highly because they can absorb the risk of hiring someone to ramp them up with their work environment. Most medium to smaller companies can't afford much ramp up time. From my experience they want you to hit the ground running (seems to be a popular phrase with them) in whatever web framework they use.

So for your benefit, you will look more appealing to hire by applying to larger companies. Smaller companies tend to interview more in concrete framework trivia while the large ones tend to test you on algorithms and other language agnostic concepts.
Another point is your server can switch context to handle other requests with async.

In real world, your web page consists more than one db (like mysql + redis + some RPC calls to microservices) queries, with async apis, you can concurrently request for all queries at once and join them all at rendering.

The async benefits can add up to a much faster responsive server.
People like the idea of isolation that containers (LXC) provide. We don't have to worry about stepping on toes, my container works with any number of other containers running on the same host, not sometimes, all times.

The env is moving fast, Kubernetes and Helm are on a tear. It's also worth taking another look at cluster standup CoreOS+Vagrant/Tectonic/Minikube/kubeadm are filling in gaps.
What's your opinion on what the punishment should be?
A lot of people are blaming Levandwoski for deceiving Google as though he were some sort of evil mastermind. Given the lack of care he's taken to hide from these inevitable accusations, one must question the intelligence of his actions. Instead, I think there might be a more simple explanation.

Levandowski is clearly a brilliant character. Is it possible that he's not trying to maximize monetary gain but is instead optimizing for power over the technology? I sense that he's good with technical implementation but possibly terrible at technical leadership/the politics necessary for seeing one's vision through in a larger organization.

If viewed in this light, it seems that Levandowski has constantly been frustrated by the direction (or lack thereof) within the organizations he's been a part of. Rather than starting side companies and jumping ship for profit, he's really just trying to maintain control over whatever vision he has for lidar-enabled self-driving technology.

Now this strategy for power breaks down a bit, because he keeps selecting the local maxima in terms of opportunity. When Google comes calling, he accepts. When Uber comes calling, he accepts. Constantly convinced that the next place will give him the power/respect he thinks he deserves.

In the end, rather than building up IP from scratch and making a good name for himself, he's stolen a bunch of work from other engineers while potentially building a patent-infringing product. (thoughts x-posted from the other thread)
You're completely right.

I'm seeing a more general trend which I find equally worrying:
Software is eating the world, and the best tech is currently produced by the likes of Facebook, Google or Amazon.

I'm fine with this, but I'm seeing governments and other "serious" businesses like health, physics... seriously lagging behind.

I don't know what to do with this assumption, though...

Google will run the world? I'm saying it's too good to be true.
> First, legal problems: you can't have a unisex multi-stall bathroom in the USA. I'm not sure if it's actually illegal (it probably is in many states), but it'll never fly even if it is.

Granted it's not the same as an office bathroom, but I know of at least one mid-price but trendyish restaurant with a unisex multi stall bathroom here. And I'm in surprised-we-don't-have-a-trans-bathroom-bill-yet Missouri.
> It's just that this time you happen to disagree with the policy being given the Newspeak treatment.

This is about the third time in a week that someone has accused me along the lines of "you're only saying that because you disagree - you wouldn't say that if the politics were reversed."

First of all, you don't know jack about my beliefs, so stop projecting your BS psychoanalysis on me.

Secondly, I realize we may have gotten to the point that it's unfathomable that someone can actually be making a point because of the principle of it, and not just because it happens to align with their politics, but I still like to believe it's actually possible.