skysight-inc/HackerNews huggingface dataset:
> you’re going to consider co-workers friends.

Why is that a bad thing? In a normal 9-5, you spend 1/3 of your waking time with those people.

I'm a few years out of University, and I've now spent more time with co workers than I did with most of the people I went to university or school with. I don't know what's going on in their lives for the most part, we catch up a few times a year and that's that.

You're probably interested in some of the same things outside of work as many of your colleague, and may have more in common with them than other friends You don't need to consider every co worker a friend, and it's definitely sensible to draw the line between working and personal life, but it seems like a total waste to spend a huge amount of your waking time with people and actively refuse to be friends with any of them.
Any university on the planet not pushing
Equal Outcome + Removing Merit + Removing Reward/Talent and Marxism from 2010-2020 ?
Does the world really need custom bottles though? At some points society should put its foot down and say that corporations should not be able to do anything they want without regard to the environment.

It's also a great example of a coordination problem: while I'm sure no company wants to stick its neck out to become the boring bottle company, they would benefit if all companies had to standardise on bottle shapes.
Off topic warning.

> A cup of coffee are starbucks is a luxury.

In Melbourne, Australia a coffee at Starbucks is considered:

1. A sign that you’re a tourist.

2. A sign that you’re a masochist.

3. A cry for help.

4. All of the above.

Sorry, I couldn’t help myself :)
The book (www).QUEEN2.tk by Kerrigan and Saber.ai's cover artwork looks like..?
I don't care about the ride; I care about me.

When they go past and they pierce my ears, that bugs me... a lot !
And the problem isn't really limited to links in the response; the same goes for computed links based on keys too.

In fact, links in responses are probably easier to update, because waiting for client software to upgrade can take a long time - but waiting for old versions to fall out of caches or at least dwindle to a small enough number is likely a much shorter wait.

Furthermore, when your clients are composing links based on keys, there's no good way for the server to tell a client that the uri has changed - the composition is in the client, and the key (presumably) hasn't changed, so the thing the server would want to update is out of conventional reach.

But with uri's there's at least a conventional solution - redirects. That's not going to be an ideal solution; but as a way of limiting transition pain it might have a place.

All in all, I think links are likely less painful to use than keys when it comes to uri routing changes. (But really, try to avoid changing uri's in the first place, because whatever you do it's likely going to be painful somewhere).
I meant to say "no ground support whatsoever". I've deplaned 737s and 320s on the tarmac recently too (at big airports), and they used mobile stairs. It's the stairs integrated into the aircraft itself that the 737 was designed around, and that's what's antiquated. Hell, just flying the stairs around with you is very fuel inefficient.
Speech itself is also covered by freedom of speech, does that mean you can shout into your neighbours property for hours a day? With amplification? From a recording?
“I’m not blaming the intern but it’s completely their fault”. Is her basic response, pretty shocking behaviour for a professional. Also, would t NatGeo demand the RAW files for any photo submitted? Or did they conveniently trust the photographers completely?
It's an API. The client isn't likely to be a browser. If it's integrating with another system, those links may have quite a long life.
I don’t think we should follow a 2 decade old thesis dogmatically, but I would point out that Roy Fielding has said:

“A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types“

In this case the only URL that is support long term is the entry point into the application. All other resources are discoverable from the index.
If your kid loves balloons so much why not fill them with air and tape them to the walls? That's what parents generally did when I was a kid.
"Because I need to treat my robot"
Model and manage the changing geopolitics of energy
Apps have been shared across PC-DOS, MS-DOS, DR-DOS, and several Windows variants, exactly the same was as Android for the last 30 years.
Much of the comments (and the article) criticize SQL as being non-standard and difficult to learn. These critiques have been around as long as SQL has.

However, there is a more insidious problem with SQL: it's all too easy to write SQL statements that have O(N^2) complexity. A simple JOIN can easily result in O(N^2) complexity, yet there aren't easy tools to identify these performance issues. As a result, as a database grows, things that once were executed quickly take forever.

I'd like to see the end of joins, replaced with something that is more explicit about what is happening under the hood.
No, the big things are varying ear canal sizes and shapes, varying earplug sizes and shapes, and side sleepers.

Put an earplug in your ear that seals the ear canal, then press firmly on the outside of your ear canal (on the side of your head, in front of the tragus). Feel that pressure. Now imagine doing that for 8 hours a night.

I have had to sleep with ear plugs because of noise from neighbors. Two results: waking up with painful ear canals during the night, and semi-permanently enlarged ear canals, requiring the use of larger ear plugs to seal, which causes more pain.

