skysight-inc/HackerNews huggingface dataset:
Unlimited vacation is a scam, where people end up taking less vacation either through fear, or pressure from peers and management. MANDATORY vacation is what should be the policy. You MUST take all of your vacation, no buy backs, no coming to work. The corporate world will amazingly survive without your presence, I promise.
Do you have a source on that that you can cite? Thanks in advance!
I've heard that Intel used to do this. They would have separate teams working on next gen chips. Eventually they'd have a bake off and pick a winner and the rest would get written off as R&D. I'm guessing they at least pick up some learnings from the dead projects.
Anatomy of a Butterfly (Keyboard)–Teardown Style
> those same single family home owners would become rich if they could subdivide their properties for intensive development. I have never understood this paradox.

There isn't unlimited demand. Just a few large apartment buildings could soak up most of the demand and then prices would go down across the board.

So essentially, you want to ban your neighbors from being able to sell for upzoning but not you. But your neighbors won't let you do that either, so everyone agrees to ban everything.
From TFA I could see that work-life balance is now considered good by 74% of employees, 24% up from the 5-day week. Still pretty far from 100%.

The article does not seem to mention the resulting performance of the company as a whole. I think that should be as front and center as the work-life balance satisfaction figure.

> Employees designed a number of innovations and initiatives to work in a more productive and efficient manner, from automating manual processes to reducing or eliminating non-work-related internet usage,” said Delaney.

Employees eliminating non-work Internet usage on their own accord sound a bit implausible, adding to the general feeling of not listing all the salient points that the article invokes in me.
iFixit Tests Silicone Membrane on 2018 MacBook Pro Keyboard with Dust Exposure
They already do this-it's called Google Opinion Rewards and it's how I feed my Clash Royale habit.
Google is a consumer software company. Consumers aren't willing to pay for software.
After looking at the first few examples I skimmed the summary header, ALL of the (examples of) phase 3 failures include lack of efficacy (some also lack of safety) as the main failure.

Since medial trails are very expensive and time consuming, I can't help but wonder if identifying this would have been possible from prior phases, possibly with better study design of at least the phase 2 version of the study.
Nope, I like competition, and until I see some I'll stick with iOS. They're way better on privacy than others.
In properly-set-up Kubernetes, no aspect of TLS is defeated. Instead, trusted CA certs (usually self-generated) are made freely available to everyone and then those are used to validate everything. If anyone is using self-signed certs and disabling TLS validation, then their implementation is probably insecure.
- You’re absolutely right, not all the 100M bug reports are actually bugs. However, we highlighted this under the "Time to Close" section: "These are most likely not programmatic bugs, but could be support issues or spam." How do you think we should highlight this more to avoid confusion?

- About bug resolution time, Instabug is used by many companies as their main bug reporting tool or they forward these bugs to another bug tracker like Jira and we have a two-way sync so whenever it gets resolved over there, it’s resolved at Instabug as well. That’s why we used the word "resolved" not "fixed" because each company has their own definition. I hope this makes sense.

- About the quality and reliability of the data: Oh, we didn’t mean to be protective about this! On the contrary, we’d love to get your feedback. What would you like to know?

- About your third point, I respectfully disagree. As the person who spent the most hours working on this report, I can tell you honestly that it was not for PR. We just wanted to put something out there that would hopefully be valuable to the people in our community. We initially shared this with our own users for them to have benchmarks. This is the first time we’ve released anything like it, so it was an experiment for us to be honest and I’m loving all these comments because it helps us know what to do better next time around.
Interesting, do you have any resources? What people?

Aside from the video I posted from Brian Goetz most of what I've read is just comments about how much people like reification in C# and how annoying those edge cases in Java are (i.e. stories from practitioners not language designers.)

I'd love to read more.
You can't have an informed risk assessment without clinical trials because you don't have the data to inform assumptions about risk / benefit. The models currently used to predict risk / benefit are really poor predictors of whether something is safe and effective. If you don't do phase 3 RCTs you'll just end up w a bunch of people gaming the risk assessments and getting drugs that don't work approved

Statistics and study powering are designed to address the issue you cite about marginal benefits "smoothing out" as the population gets bigger. That's why you have to do big phase 3 studies with __predefined__ endpoints and statistical analysis plans powered by estimated effect sizes

