281 karma · joined February 1, 2022
I've done some work with the public data from the US Occupational Safety and Health Administration (OSHA). OSHA does a great job of making detailed data on inspections and accidents public. If memory serves me correctly, it turns out there are about two deaths per day from work-related causes in the US...
I think it makes a ton of sense, but again, I suspect there's a fair bit of personal preference in these kinds of things.
I'm eager to see what other styles and architectures people suggest!
I have anecdotally also heard that some are using k8s, but I've not seen that myself. Slurm [1] is basically built for this stuff; that's definitely what I would use!
This is Cunningham's Law [1]! And it seems exceedingly plausible after observing behavior on many online forums!
PostGIS is one such extension, and I would argue that if your use case involves geospatial data, then PostGIS alone is enough of a reason to use PostgreSQL!
I know of some institutions with F&A rates at or above 70%!! I presume that an institution trying to negotiate a higher F&A rate than this would have some significant pushback!
In practice, however, most organizations are extremely risk-averse when it comes to wrongful termination lawsuits. And as such, they'll have a lengthy "performance-improvement plan" (PIP) that can last three to six months and is meant to serve as evidence that an employee's poor performance was the reason for dismissal.
There are also, of course, extreme cases where someone can be fired "for cause" when they've committed some kind of egregious violation (e.g., embezzling funds, fraud, corporate espionage).
This is also supported by the fact that the question was only completed by 1322 responders, which is about 10% of total responders.
And to answer your question, we use the Rust API because all of our backend services are in Rust, and we like to stay in Rust whenever possible.
I would also add that there now seems to be more of an emphasis around being intentional in how languages foster community. The C and C++ communities (in my opinion) became how they are not by design, but mostly by accident or chance.
I think my only gripe is that the Rust API seems (to me at least) to be less well documented than the Python API. I guess Python is the de facto data science language, so maybe that explains it.
I'm probably an outlier, but when I saw this name I thought of the eating disorder [1].
I think probably the major challenge for the social sciences is the nature of the phenomena under study. Psychologists, sociologists, and economists aren't studying physical quantities that can easily be measured. Instead, they typically study abstract and intangible variables. Measuring these accurately is very difficult.
I'm not sure of the exact numbers, but I would guess that an overwhelming majority of the Top 500 Supercomputers [3] are running Slurm. And as others have noted, research computing centers in academia all mostly run Slurm. And Slurm also dominates in the DoE national labs in the US.
Oh, and as a [potentially apocryphal] fun fact, the name "Simple Linux Utility for Resource Management (SLURM)" is a backronym from the soda in Futurama! [4]
[1] https://en.wikipedia.org/wiki/Oracle_Grid_Engine
It seemed that gmfawcett was indicating that there was a dataframe library in _Python_ that existed prior to Pandas. I was curious what that library was/is, as I'd not heard that before.
Statisticians are funny!