It is fine to say there isn’t evidence for something. For some reason the poster decided to invite this challenge by calling it “easily debunked” instead. A debunking is specifically a claim that there’s evidence that the original claim was wrong.
This is just a form of gish galloping [0]. Like I alluded to, it's disappointing that discourse on HN is at a place where enough of the participants are supportive of this as long as it's happening to the "other team."
> During a typical Gish gallop, the galloper confronts an opponent with a rapid series of specious arguments, half-truths, misrepresentations and outright lies, making it impossible for the opponent to refute all of them within the format of the debate.
See also Brandolini's law [1] if this feels familiar:
> The amount of energy needed to refute bullshit is an order of magnitude bigger than that needed to produce it.
It is not any more effort to say “It is an unsubstantiated and unprovable rumor that ICE has deputized proud boys.” It is also a much more accurate reflection of the level of confidence.
If you call somebody’s claim “easily debunked,” that’s a proactive offer of counter evidence. It isn’t Gish gallop to accept that offer of counter evidence.
Anyway, where else is the conversation supposed to go? The post had the offer of an easy debunking and no other content.
As someone on the other side of this - applications sink to the bottom and often never receive a response when sent to places like jobs@, so LinkedIn is a way to at least get the attention of a real person.
I’d suggest calling out on your job posting that LinkedIn messages may be missed and the email is the correct place to reach out.
Merely anecdotal but my worst experiences over the last year have been with startupschool companies - not saying they’re all bad (maybe I’ve been meeting the statistical minority that aren’t great) but as a part of the community I really expected better
Depends on the use case but all physical resources are finite in some limit so you may want to distribute that load so the different domain processes can scale appropriately. When/where/how is dependent on the application you’re building.
We possibly have encountered graduate students with differing lifestyles, but a lot of the grad students I know in the natural sciences have grueling schedules between taking classes, TAing, and conducting research. The way these activities are structured may not correspond to a typical 9-5 but they’re still intense in their own right. To add onto this - attending conferences isn’t always on the universities dime, often it comes out of grants and other associated project costs that are allotted for your research. Maybe the university does foot the bill in other cases, but these are marginal costs when compared to the realizable value brought by graduate students in the form of monetizable knowledge and subsidized teaching costs. The latter point is at the crux of most tension between graduate students and university administrations, and there’s a large imbalance between the tangible value that grad students (and most academic researchers) bring to universities and the way that they’re compensated.
