skysight-inc/HackerNews huggingface dataset:
What a great comment.

> "Hate speech" has specific functional meanings when it comes to legal jurisdictions in which it applies. The idea that it's a tool for arbitrary suppression of disagreement is approximately correct as the idea that any other limitation on free speech (libel, slander, fire in a crowded theater, verbal assault, time place manner, etc) can be used arbitrarily

As I understand it (could be wrong), hate crime/speech regulations only actually act as punishment modifiers for existing crimes. They don't criminalize otherwise legal acts or speech (in the US, at least).

For example, it's illegal to vandalize a synagogue with spray paint. Hate crime/speech laws generally might mean that a person who spray paints an immature, lewd picture/message on a synagogue, is treated differently that a person who spray paints a swastika. The latter would be treated more harshly - which seems reasonable to me.
There are 2 normal ways to do things: work until you achieve the functionality you want and release it when that happens or work until an arbitrary date and release whatever you have at that point. Surprisingly, as a developer I always prefer the latter. As a coworker of mine if fond of saying, the time you know the most about the project is when you are finished. The time when you know the least is when you are starting.

By choosing to release "whatever we can do" at a certain time it encourages you to make difficult prioritisation decisions as the "deadline" approaches. Are we really OK with releasing with just this functionality? Maybe we should axe X and replace it with Y since we don't look like we are going to get both. Maybe Z is an even better compromise that we didn't realise was an option at the beginning of the project.

If you try to hit functionality, it allows the organisation to avoid rethinking its planning decisions. We aren't releasing until the ideas we had 6 months ago are all implemented exactly as we envisioned it back then. By the way, why is it taking so long?

Of course trying to hit both at the same time is just a recipe for disaster.
On the one hand, the author is taking the high road. Good for him. He has principles, and sticks by them.

On the other hand, you are completely and utterly correct. There are people in the publishing industry that should have never been allowed into their position. This editor sounds like a prime candidate for charges of moral cowardice and partisan opinions unbecoming a member of the “free press”.
Do you happen to know how it compares to curio?
Just a collection of Amazon affiliate links (tag=mostrecommendedbooks-20).
Meant to say “just cancelled my PIA subscription” :)
How to Know If You Are Ready to Start Your Own Business
A 160k-year-old jaw in a Tibetan cave might explain high altitude living
Introverts can be, and often are, very outgoing. They just find it exhausting and need time alone afterwards to recharge.

I have an evergreen recommendation that anyone who wants to understand want introvert, extravert, and ambivert really mean should read Quiet by Susan Cains.
Nitpicking: gas goes bad eventually and needs to be burned before that, the usually given timeframe is after ~6 months.
Sure you're more than welcome to do that.

And unions should be free to go to the negotiating table. But it should be just that. A negotiation. They should offer something of value in exchange for more compensation other than "give us X or we shut down the business".

That's a cartel. Imagine if businesses organized themselves into employers unions and refused to hire anyone above a certain wage?

Cartels are bad. They are anti-free market
C++ Pattern Matching Proposal [pdf]
> If X is not done by this date we will lose Y dollars. That Y number is almost made up to make things more urgent.

Sometimes it's real though.

Clients might have to make a vendor decision by the end of a quarter for example and want a bug to be fixed or a feature to be added before they sign.

In other cases, there might be a huge event and ad campaign where you have a limited timeframe to make a good first impression on a lot of potential customers.

Deadlines suck but in certain cases they're very necessary.
Thank you for the kind words !
Good question. An iteration is a marker to generate velocity.

All of the points collected in that week are summed together and the average of those points across a configurable threshold (typically 3 weeks) is the velocity. Once you have a velocity, you can start to make predictions about the future.

For example, if velocity is 10, that means 10 points worth of stories can fit into an iteration. If the PM moves another story into the iteration, the last story would be automatically pushed into the next iteration. Makes it easier to answer the question of 'when will a story be done?' as well as 'how will changing the flow of stories affect deliverables?'

