Meh, this was a survey conducted at 4 different companies. It only proves correlation, not causation. And even then, it only proves it at these 4 companies since they didn't use random sampling from a larger population. Most of the rest of the article is unfounded speculation about the cause of this correlation. Definitely not an impressive study by any means.
I have a cheap drawing tablet I purchased for about $20. It works wonders for whiteboarding and diagramming things for my remote coworkers. Especially when used in conjunction with tools like Google Jamboard, it's almost as good as an in-person whiteboard.
Doesn't seem to be a very credible article. There's an awful lot of pontificating about the disastrous outcomes of COVID-era policies without any supporting evidence. The whole thing reads a bit like a non-sequitur.
Also, there's an awful lot of talk about "we in the scientific community" for someone who is still in medical school.
Not the original commenter, but our team has recently been dealing with this exact thing. It depends on the specifics of your use case, architecture, etc., but there is a lot of value in keeping application Terraform code in the same repo as your applications. The main benefit is that it's a simpler developer experience to make infrastructure changes related to their specific app. You can still have a big repo with a bunch of internal modules and core infrastructure code, but having the apps have their own infrastructure code can lead to developers having more autonomy in the DevOps process.
As a transport I agree. But as a config file format? I'm a little skeptical.
The main benefit of a flat file format for configs is that it can be added to source control and edited by any plaintext editor. If I kept config as protobuf, I would need special tools to handle it, which could be annoying (e.g. if I'm remoted into a remote system). It would also make it more difficult to see diffs between different config versions stored in git.
This. Security questions are almost always visible to humans in plaintext, and those humans are expected to be the judge of whether the security question was answered correctly.
I used to do random characters, but have switch to a string of random dictionary words. Still not perfect (since "a string of random words" could potentially be accepted as a valid answer), but I feel like having it be human-readable makes it less prone to that kind of fuzzing.
In my case, I'm running FreeNAS/TrueNAS for storage and a Plex jail. I'd imagine there are a number of people in the same boat considering the popularity of TrueNAS.
TrueNAS Scale is Debian-based. It's easy to migrate from Core to Scale [0]. You do lose your jails but there's both an official Plex chart for the underlying k3s, and a community-supported one in TrueCharts [1].
TrueNAS is a pretty small niche, no? Not only that, but the usual way of using NAS involves doing compute tasks on a separate server.
Besides, the FreeBSD based TrueNAS Core will almost certainly be deprecated and replaced with Linux based TrueNAS Scale within the nest couple of years. Further strengthening the idea that this is a pointless platform to support.