If you can comfortably sleep with ear plugs with no adverse effects, you are lucky.
Where you start to go wrong is where your talk starts to be of "YOUR" schema. The schema isn't yours, it's the company's. And guarding it is the DBA's job.

(I understand full well that that is a problem if the company has kicked out the DBA role and handed it over to the individual programmers, but perhaps that is precisely the problem.)
Data Science. Measures
> If you have to honor all previously-issued URL

You don't have to honor it forever; if you want to be good about planning for changes, you annotate each link with the latest date when it is guaranteed not to be expired, and the latest date an updated authoritative URL will be available (either as content in the resource representation or an HTTP redirect) if it expires on the earliest possible date. Consumers are then free to determine whether they need to update links or whether the data from which they come is stale (if your resources at any given link are immutable but for metadata about currency and links to updated versions if the content of the logical entity has changed, so that you can always recover the same version of an entity you fetched at the original URL so long as the URL hasn't expired, clients don't even need to check each references URL for updates, they can just check the base URLs of the entities they already have read that referenced them, and in the process update all referenced URLs; you kind of need that allow clients an approximately consistent view of data when they can't read it all simultaneously anyway, and if your API doesn't need that level of consistency, it then it certainly doesn't need link stability, either—you’ver already decided you are dealing with fundamentally ephemeral data,.so.if people don't follow links relatively quickly, they aren't getting meaningful data even if the links are permanently stable.)
Show HN: Random Reading Generator
After having taught myself Python, I've created a first - extremely trivial - "web app":
www.luckyread.app.
It recommends a random article to read every time you reload the page.

The articles are taken from a weekly newsletter I publish since 2015. Generally, I'm selecting the top 3 most clicked pieces from each issue (cleaned by those that are outdated) and store it in a text file which is read by the script.

Many of the articles are originally sourced from HN, so some here might appreciate the type of content.

I built this mostly as a personal project to practice, and a little bit to promote my newsletter.

However, obviously I could expand this. Any ideas what the next step could be?
>> the set of standards around HTTP are a horrible mess.

> That's not the problem at all.

sorry, what is the real problem then, in your opinion?

i have never heard of that link in headers RFC until now. i have never heard of CURIEs but i remember seeing the xhtml example they gave. no one called them curies.

there is a huge communication gap, it seems, between what the standard defines and what people do in practice.
I'd recommend giving a try to VictoriaMetrics. It requires less hardware resources - RAM, CPU, disk - comparing to InfluxDB [1] and it supports PromQL - much nicer query language for typical time series queries comparing to InfluxQL or Flux [2].
It may be used as a drop-in replacement instead of InfluxDB on the ingestion path [3].

[1] https://medium.com/@valyala/insert-benchmarks-with-inch-infl...

[2] https://medium.com/@valyala/promql-tutorial-for-beginners-9a...

[3] https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Sing...
She definitely seems European. And I can see that some of it is a becoming an adult story but a part of it isn't. A part of it really is about the corporate culture in Microsoft.

I've worked at startups and universities and I never had to deal with:

> The people I had on my team, were extremely closed minded. Most of them with many years of experience working in a corporation, so even more closed minded, only caring about their manager’s approval.

> I actually cared about my role, I cared about the people we were doing the Connect event for more than for my career and no one seemed to understand that.

> I found a job fairly easily with a similar salary, where they didn’t expect me to work 24/7.

I've worked long hours at a startup, but not like she is describing. The startup wasn't part of my identity, I didn't need to play politics. All I did was dev dev dev and some more dev. The communication overhead was low. Compared to her story, I had a dream job. Except that I didn't, it had good parts, and it had frustrating parts. Teaching at a coding school is more like a dream job since it doesn't feel like work and people pay you for it, except that it stifles career growth.
But seeing something go up when everything else in the world goes down is just in another league.

When I was a kid, helium balloons were much less common than today (at least in my country) and I remember seeing them as objects of desire.
> Car horn use seems to be extremely culture-dependent. I almost never hear it in Finland except when someone does something stupid in traffic.

Can confirm. It's quite rare to hear the horn here.

I haven't ever used the horn (having had a license for 10 years) except by accident.
I’m not suggesting we change the title, I’m suggesting the author could’ve done a little better.
Is this since 2013?
The whole point of the EU is not to depend on the country. The EU is most of a continent, I’m sure it has ample sand and sandstone for making glass. German manufacture of cement isn’t much different from elsewhere, why would manufacture of glass be absent taxes and regulation?
> Survival is definitely valuable, by simply allowing you to produce value longer.

...can you please take a step back, read this again, and think about what it is that you're saying?
> I hate that someone can change my schema, and that can turn my efficient index lookup into a horrible scan, without breaking tests.