Highly recommend you read the documentation, it has been formed over many years and is excellent.

https://www.pivotaltracker.com/help/articles/quick_start/
He was elected initially as a republican and was a republican for much longer than he was in the "National Union Party" - I think the result from google is clearly deceptive.
Free markets hate unchanging software. Software churn generates activity and revenue, and the basic goal of the game is to be the one controlling the change. Change is good when you have your hands on the knobs and levers, bad when someone else does. Organizations try to steer their users away from having dependencies on changes that they don't control. "You're still using some of XYZ Corp's tools along with ABC's suite? In the upcoming release, ABC we will help you drop that XYZ stuff ..."
>Anyway, even if prices were increased, what's wrong with a market in which all participants earned a living wage?

Because if prices increase, what you thought would be a "living wage" is no longer a living wage
Yes, this won't be 100%. But I'd say easily 99% of people could get all this tax bullshit automated away and they wouldn't have to pay Intuit a single penny.
Happy to consider other examples, but it does feel like the combination of China's capitalistic reforms while maintaining its authoritarian rule and the state control of information is fairly unique in the 20th century.

And any comparables likely failed due to war with democratic countries, and that seems unlikely given China's role in the globalization of trade as well as it being a nuclear power.
Sounds like a great way for the company to make people work hard (not smart), product mediocre results and not have to pay out bonuses. Have you considered either improving the process or finding a new job?
It's very hard for me to get away from C# because it's just so crazy productive. The tooling is fanstastic and the runtime performance is more than good enough.

One thing I found was that surprisingly the C# code I write outperforms the C++ code I used to write at equal development times.

I was good at C++, but the language has so many footguns and in general is so slow to develop in that I would stick to "simple" and straightforward solutions. I avoided multi-threading like the plague because it was just so hard to get right.

Meanwhile in C# it's just so easy to sprinkle a little bit of multithreading into almost any application (even command-line tools) that I do it "just because". Even if the single-threaded performance is not-so-great, the end result is often much better.

Similarly, it's easy to apply complex algorithms or switch between a few variants until something works well. In C++ or even Rust, the strict ownership semantics makes some algorithm changes require wholesale changes to the rest of the program, making this kind of experimentation a no-go.

The thing that blows my mind is the "modern" approach to programming that seems to be mostly young people pretending that Java or C# just don't exist.

Have you seen what JavaScript and Python people call "easy?"
I saw a page describing a REST API based on JSON where they basically had thousands of functions with no documentation, no schema, and no typed return values. It was all "Just look at what the website JS does and reverse engineer it! It's so easy!"

I was flabbergasted. In Visual Studio I can literally just paste a WSDL URL into a form and it'll auto-generate a 100K-line client with async methods and strongly-typed parameters and return values in like... a second. Ditto for Linq-2-SQL or similar frameworks.
Have you tried the CDK yet instead of using Troposphere?
Has the same fundamental problem as tfa: codes are not sticky / spanned so to know what sort of changes you should expect between two versions you have to look at every intermediate.

Meaning the tag is useless. If a release is “bad” you just yank it.

> it will show up as after 2.2020.1.1.3-bd

According to your scheme the last number is the release index in the day so this is nonsense: either -z replaces -bd or it’s a later release which appears before in the release list (assuming you have a descending alphanumeric sort).

You wouldn’t have both 2.2020.1.1.3-bd and 2.2020.1.1.3-z because they’re the same release with different crap tacked on.
https://www.wealthwords.com/blog/mind-games/
More relevant:

https://en.wikipedia.org/wiki/Goldman_Sachs#Subprime_mortgag...
The essay is just a long winded way of saying the quote from Eisenhower:
"Plans are worthless, but planning is essential"

Which is of course a short winded way of saying that the article makes a lot of sense. We for example have sprint goals - these are things that the team commits to actually getting done during the sprint. Then there are tasks in the sprint which may or may not overlap with the sprint goals and may or may not get done during the sprint.

