skysight-inc/HackerNews huggingface dataset:
I can imagine a few ways this may be legally executed. One is to use the 1800s anti-trust laws to forcibly break up Facebook. Create the smaller entities I described in the process and say “this is the standard for a social media company.” Another would be to endow or reinforce citizens private data as some form of personal property. Give them the legal means to sue and demand payment for any storage of their PI. Make the costs of offenses steep. I am definitely not a lawyer though and not as up to date as I should be for this sort of spit balling.

Edit-I think they could also tie a temporal component and per instance cost of storing someone’s “PI”. That value could then be a basis to tax the corporation- create an incentive to “forget”.

Edit2-make a persons likeness and social media posts part of this “PI.” This would give Pelosi the legal right to the doctored content.
This is pretty typical elsewhere too (midwest US as a data point).

Its popular because managers can implement it. Agile- the manifesto version- was intended as a way to re-introduce the notion of discipline that newer generations of programmers had lost (where previously they were engineers and scientists who wrote code, now people who code exclusively eithout other backgrounds).

It feels like we have come full circle to where the new generations of programmers have delegated (or lost) all discipline to managers' Scrum plannings.

Managers and "product owners" aren't engineers or programmers. They shouldn't be expected to "manage" a developer's day-to-day, and yet them presiding over sit-down-stand-up meetings and demanding points and determining deadlines and features is precisely what it has come to. We are right back where we were when the manifesto was drafted.
Micro-WWVB (2016)
My (related) experience has led me to believe reporting to management should be strictly separate from any tools or processes used to track actual work, specifically to avoid dumb shit like this. Team task-tracking should be a team communication tool. If you want to report task-related stuff upstream it should be totally separate, with updates/sync done by a human (project manager would make sense).

I also think speculative future make-believe planning junk should be kept out of the real getting-shit-done tool. Put it in there when it actually matters. There should be no "on ice" or "phase 3" (when in "phase 1") crap in the tool the devs use. It may or may not make sense to have them involved in planning stuff that early, but keep the output of that planning away from the real-work trackers until it's closer to time to do it.

I think that's part of why Jira (and similar, heavy, report-focused tools) is so god-awful. It not only tries to have features for teams to get stuff done and for five other roles to dig around in tasks and reports for whatever reason, it enables and encourages that, and I'm fairly sure, at this point, that it's fundamentally a bad idea.
> And sad as it is, veganism will actually increase fossil fuel usage as the vegetation that people eat need petrochemical fertilizers

I'm trying to wrap my head around this argument (and I'm not a vegan). If we're not vegan, we're eating animal protein, and those animals making that protein are...vegan. We're ultimately all getting our protein from plants.
A New Illusion
I wouldn't say that. Why are Epycs worse than Skylake xeons?
What if a fiction is someone try to tell the truth that will happen in the future, but in a acceptable and literature way?
Books Warren Buffett thinks everyone should read
OK that's pretty cool
The Free State Project seems to have had a very large impact in New Hampshire for the tiny number of declared people who moved to the state under its auspices. Is there any reason another Bay Area (or near) city or local government couldn’t be the YIMBY alternative to SF? YIMBY in SF is probably doomed to fail but a small number of highly committed people might be able to set up a second start up hub relatively nearby. It doesn’t really seem plausible but the FSP looked pretty nuts too.
Understood but we're talking about different things I think (though this is very much not my area).

You're saying volatile is acting as a kind of memory barrier instruction for the compiler - got it. But I'm saying I understand that at the CPU level, just considering x86 instructions, writes don't have to be forced to RAM, despite a common assumption that they are; they can remain in caches. See johntb86's reply confirming this.
I see the article is from 2010. Is that before or after Objective-C 2.0?
I'm dubious because of the frequency range of audio recordings (especially post compression on Youtube) and the size of cells, even large ones like hair follicles.
I still don't really know what a business analyst role truly entails. In my office they seem more like mini project managers w/o the management. They talk to internal stakeholders a bunch, handle a lot of our UAT, and I guess do some reports stuff? One has moderate tech skills (but no programming) and the other is just really good at Excel.

I'm still not sure what their actual formal responsibilities are.
Could Andrew Yang Be the Dark Horse of 2020?
> I am getting increasingly annoyed by the fact that buying anything is becoming a minefield

Not only that, but they keep repopulating the minefield with new mines after you've spent considerable time clearing them. (Google, I really don't want you to use wifi to "improve" location precision and silently re-enabling the setting after a system update isn't going to change my mind.)