They can't, if you do perf testing as part of your pre-release testing, which you should do.

If you aren't doing perf testing, you are saying perf isn't an acceptance criteria, so why are you upset that breaking perf doesn't break tests?
I think 'accessible' being the key word here.

I read the article, and as someone who does not have English as a first language and therefore know next to nothing on its literature, I am still amazed by its humanities focus on dissecting old texts and poems. Academic English in this respect looks very different to me than academic Dutch or French.

I mean, this is a thing that should never happen to a field "looking for truth": https://m.huffpost.com/us/entry/us_586d5517e4b0c3539e80c341

On the other hand, having universities educate for the needs of the economy is one of the stupider, short-sighted things happening now.
I still don't see how a frozen AoA sensor cannot be detected by the reduction in noise or correlation with other sensors (such as gyroscope or accelerometer).
> If you're billing by the hour, your client should have a general idea of how long something will take. A lower bound and an upper bound. Time-box all tasks.

In a world with perfect information, you'd be right. Unfortunately, people have to make decisions with incomplete and potentially misleading information all the time. Demanding perfect time-boxing ahead of time is a recipe for disaster.
It went from a poor fishermen's village to the poorest village for decades. It really destroyed the economy and lives of the place, there are no jobs there whatsoever and you are advised against going there without protection (which is unheard off in the rest of Portugal).
I know there are a lot of shitty people out there but one should also note that the workplace is one of the places where people tend to meet their partner. There is a lot of flirting going on in general and some of that by nature will be unwanted.

As an example early in my career I used to work with a woman that was also pretty new and we had some chemistry. Nothing really came out of it but we did spend some time together at work and outside work. But that started as professional attitude -> friendly -> flirty. She was the one that pushed flirty at first and for example after a while when I sent her a message that she forgot an attachment I could get a "Oops, sorry! You will have to spank me!" or something similar.

I'm not trying to defend that 45 year old married guy that drunk walks up to the new 20 something hire and tells her that she has a hot body but at the same time you will have people looking for a partner spending a lot of time together. And if you also add in office parties with alcohol you are bound to also have a few misunderstandings where Guy/Girl thinks that they are hitting it off with other Guy/Girl and wants to try to take to the next level while the other person only thought they were friendly co-workers and wants to stay that way.
You even don't have to "imagine" it anymore, it already exists. See the projects list at http://www.thethirdmanifesto.com .

The crux is : it takes much much more to achieve that than what the average C# or java coder yup has to offer. So the average C# or java coder yup will dismiss those things too.
I am not trying to be defeatist when I say that adults have a harder time acquiring new skills.

Maybe the factor is not that large as previously thought, but there is still a difficulty factor that increases as you get older.

EDIT: Well there goes my hope for HN supporting differing viewpoints. Pollyannaism is what one should support if one cares about karma.

I welcome multiple downvotes without explanation on where my hypothesis fails.

The OP (despite bias in promoting language learning schools as he is CEO of one) does not even disagree with me:

"Certainly on average the later learner seems to have a rarer time getting there, but is it impossible?

The data tells us that it’s not. On average less likely, certainly, but there are thousands of people who took this quiz, got a score in the range that a native speaker would, and started learning the language after the age of 20."

So it is possible but much harder/rarer.
Sorry. I get emotional about programming languages...
Is this the percentage of residents' wastes that are placed into recycle bins, or is this the percentage of waste that would've gone into a landfill that ends up actually processed for recycling? I thought part of the problem was that not everything residents send for recycling actually ends up being recycled. Your page sounds like it's in the former category but I understood the 8% figure was in the latter... though I can't say either page is clear on this...
I believe it's a chicken and egg problem. I know I would rely on video way more if my first sentence in every video call didn't have to be "can you hear me?"
Is it just me or all the images are broken?
You were lost some where in the thread above. I totally agree but that's not what we were discussing here.
No half decent programmer will randomly break backwards compatibility anyway so I'm not sure what your point is.

Consider your audience. Is it APIs like GitHub? Well guess what, you're stuck with maintaining backwards compat anyway, may as well have the relationships readable.

And if it's not and you control both ends then what does it matter because you can break links all you want.

It was touched on but less emphasized the relationships being expressed as links exposes further context than you otherwise get.

It's also nice to be able reason about shared domains. I.e. you might have the concept of a stock item and an order item. They are both represent the same thing in the real world and share a lot of information but depending on the value of self will tell you what kind of data you can expect to be a available and what domain you're in as well. Reading logs would be oh so much clearer.
If you use industrial feedstock of known characteristics quality control is much easier than if you use glass that might include window glass, coloured glass of a colour you don’t want, random chips of ceramic, etc.