It's always about trade-offs.
It seems like the gist is that the responsibility is on the application to be architect-ed (perhaps using one of the various libraries/strategies) to handle flow-control/back-pressure. The language itself doesn't directly help.
Getting Straight to the Point: Gaining Respect and Confidence
99% conviction rate, and 23-day detention without charges. One can imagine the various ways to torture people with no lasting marks in 23 days, including the « cold room » (soaking someone in freezing water in the aircon, which made Michael P Fay accuse himself in Singapore in 1995). The thing that I didn’t know is, it is apparently renewable in Ghosn’s case without charges, then converted to half a year of detention.
Is this really doing something complicated enough that I need an account for it? And why would I ever want to make an account with no demo or any idea of what this thing does and is about aside from two vague sentences?
This implies that time not spent using their software is time wasted doing nothing. Not that reducing boot times would be a bad thing, but that sounds more like a marketing gimmick. As kids we would wait for forever for our Commodore 64 games to load - knowing this we planned accordingly.
Indeed I am, the interpreter is the microcoded CPU.

Even modern 80x86 Assembly is a low level form of bytecode, given that the micro-ops that are processed by the microcoded CPU are completly unrelated to 80x86 Assembly opcodes.
Time is not exactly on an equal footing with space. It has the opposite sign in the metric signature, which is physically significant.

The differences boil down to the fact that the Lorentz group is O(1,3) whereas the (homogeneous) Galilean group is R^3 x O(3), both 6-dimensional.
Matrimony website
> Web pages ask you to refresh if anything goes wrong. Who has time to figure out what happened?

I feel like this is a feature, not a bug of software dev. The fact that you can push updates out so instantaneously allows you to work incredibly incrementally. You can make barely functional, inefficient things (shortcut hacks) just to make sure that your product is something that people actually use before focusing on optimization. If users are willing to put in the extra work to "refresh" the page, then certainly there's some real problem you are solving.
Because then we'd call them weeks and Sprints would be Fortnights :)

In all seriousness I'm curious about the story pointing. Does the team meet together for that at Pivotal?
In practice, most places I've worked treats sprints much closer to how you describe your iterations than to a fixed amount of work.

Most of the time, the sprint planning just provides some ceremony around ensuring important stories are discussed and points allocated, and priorities set, and the planned sprint is pretty much a line in the backlog that suggests an aspirational goal that is likely to change. The point is rarely to hit exactly that, but for it to serve as a means of talking about what needs to be done first - whether something needs to fit into this round, or can wait for the next. It also serves as a means of talking about inter-dependencies and sequencing of changes.
How to Choose Between Message DB and Kafka
Yes, I found it very deceptive as well. I have no idea why you're being downvoted.
> codes are not sticky / spanned so to know what sort of changes you should expect between two versions you have to look at every intermediate.

The only changes people usually care about are "will it break my software?" and "Am I using deprecated calls?" Beyond that, there's no standardized way to know what has changed between releases, and you'd have to look at every release regardless. Of course we could always add another metadata letter "n" to signify "new features". In fact, I'll add it...

> If a release is “bad” you just yank it.

And what if you can't yank it? That's what the "z" tag is for. If you can yank it then by all means yank it.
I don't quite agree here, developers need to have an idea of what they're working to so they can manage their own implementation time. If you don't make developers aware, you put too much control in the manager's hand which isn't a good thing here (unless you're referring to a developer lead but even then, individual developers should have an idea of when they need to complete by).
I think fedex, UPS might have a chance for disrupting Amazon like Amazon is disrupting them by providing warehouse space to Brands that want to move off Amazon but are unable too.
The word that you want to Google: Valisure.

Enjoy :) It's a lot easier to e.g. fundraise when you can demonstrate prior art and business models.