Saying that phase 3 study "clearly worked" is not true. It didn't do better than sham. Yes it could be true that there is some drug related benefit in the nontreated eye, but another interpretation is the sham injection itself could cause the observed improvement. Or the study design was wonky, endpoints inconsistently measured, etc
Why even keep the unsynchronized RNG? I'm guessing it was more performant when used appropriately?
Really? I eould certainly do this if it contributed to the company continuing with a 4 day week!
Those casts are still there. The compiler puts them in and the JVM has to execute them.
username is appropriate
In this case OP is talking about the GraphQL schemas, not the DB.
That first mistake isn't in the article anymore, but the second is.
It doesn't suprise me - at least in the UK (and I get the impression it's basically the same outside of SV), companies don't seriously compete on benefits other than pay at all.
So quietly, it's almost nefarious
You have to check the angles. Think of the X I posted earlier. Imagine your goal is to stand at the point looking "up" (because that's were they will meet), both moons were traveling bottom to top, and you were on the moon that started bottom left. (So your gaze is at an angle to direction of travel.)

For most of the time the moon will be behind you to your right out of sight. After the interaction, if the other moon was larger than yours, you might be able to see it.

But if it was smaller, then your own moon's horizon would block your view of it.

But it's worse than that - even if you could see it, you would have to turn your head to the left to see it, but it's moving so fast you just don't have enough time to physically move your head before it's far far away.

i.e. It would whiz by across your field of view, not toward it. Which makes it really hard to see.

Edit: I'm tying to visualize how it would look, but I may have missed some detail. It would be cool if someone could program a visualization of this.
The important thing, as far as I understand it, is the way the future moon slowly transitions from being primarily under the gravitational influence of the Sun to primarily under the orbital influence of Jupiter.

We've actually used ballistic transport to transition probes from orbit around the Earth to basically in orbit around the Moon with just a tiny braking burn at the far side instead of the serious burn that a Holman Transfer orbit would require. And the Moon is in a stable orbit around the Earth and doesn't have any further satellites.
Right, it was pretty shocking for me when I drove through Bakersfield on the way to SF. Nice folks, but lots of Trump supporters
Limited error handling mechanism in Apollo and our backend GraphQL library means I can't use then/catch to reliably handle both network and server errors. Apollo also hijacks state management and somehow decides when to fetch over the network or render a cached response, with no particular logic I can deduce or find documentation for. Then there's the thousand lines of repetitive query code that is a joy to read/write/manage.
That's really where the productivity gains of the next 20 years will be: free employees from the tyranny of workplace attendance, so that they will not resent these gaps and actually concentrate on end-product.
Thanks for the info, that's quite a lot less. I'm American but living in the EU where I was told by an Apple repair outfit over here that the topcase replacement would be something like 400-450 euro (so, roughly $500). I also noticed price differences of about $300 on the laptops themselves, if bought new and locally.

What I'll probably do is wait til the rest of the fall lineup is announced, including the rumored "MBA replacement", to see what the prices are before buying one. Then I'll just use my current MB as backup.
If we still look at the messaging example, I honestly think this theory (if that really is what Google is doing) is backfiring spectacularly - the fragmented messaging standards mean that most Android users communicate using SMS, which is a laughably bad protocol in 2018. iMessage - boring old non-developed by a "startup" style-team iMessage - is so much better that I've often contemplated switching to iOS for that reason only.

The funny part is that they might be actually emulating an entire marketplace entirely within one company, but it often seems like it's a marketplace where a large entrenched lowest common denominator is the option that everyone uses and dislikes.
In ops, we often have other internal groups that we either work with or support. It's often useful to view these groups as a customer, then you use the same policies, perhaps with a few exceptions in some cases, to manage the relationship. Typically we call this the OLA, the operating level agreement. I can only speak for my own experience, but operations groups I've been part of that don't have this concept of the operating level agreement typically suffer various types of damage to reputation. This is because there are no rules around how internal groups assess accountability, and therefore by having the terms of the OLA, you have the ability to defend your position as long as you stayed within the terms of the OLA. For example when we started building VAData data centers all over the world for Amazon, by having an OLA, we were able to push back on groups that claimed we were not holding up our end of the agreement.
Based on my subjective observations, homelessness definitely seems to have gotten worse in the South Bay Area in the past few years. If you go biking or walking along the various creek trails and railroad tracks you'll see more encampments. Some of them are fairly well hidden but if you stop and look you'll see the signs.

By the way, this is one of the reasons why it's tough to get people out of their cars and commuting by bike. Many people don't feel safe cycling through those areas.
I agree that Fermi isn't a paradox but if the chance of an advanced civilization on a given star is independent from the chance of one on another, then the components of Drake's equation exist and to have the chance be small, the components must be small, for suitable definition of small.

The article and blog's meta-argument involves choosing components over a random distribution of universes and saying "well, there's a good chance you wind-up in a universe with small". But reasoning about random universes is debatable, introducing unnecessary metaphysics but even so, if you wind-up in a universe with a small chance of an advanced civilization, you will wind-up in a universe with Drake's components also small. Which is to say the whole reasoning does nothing but "muddy the waters".

The only way the "randomly chosen universe" argument matters is if we're jumping from universe to universe or if there's a force that inherently keeps us from reasoning about the why of the Drake components - but neither of those conditions are met.
In the UK, employers are required by law to consider requests of flexible time arrangements like yours. They can refuse it, of course, but they have to do it in a reasonable manner and can be held accountable to a tribunal.
Everyone who owns a house near san fransisco has the price of their property, and thus their money, reduced by more houses being built near san fransisco. They get more money by reducing the supply of houses, thus all the house owners, usually more rich and people who already live in an area, are against more houses being built.
Right, then you basically lose caching, since the everything's-a-POST requests would go to the wire every time. Not that I haven't considered making that trade-off.
It is a problem because it creates NIMBY behavior. It is not feasible to fix it because it would require rewriting the US tax code.
Cryptocurrencies solve a problem that people don't really have -- namely that trust is in short supply. So even if some cryptocurrency was popular we would wind up right back we are because of the same market forces that brought us here the first time. Cash that you can send over the internet was never something people really needed or wanted.

* People won't want to actually manage their wallet and risk losing all their money and FDIC carries real tangible value so individuals won't have wallets, they'll have an account with a bank. And because nobody -- not you, not your bank wants to pay transaction fees all intra-bank transactions will be done off-chain.

* And there's never been a problem with intra-bank trust so transactions between banks will also naturally be off-chain with some trusted intermediary so all banks would have is an account with that intermediary.

* But how do people with bank accounts actually do day to day transactions? Banks could have a system where users have a local wallet that the bank xfers down and then performs a real crypto transaction with the other party and then back up to their bank -- but 3 rounds of fees just to buy a coffee? Some trendy start-up will emerge to do all these transactions off-chain for pennies.

* And then you run into the same problem with credit cards where you essentially need virtual accounts with unspecified amounts in them and if you actually try to do transactions like this on-chain you spend a lot of money in fees just to move money between the wallets of trusted parties.

So we'll wind up heading toward a cryptoless society for all the same reasons we're headed toward a cashless one now.
Python is certainly way better for a layman trying to do small things than C++
Well, for good or for bad, python does the same.
>Their stores are actually rented out retail space for Apple, Samsung, and other brands.

This is what the article is all about. They are leveraging their one advantage they have over Amazon.

Do you not realize that BestBuy does not actually make electronics?
Yes. And my point is they'd be there anyway, with or without generics. It's not "generics" making the JVM any slower.
I think this tourist map[1] brilliantly depicts what parts most tourists actually stick to, by shrinking the western parts of the city on the map.

There are very few tourists in the vast majority of the Richmond and Sunset, except near the water and Golden Gate Park (around the museums). Also, there are very few tourists south of Bernal Heights Park.

[1] http://baycityguide.com/media/San-Francisco-Map.pdf
Then why didn’t those people set the value higher? If you sell for some price, then you agree that you do want to leave for that price. The “market” would be efficient — people would sell for exactly what they would be willing to sell for. “Sentimental” value could be expressed in actual, taxable value. You could quantify exactly what a house is worth to you — and can insure the home appropriately.
Does this simply reduce social mobility ?

If you are already with a strong employer (e.g. banks, google, utilities, monopolies, university) then yay for u.

But if u r in a 2nd tier employer - then u lose the opportunity to out-compete them and advance ?
> slowly transitions

There is no slowly for capturing an incoming object - you get one chance, unless that object is in a similar orbit to your (and in that case the Sun doesn't help).

> with just a tiny braking burn

Tiny is relative here. It's still enough of a burn to significantly change the momentum of the rocket. Moons don't have anything with that kind of energy, except other moons.
JavaScript fundamentals before learning React
It’s not surprising that the cashier in Malmö didn’t have any suggestions: surströmming is from the other end of the country, and all the southerners I’ve spoken to about it have got that “those crazy norrlännings” expression on their faces.
BTW, alcoholic drinks are requred to be radioactive by US law.

https://youtu.be/1N1ydPJGGj4
Time, energy, and infrastructure.

People experiencing low income in the US aren't generally just low on money. They're also low on time, energy, and often infrastructure. It's hard to buy staples in bulk and cook healthy meals with them when you don't have the time required or a place where you can reliably and safely store the staples.

And, at this point, a lot of it is cultural. Not all people value healthy food.
My wealth is already being used to fight insurgents in parts of the world we have zero business being in.
And one source for this steel is courtesy to Admiral von Reuter who managed to scuttle his fleet, guarded by the Brits and interned in the Orkney archipelago, in June 1919. Better to sink that serve the enemy, right?

https://en.wikipedia.org/wiki/Scuttling_of_the_German_fleet_...
Then, of course, there's this: https://www.joelonsoftware.com/2000/04/06/things-you-should-...
You as an English speaker. What about the remainder of the world?

Must everything be left-to-right? What if the nouns and verbs were not English words? What if the natural order of possessives or adjectives is reversed in a romance language? What if the words are not even cognates, and the characters to express terms are not even letters, but opaque pictographs?

The paths chosen are an abstraction, and REST is designed such that it should be easy to bind any one resource to perhaps multiple URLs. But honestly, to the vast majority of the world, these URLs never see the light of day, and every consumer of a REST URL is probably going to do so programmatically, perhaps once, while reading the docs and setting up tests, and then they'll call it a day, and never look back, because honestly, consuming data from API endpoints isn't actually anyone's idea of "fun" despite wild claims to the contrary.

For the sake of getting shit done, I usually avoid this conversation in practice, but honestly, also because arguing is worthless. People have their opinions as a matter of convenience to their own efforts, and not as considerations to others.

These are the tastes of a given developer creeping in as a leaky abstraction of human readability.
Take a look at kscript, which is a single-file wrapper around Kotlin that includes dependency specification in the script file: https://github.com/holgerbrandl/kscript

Example:

#!/usr/bin/env kscript
// Declare dependencies
@file:DependsOn(“com.offbytwo:docopt:0.6.0.20150202“)
import org.docopt.Docopt
val usage = “...”
val doArgs = Docopt(usage).parse(args.toList())

println("Hello from Kotlin!")
println("Parsed script arguments are: \n" + doArgs)
Sure, but that doesn't mean we need to introduce more classes of problems we have to check against. Designing algorithms to handle all cases efficiently is often better than trying to filter everything that triggers cases the lazy algorithms can't handle
Awareness is good, but I object to the notion that it is "largely avoidable", and that all we're lacking is some awareness training.
So set a high price. Problem solved. You wouldn’t be forced to sell for any less than the value you, yourself have assigned. Nobody gets exploited: people get exactly what they want.
Show HN: Design and share collections for your favorite cryptocollectibles
All major OS have gone kernel changes over time. Windows,MacOS,now Android. Simple. Of course, lots of other factors as well like Oracle lawsuit.

Taken from reddit:
I don't think it will be "starting over," just a major platform change. Imagine Fuchsia being Android 13.0. Every OS maker does a major platform rewrite along these lines eventually.

Windows moved from DOS to the NT kernel.

Apple moved from the classic Mac OS nanokernel (is this the right name?) to the Unix-like XNU kernel with OS X.

Google could trade Linux for Fuchsia's kernel.

These projects are always codenamed something else at first. They always come with big compatibility problems that are overcome with time or emulation layers. Sometimes there are major UI changes, sometimes the UI is built to closely replicate the old OS, but everyone does a huge "reboot" transition like this eventually.
I agree. Three days is too little (the "weekend" is too long), but four days is just right. I've worked four days for years, now I'm temporarily working five, and I am looking forward to going back. Two days aren't long enough to unwind from the other five, I keep feeling that the week is too long and the weekend too short.

Working four day weeks, every week I'd think "damn, is it the Thursday already?" and on Sunday I'd be looking forward to going to work on Monday
> I took a look at Scala but instead of virtualenv style dependency management it's more like maven projects.

You could do virtualenv style by setting the CLASSPATH environment variable if you really want. The ecosystem tends to prefer using explicit dependencies though.

> It has Ammonite where you can declare dependencies at the top of files but that seems kind of hacky.

Sort of, but I don't think you'll do better anywhere else. Lots of other replies are suggesting various languages that do essentially the same thing - a magic comment at the top of the file that declares your dependencies.
Yeah, but I like bean soup with a lot of beans in it which has +vegetables+bacon. I did tried to make myself full from beans but mostly, but it does not really work and lasts shorter then normal meal with meat.

As in, it is ok lunch, but I am hunger in shorter time then with meat or say mac&cheese. Importantly, when I try to eat only that for 2-3 days, it does not work at all.
Patient choice is an idea that sounds good in theory but just has no good way of actually working in practice.

Most people are going to be uninformed about medical science. (Hell, most medical practitioners struggle to stay informed). Worse, there is a strong bias towards misinformation--look at the health supplement market, which is basically a market the seedy snake oil sellers set up to get around FDA regulation.

On top of this, keep in mind that it is very easy to accidentally design bad experiment methodology. With respect to clinical trials, it's all too easy to take a failed trial and say "it actually worked on this subgroup" because there are often enough subgroups to find one with a spurious correlation. And when you have monetary pressure to salvage a failed product, the p-hacking is less likely to be internally questioned. The current regulatory regime requires that you declare how you're going to define acceptance before you run the trial to prevent this kind of p-hacking, and if you truly believe that you're not p-hacking, you're welcome to submit another trial to show correlation on that subgroup (unsurprisingly, many of these end up coming negative).
Zuckerberg Secretly Called Trump After the Election