Recycling of one time glass doesn’t work that well in Germany, look at wine bottles. What works well is reuse of bottles, both glass and plastic, and having big deposits on bottles, big enough that people are motivated to bring them back to the store to redeem the deposit.
But there is a chance you could skip some important judgement by doing blind auditions, for example if someone has sociopathic behaviors that will damage the orchestra team in the long run and that personality trait may have been clear in a face-to-face interview but not so much in a blind one.
This can be true, but orchestra is a performance act. If I look at it as a business, I don't see anything wrong in giving higher value to more attractive performers. On the other hand it's important how much higher value they get (and the multiple round audition when only one of the rounds is blind makes sense).
No, it's a value problem. When the resources tied up in recyclables are scarce enough from other sources, the value will go up.

When you're really hungry and there's not much food, your willingness to pay more for it increases. Same mechanism.

Ultimately we need to bake the cost of disposal into the purchase price.
Artificially Intelligent Drones' Potential for Abuse at the Border
This really is an old quote, and some people certainly do cling to it quite dogmatically, but my own experience suggests that slavishly following this principle makes life more difficult for both producers and consumers, and that there's little substitute for excellent API documentation, and clear, timely communication of changes.
That is very interesting. Art being compared to business. Should we censor talent to benefit the whole? This isn't a dev team with production deadlines... And yet, where do we draw the line? The artists know.
China’s New Carrier Shows Beijing Is Done Playing Defense
To me MCAS looks like an ugly software hack implemented to save money on redesigning a plane and re-training pilots. It brings several problems:

- it is difficult for pilots to understand how MCAS works, and how to diagnose failures. They are not programmers or engineers. And MCAS doesn't provide any debugging information about its work anyway. And pilots don't have time to analyze it.

- it adds new points of failure

- sometimes there are situations when automatic systems shut down and pilots have to control everything manually. With MCAS, they would have more things to look after. Pilots who got used to flying with autopilot are usually not comfortable with manual flight, and systems like MCAS only make things more complicated for them. An example is a recent crash of SSJ100 in Moscow where experienced pilots failed to land a plane manually after autopilot has turned off.

So I think that plane designers should be very careful with adding more automatic controls. Especially if their purpose is only to save money at cost of making place less safer.
A project manager's tips for working with web developers
Thinking it through, if they find other wallets with this problem, I wonder what the fix is?

They could generate a new key + wallet, which could probably then be made to work for the running instance.

All the backups though, would probably need to be opened with the current (missing) key+wallet in order to re-encrypt them.

Might be doable with the current key+wallet that's in memory, but also it might not be. eg might not be able to change the software on the running system, in which case ouch... places that need historical backups (eg for legal purposes) would be in bad place.
Standardizing containers (not just bottles) brings a number of improvements not just for recycling but for general logistics. It's one of those things that no one is large enough to implement on their own but once it's done everyone benefits.
There's literally not a single upside of this shown in the article.

> The server is now free to change the format of new URLs at any time without affecting clients (of course, the server must continue to honour all previously-issued URLs).

No more than it was previously.

> The URL passed out to the client by the server will have to include the primary key of the entity in a database plus some routing information, but because the client just echoes the URL back to the server and the client is never required to parse the URL, clients do not have to know the format of the URL.

Instead, you now have to require new kind of knowledge, one of the keys which must be present in schema and their meaning. E.g. knowing that "pets" key is present and leads to a relationship of a particular kind, with all the implicit logic added and documented. And what if you want to get pet's owners with some additional parameter, like only getting ones which are exclusively yours? Would you need to edit that "pets" url adding "&exclusively_owned=true"?
This argument is true for any data that was included in the response. If the client chooses to cache it, it needs to deal with it being stale.. which in this case could result in a 404. Obviously it would be a nice-to-have if the server had a redirect from the old to new.

> Even if you figured all of that out, links are not idiomatic if your users consume your api via an RPC or GraphQL.

Agreed, although you could model a link in the object-based structure representation to match the protocol, something like..

# RPC
{
"rel": "owner",
"procedure": "GetOwner",
"args": {
"id": 98765
}
}

# GraphQL
{
"rel": "owner",
"root": "owner",
"args": {
"id": 98765
}
}
If I remember correctly it was the other way around here: Basically everyone used the same bottle shapes and it worked fine, and then companies started going "hey, our branding people would really like a fancy bottle for this new product", and the setup of the entire return network wasn't done in a way that strongly-enough discouraged that. (Also a scale thing: a large brewery can afford the one-time expense of buying a big machine that can sort through tons of bottles by shape, smaller ones need to do it by hand or with simpler equipment)