Might want to collaborate with some yoga places or Whole Foods-style hipster supermarkets. The "detox" crowd loves this sort of thing. (I will admit that the science of many hipster beliefs are not the most reliable but the market is definitely there) If you can successfully market to the Peloton/wannabe-health-conscious-middle-class homemaker crowd, I smell an unicorn in the making.

Another market is for people with allergies/autoimmune problems. It ranges from high tolerance conditions like e.g. mild enczema all the way to scorched-earth-intolerance where a single particle can trigger an allergy attack. This sort of crowd often have to watch what they eat and it can get troublesome if the food is not labeled properly.

If you want to discuss more, email's in profile.
>>> ... since they don't even know the message exists, they won't be seeking it out on alternative platforms.

>> .. Yes it's a problem. It's unclear it it limited to digital platforms.

> It's not a problem though...

You didn't seem to address the OP's issue ("they don't even know the message exists, they won't be seeking it out on alternative platforms") here at all?
I think the GP was referring to other US territories such as Puerto Rico, US Virgin Islands, etc.
> Citing your ignorance of events is not a compelling argument.

If you're going to make a case that there are harms from imposition on speech, then you need to be able to point to harms. An absence of demonstrable harms does not necessarily constitute ignorance on my part (though demonstrable harms might, although the good news for me is that can be easily remedied).

> Now I would not exactly consider this an "important idea". But arresting and convicting someone for that is egregious and, dare I say, offensive.

Your objection here is apparently to either the fact that the law was enforced, or to the specific punishment. I assume it's not the former, or laws protecting speech don't matter either. There's legitimate room for discussion of the later, but all conversations about what constitutes a reasonable consequence for violating the law are distinct from whether it's reasonable to have a law regarding any specific activity in the first place. And it's worth pointing out that there are other forms of speech such as fraud and perjury that can result in prison time.

> I could not possibly care less which ideas _you_ consider important or not. Or anyone for that matter. That's the whole point of free speech.

Actually the whole point of free speech is that ideas matter. Broad allowances aren't the primary value; the search for value in discourse is. Where broad allowances exist they flow from that central point.

When you understand that, it's easier to see why even societies which hold free speech as a high value do not consider every form of expression equally valuable, and why exceptions to allowances exist both by informal social construction and in legal formalisms. Including those that distinguish even crude expressions like "The Prime Minister is an Asshole" from slurs, or the idea that freedom is for teaching animals to pass on Nazi signifiers.
The end of the sprint should not be a deadline, but a goal. Wasn't that kinda the point of the article?

No one ever said a story has to fit within a sprint, that's not how agile or sprints are supposed to work. Some stories take multiple sprints. You should always break down large stories into sub-tasks that do fit within sprints.

This iteration thing your describing sounds almost exactly like sprints to me, just reworded to sound like their own thing.
Worth noting that eBay's old CEO now runs Nike. I wonder what his thoughts are.

Also, I wish I could have been a fly on the wall in the legal discussions where Nike must have extracted a promise from Amazon to remove counterfeit products despite Nike not selling on the Amazon platform.

Now THATs a privilege.
I am coming back to Unity for a side-gig VR thing after not touching it for a couple years. Unfortunately the timing is not great since they are still sorting out all the new offerings (XR Plugin vs. Player settings, Input systems, ECS from prefabs, etc.)

Is anyone doing VR with Godot? I have a couple questions:

1. What's the development cycle look like? In Unity I can hit play and put on the headset (Oculus Quest w/ Link, so essentially a Rift). No need to export a full build or go through multiple steps. Honestly this is the single most important factor for me since it allows quickly figuring out other problems. Does Godot support it?

2. Unity has made a big deal about DOTS and from initial tests it's legit. For VR on low-powered headsets (ultimate target is Oculus Go) these performance savings matter. How does Godot compare?