One way or another, this has to stop.
Ethics, the researchers exposing these exploits and proper implementation of the x86 ISA.
Really? I lived in Paris for a month and saw the "dératisation", and the rats. A park was so infested they had to close it temporarily.
I don't think we should lump all rodents together. Squirrels, for instance, can reasonably be kept out of our houses and buildings, especially out of the living areas. Even if one finds a way into an attic or crawlspace that you forgot to squirrel proof, it is going to be going out to forage, and so hawks, cats, dogs, and cars keep the population down.

Urban squirrels for the most part live beside us, where as rats and mice live with us, and so the later are much more likely to need to be managed.
I take really long showers, drive aimlessly at night, and go on long walks.
What's now making the problem even worse is that construction costs are extremely high partially because of housing costs. The construction workers either have to afford a place to live or commute in from the valley. Either way they have to get paid for this. I've heard of people paying north of $70/hr for day labor in the city to dig a ditch with shovels.
`du`, `ls -r` and `find` are all tools which recursively walk and stat directory trees. In that light, it can make sense to pick just one.
Mensa, the High IQ Society
Trump-Style Politics Infects a Local Race
Typically you lock in specific revisions of your dependencies until the next time you run your dependency management tool, at which point it is free to bring in nonbreaking changes.

You don't want stuff changing of its own accord without a corresponding commit in your own repo. Especially not on a per-installation basis. Sometimes people get SemVer wrong. Or you may be bit by the bug that caused a patch release on one machine, and want to reproduce the issue on another.

But the downside of pinning versions is that you don't get the patch release in dependency A until you go to update/install unrelated dependency B. For a mature project, that could be never, or only by giant leaps every few months or years. Tools like this keep your version locks consistently up to date.
Nobody is attributing it to bots? I believe the media has. But you are blaming it on "foreign entities" so is that any better?

Also, the institutions are the ones causing polarization and distrust. And the problems you listed - mass migration, aging population, climate change, etc were caused by the establishment and the institutions they control.

What caused mass migration? The establishment and their institutions encouraging it perhaps?

What caused the aging population? The attacks on femininity by encouraging women not to have children? The attacks on masculinity by encouraging men to stay immature and childish? The media portraying raising a family as burdensome and undesirable had something to do with it no? The media encouraging women to forego child rearing so that they can be career women and consume, consume, consume.

What caused climate change? Oh that's right, the establishemtn and their institutions encouraging globalization and consumption, consumption, consumption.

Believing these institutions are going to solve these issues is as silly as believing an arsonist is going to help put out the fire.

I guess it's easier to scapeout "foreign entities" rather than dealing with the real problem.
> It's interesting to me that democide is the number 1 cause of death in the 20th century and everyone ignores that fact.

Can you please provide a reputable source for this claim? I find this difficult to believe.
> I'm still curious what datasource they're using to match those three bits of information together...

A phone book?
I think this gets at a very common problem with managers in the hierarchy. They forget that iteration of processes is crucial to good agile process. Your goal isn't to adhere to "true scrum." Your goal is to tailor scrum to what your team needs.

If your daily stand-ups are just repeating the JIRA board, then just give people back their time. If your features are coming out badly designed, then stick a designer in the engineering pods, or call out the design phase in project lifecycle.

If your projects are consistently late, then... slow down the estimates!

Of course teams that do it right tend to know this, but the bad implementations of scrum I've seen consistently lack attentive iteration on the process itself.
and yet, reasonable people who know what they're doing buy bonds with negative interest rates.

the financial world is more complicated than you realize.
And they let you subscribe to other services through their payment processing. And if you have a FireTV device, you can search for content across all those providers
Copyright is automatic in almost all of the world except america, and even in america most forms of copyright do not require registration.
Managers are often looking for ways to fill their calendar. Meetings, calls that could be a two-minute Slack exchange, et c. Some will hop into meetings like that if they can. They love the recurring ones, especially, bonus if they can apologize any time they have to skip it for something that actually, maybe, matters ("uh, yeah, we don't care if you come, OK, thanks for apologizing I guess?")
slightly off topic but IIRC the only time Adam Smith mentioned 'an invisible hand' in his Wealth of Nations book was to explain why English companies _wouldn't_ do this. Nothing to do with a market reaching equilibrium etc.

It was very much a cultural assumption that doing something like that 'just wasn't cricket' and no true Englishman would offshore their company!...

wiki: The only use of "invisible hand" found in The Wealth of Nations is in Book IV, Chapter II, "Of Restraints upon the Importation from foreign Countries of such Goods as can be produced at Home."
One set of figures that I saw suggested that iOS 12.1 had a small lead over Android 8.1 in March 2019. (These were the most common versions at the time.) Consider all of the versions of iOS 12 and Android Oreo, then Android had a major lead. That is before considering Nought and Pie, which I suspect is the range of releases that most developers would target.
One of my previous job was for one of the big music streaming services.