3. I don't know C++ and worried that I wouldn't be able to squeak by from bad usage of it. GDScript looks interesting but in this use case performance matters. I am doing a significant amount of Rust these days esp for hobby projects and would LOVE to be able to code in that. Are the Rust bindings to Godot good? Does it interfere with quick iteration? (looking at the repo it's hard to see what's going on and what the impact is on a real project)
Well that hits home pretty hard. I didn't know Steve Jobs did these kinds of interviews, thanks.
> that is even more relevant here

Is it really? It doesn't comment on the article or its content in any way. (The same was true the first time you posted it, when it was also top comment and received plenty of discussion.)
How to Make a Secret Phone Call (2015)
I mean, sure, you're absolutely right: the fundamentals are kind of a mess, especially with respect to quantum gravity. (But not cosmological gravity!) In many ways the Standard Model is a mixed blessing: it works really, really well... right up until it has nothing at all to offer. If it didn't work quite so well, things would be more interesting.

It doesn't help that there aren't all that many experiments left to do (in the fundamentals realm). Either they're likely to be uninteresting, or they're currently beyond our reach. I think there are going to be many lean years ahead for fundamental particle physics.

I used to work on neutrino experiments, but (as the username indicates), don't do that stuff any more. I could link my publication record, but all that's really there is a bunch of nitty-gritty detector characterization, plus a few blockbusters that my name got on because, well, I helped build the bloody detector :) Turns out that if you can build neutrino detectors that work, there are plenty of other things you can do with your life....
A major version number is still needed. ChronVer seems fine as a replacement for minor and micro versions (and rc and other designations).
Here's a simple test: do people actually want their lives to ressemble this? I'd wager most people don't want most of that stuff. It manages to both provide very little perceivable value, and looks to completely suck the life out of most things through rationalization.

To be fair, some of those things do seem valuable (mostly the health related stuff), and some things may actually appear in a different form, but the storytelling here is some of the least compelling I've seen in a while.
Machine learning is interesting in computer graphics for denoising path traced images för example. There also some uses in game developmemt where graphicsl artefacts might be detected during automated test runs instead of having an army of QA people.

Pretty sure ML have shown promising results in cancer classification in images (such as xray, etc). Not sure how this will pan out but the limited scope seems ideal .
Surprised to see India not mentioned in the article.

https://internetshutdowns.in/
Just an aside regarding stacktraces:

In all somewhat recent V8 using engines such as Chrome or node.js you get a "zero-cost" full asynchronous stacktrace these days. That's independent of the async. stacktrace provided through the dev.tools for a long time and "always on" for free.

The condition: You must use async/await. Even if you return a promise from a function, for that function to be included in the stacktrace is that you "return await thePromise;". Because of the await the context of the function calling an asynchronous function remains available and can be (and now is) used to create the stacktrace.

The Firefox JS engine does not have that feature (yet?) last time I checked.
It's technically possible to achieve the result op wants in sub millisecond time. However I'm not sure if Node.JS is the right stack for this. You'll have to carefully avoid object creation and reduce garbage collection overhead.
I got my first smart phone six months ago, Surprisingly it eats too much of time. For last 9 years I have been using nokia x201 qwerty phone, still it is my main phone. The main reason I use new smartphone is whatsapp, otherwise all other tasks can be performed on my dev machine.
That's more than a century ago. I was thinking about stuff built like in 1850-1950.
> Modern text editors have higher latency than 42-year-old Emacs. Text editors! What can be simpler? On each keystroke, all you have to do is update a tiny rectangular region and modern text editors can’t do that in 16ms. It’s a lot of time.

because we are going to make editors using JAVASCRIPT, which was never meant to be used this way
The first thing I'd do after installing this is to alias prefixing "aws-" to every commands. I like namespacing things as I suck at remembering names...
Part Time Jobs for IT Engineers to Earn Extra Money
Ah, the difference is that with iterations, there is never an 'end' and goals are just epics.

Correct, all larger stories should be broken down.

To be super clear, this is not my own thing. =) It is Pivotal's thing. I am just explaining the process as it was taught to me.
Thanks!

Do you use paid advertising also or primarily focus on ASO?