So very much a mass market product :)

As stated above, what we did was that when we decided to "drop support" for an API level, what it meant was that we would freeze an apk that would be delivered to these older devices and have a higher min api level for the new app versions.

The burden might higher on the backend people not to break the old endpoints than for us.. these old apks need to continue working. Technically we were supporting these frozen legacy
apks, but since we have chosen particularly stable app releases for this, in practice we never touched them.

Weird corner cases/devices were indeed a bit more of a concern. And to be explicit, that was never a significant amount of our time. I was part of the more senior team that had to (among many other things) deal with that, and I don't think it has been more than 5% of my time (and 5% of the time of 2 other colleagues, whereas the 20 others not in our team did not have to deal with it at all).

As far as I can tell it is the result of :

- at this scale, if something can break, it will break. when you have millions of daily users, all of your app issues will be uncovered (and to be honest, there was a ton of these... we inherited some very awful code in some crucial areas)

- mass market means that you will see all kind of devices connecting to your service, including weird no names chinese devices that have not been certified by google. So they did not have to pass the compatibility test suite that devices shipping with the play store have to satisfy. This has been getting better and better year after year but at first you could see some "exotic" behaviors.

- mass market also means that people will try everything in order to use your product for free. Although to be honest 99% are refreshingly naive. Like somebody distributing a "cracked" apk letting you get one month of premium for free. We decompiled that version and could not figure out what had changed .... until we tried it and.. oh man, so that "hack" is just that we we offering a one month free trial at that time .. Nothing nefarious here, just the same free month you would have gotten for a new account by downloading the official apk from the play store.
You're right that my math is off, it loses 0.06s every minute, so a second every 16 minutes, still not 'real time'.
The author Alex Danco’s link that supposedly proves that building housing doesn’t improve affordability is a poor review article by Michael Storper and Andres Rodríguez-Pose that is rather thoroughly debunked by their own colleagues Michael Manville, Michael Lens, and Paavo Monkkonen here: https://twitter.com/mc_lens/status/1129502980498022401 In summary, Storper badly misrepresents or misunderstands the economic literature, and attacks strawman arguments, to try to avoid admitting that supply improves affordability.

The author also says, “The third factor that somehow gets left out of a lot of armchair debates about housing and yet is an essential (possibly THE essential) element in all of this is credit.” As Kevin Erdmann explains in Shut Out (https://www.amazon.com/Shut-Out-Shortage-Recession-Universit...), the opposite is true. Credit is the factor that people jump to to the exclusion of rent (and expected rent given the low rate of homebuilding), which is directly related to supply constraints. Housing prices are high in the Bay Area because rents are high; low interest rates did not detach prices from rents.

Yes, there are a lot of factors in the housing market if you want to get deep in the weeds. But in my opinion, attempts to elevate second and third order factors to avoid dealing with the first-order factors of supply and demand are sophomoric.
Do I trust this brokerage to exist in 10 years? 20? Are they going to be convicted of fraud? If I have a problem, is there a phone number that I can call to speak to a knowledgeable agent that can solve my problem?

A sampling of things that differentiate brokerages for me, price per trade is so far down my list since I buy rarely but hold for a long time.
You'd be lucky to cover 1% of the United States, much less 1% of the world. The real world impact of everyone in the US putting this on their roof would be minimal, and you're unlikely to actually get a significant percentage to switch anytime soon.

If you're looking for solutions to global warming, look elsewhere. However, that won't stop the marketing team from selling it as such. Evaluate this technology on its merits and take the IR radiation reflection as a bonus.
Is the Silicon Valley representative of software development though ?
Because on the other hand we have professors telling us that the average (surviving?) software lifetime is 20 years...
I have decades of industry experience and I mostly agree.

> find what works for your team

For the combination of team and project. Different software projects need to take very different tradeoffs in how they managed. Use scrum in aerospace for flight control, and people will die. Use scrum for system software, and you'll have hard time delivering quality and performance, system software often requires non-trivial amount of engineering. Implement NASA's best practices when working on videogame or web app, and you'll blow budget.

This article is from 2002 but still good: https://www.joelonsoftware.com/2002/05/06/five-worlds/
You can use a lock but held in a regular CPU register. They're just regular variables for the most part.

Lock free in Java is usually worse that what the JVM can pull off with lock elison
The first part of your solution conflicts with the second. You cannot both require new hardware for an OS version and require OS updates for old hardware.
For primitives Java uses special CPU instructions. In the Atomic* package. It's not recommended for plain objects.
I don't see how the act of taking and publishing measurements after microcode and OS updates constitutes hysteria. It's my understanding, at least on Windows, you pretty much have to opt-out of these patches or manually install an update that disables the mitigations.

I fully support a users right to bypass these mitigations, and you're correct that your typical desktop user, at least today, isn't a target. But it seems odd that websites dedicated to performance computing have a blindspot to how automatically installed updates will impact performance.
Scrum existed before the agile manifesto. It's probability more accurate to say Agile is a mix of those things.
As someone who has been using depenabot for my rust projects for about 6 months now, I appreciate having it attempt to upgrade past breaking changes. Not all breaking changes break everyone. When they do break, I appreciate knowing a new version is available for me to upgrade to so I don't fall behind. Probably the riskiest case is behavior-breaking (rather than API) and your tests don't happen to cover that case but dependabot helps by gathering changelist info that I first review.

This is on top of the benefits of upgrading pinned-but-compatible versions which someone else covered.
>a single reasonable subscription

That subscription might be reasonable for a middle class person in the US, but way too expensive for the average person in a poorer country. Ads put everyone on the same footing.

And if you want to do research on a topic across many different websites, it'll happen that they won't all be in the same community, so you'll have to pay subscription fees to many different communities, sometimes just for a single page view.
An interesting variation: if you have the first n primes, partition them in two groups and take the product of all primes in each group. Then take the difference of the two products. This number will not be divisible by any of the primes, and if it is less than the square of the nth prime (and greater than 1) it will be prime. Searching for the partition that produces the lowest difference of products produces the next prime for a short while:

2x5 - 3 = 7

3x7 - 2x5 = 11

11x5 - 2x3x7 = 13

This fails to produce the next prime very soon, but it's slightly interesting.
Do people really want to own their data? I'm very skeptical about this.
Wait, if the brokerage goes broke do your stocks go away with it? I thought your stocks belong to you? What could (legally) happen to the stocks?
Agreed, it feeds the existing power structures. And it did hit at the right time when over-communication is not only appreciated but everything else is seen as intransparent and potentially suspicious.
"You don't even know what your team is doing?" - is the best way for middle-management to pick on each other. So in order to never get into that situation daily standups, slack, jira, basecamp all these "transparency tools" are welcome as they offer defense for this manager.

Does anyone know if there is an anti-movement to that over-communication trend? Something along the lines: "The only way to go fast is to go well",
* Plan
* Honor the flow
* Adjust
In practice this is a non issue, even for larger apps with a big user base. This is just trolling.
Anything you replace it with will, over time, suffer the same problems. If it becomes popular then it will have vulnerabilities. As technology and its uses change, it will need updating to match and so become versioned and have legacy features and complications in implementation. That is just what happens to all formats. Many people just use PDF as a simple way and showing documents and printing them out on standard office printers.
The real problem is that most consumers just don't care about privacy at all.

Losing the 0.01% of people who care about their privacy is no incentive for manufacturers to change their shady practices.

It would be nice to have some kind of privacy certification, then consumers could have an easy way of knowing the product they're buying respects their privacy.

It's a sad state of affairs that this would be needed to buy a set of headphones.
That reads like one of the instruction mnemonics from https://twitter.com/x86instructions
There have been a lot of software development methodology but one thing that's been overlooked a lot is the competence of the people doing the execution of the project. I am talking not just about the developers / engineers who are building the product but everyone across the pipeline - product owners, business stakeholders, process specialists, business analysts, project managers and just about everyone else.

People attribute failure to the process because it is demeaning to put the blame on people when established best practices can receive the finger pointing.

Stop the notion of being nice to the lack of skills of people. Hiding behind being nice does not resolve the issue but rather propagates it. Fix the issue by providing the grounds for people to learn and become productive.
Show HN: Configurable command line pastebin client in rust
This is just not accurate. The types of changes thrown in after early requirements gathering are most often coming from product managers and executives, not from customers and not driven by genuine feedback or budget constraints, etc.

“Sticking to the plan” does not mean rigidly enforcing zero changes, but rather means keeping a commitment to the general scope and direction that was mapped out. Compromises should require extraordinary hard evidence before being accepted.

This is really why Agile as a general set of guidelines is so easy to subvert and ends up being a misused tool in most every situation where Agile is deployed (Scrum of otherwise).

Project management guidelines need to start out by specifying a way that quality is strictly disallowed from being subverted by competing interests that lobby for changing the plan.

If a set of software project management guidelines doesn’t start out with an unchallengeable quality-above-all-else mandate that creates policy barriers to the natural entropy of different interests trying to lobby for why their preferred change has to be made, then it’s doomed to just get politically subverted.

Doesn’t matter if it’s Agile, Waterfall, extreme programming, whatever.

“Sticking to the plan” in the sense of setting up preemptive, high-cost barriers to anti-quality modifications to what was agreed is _the_ thing.