jjjensen90

The odd thing is that in most countries the age of consent is below (sometimes significantly below) 18. So we’ve got strange mixed signals.

Commonly electrical systems and/or the battery itself in ICEs cause unattended fires.

I think your response is emotionally-charged and mixes feelings with data and anecdotes, which is unhelpful in a complex discussion of a sensitive topic, so I hesitate to engage further, but…

I’ve reviewed much of the existing data on minor-attracted persons (which is scant). The problem is that the samples are heavily biased towards including individuals who are caught or self-admit for care, which is not a very good representative sample. As a few of the studies and articles you posted mention, there was little study done until very recently. You also make the leap without supporting data that this system would catch those most likely to offend. Generally I would say the data is insufficient to conclude in any direction other than dumber people get caught doing crimes at a higher rate than smarter people.

Lastly, I have some serious doubts about your expertise in mental health and the study thereof from your use of “mentally retarded” and “retardedness”. You should know for future discussions that the clinical terminology has shifted to “intellectually disability”.

This is not true and a harmful generalization. There are dumb people of every type. There are probably smart people you respect that engage in CSAM and are minor-attracted. This kind of privacy invasion will only net a tiny section of that population, as most know that lack of caution is life or death.

I've commented on it before, but I have to say again, the Timescale Helm charts are by far the best way I've ever seen a database run in Kubernetes, and actually from an operations, backup, and scaling perspective they are the best database management experience I've had period. Huge fan, always enjoy talking with Feike, and keep up the great work Timescale team.

I brought timescale (a postgres extension that brings time series to postgres) to my current IoT job, and it has been the biggest engineering win of my career. The tooling, community, extensions, and quality of postgres + very high performance inserts + reads has reduced costs for the business dramatically versus the previous cassandra + sql server setup. We have tens of billions of events in multiple timescale hypertables, with many thousands of inserts per second running on r5.xl nodes in k8s (4 vcpu, 30gb ram) and they don't break a sweat.

So yeah, it's "good enough".

I brought Timescale to my current job, and I have to plug their Helm charts. They have made deployment, backup, scaling, and config so easy on k8s for Timescale. Probably the best postgres chart that exists, period. Great work TSDB team.

Yes, there was a midterm held in 1918.

If you're referring to the WFH situation staying with us forever, it definitely will not. Things may change somewhat, but in discussing WFH with a variety of execs who employee tens of thousands of engineers collectively, there is a very strong majority of engineers who would come back to the office tomorrow if able.

Again referring to Go's imperfect but interesting handling of this problem, the style in Go would be:

  data, err := open("/var/foo")
  if err != nil....

In fact, the compiler will make you deal with both values after assignment unless you explicitly ignore one of the return values.

Though I don't think it's perfect, languages like Go that treat errors as simply another type and you check as a return value do get closer to treating errors and success symmetrically versus an exception throwing and typing system like some other languages.

It's incredible the quality you can get in that price range. I bought a PRS SE Custom 24 for $700 and it is like a museum piece compared to what $500-700 would have bought when I was starting out 20 years ago. Absolutely awesome.

I realize you've made a weak straw man argument here, but there are important distinctions that need to be made in discussions about platform/user base moderation. While there are classes of people protected from discrimination by civil rights laws, what is not protected is discrimination or refusal of service for customers based on what they do rather than who they are. Banning someone for cheating, harassment, circumventing moderation, etc is not comparable for banning users of a certain race, and even attempting to equivocate them is a weak argument.

I run multi terabyte, billions of rows HA postgres in kubernetes using a helm chart and Patroni (baked into the chart), which uses the native k8s API for automatic failover and pgbackrest for seamlessly provisioning new replicas. It's a single helm chart and is by far the easiest DBA I've ever done in many years.

Because it's possible that there are many, many infected who don't seroconvert or ever manifest symptoms, and therefore would not have been tested with a PCR test, and would have a negative antibody test. We can see this in effect in studies of household attack rates and seroconversion. See this recent preprint and interesting thread (/r/covid19 is a strict science sub, not to be confused with /r/coronavirus) https://www.reddit.com/r/COVID19/comments/hdxwf5/intrafamili...

There is no "death rate" metric. There is CFR (case fatality rate) and IFR (infection fatality rate). We know that there are many more infections than known cases, and serological studies point to total IFR <1%, with massive stratifications by age (<50 having extremely few fatalities, and >50 having increasing IFR every age bracket).

We have no idea what the required percentage of infection is for herd immunity, given that we don't know what percentage of people are naturally immune or resistant, what percentage of people clear the virus without any antibody response, etc.

There is a decent amount of research beginning to indicate we won't need nearly that level of infection to reach herd immunity. It's not guaranteed but I'd keep an open mind.

https://arxiv.org/abs/2005.03085 https://www.ncbi.nlm.nih.gov/pubmed/32209383 https://www.medrxiv.org/content/10.1101/2020.04.27.20081893v...

IFR is not a fixed value and is affected by many things. For example, intial viral load may be higher in NYC than many other places, vitamin D levels, air pollution, etc. There is no single IFR for any disease.

Have you tried Kotlin?

Being a cop is exceedingly safer than many professions where we don't bend the standard of protecting human life like we do for cops. About the same amount of lumberjacks die in the US during work as police. About the same number of toddlers kill themselves with guns every year as police die in the line of duty.

Part of the duty of a police officer is to put themselves in higher-danger situations than other citizens in order to protect and serve the public, up to and including taking physical harm or death (in fact half of police fatalities every year are in car accidents on duty).

If you train to be a hair trigger, protect-yourself-at-all-costs cop, that's how you will behave.

Marsh v. Alabama is not relevant in this case, so says the Supreme court https://en.wikipedia.org/wiki/Manhattan_Community_Access_Cor...

Why is it not possible? New platforms are started and grow all the time. For example, TikTok only came out in 2016 and is massive.

You already cannot discriminate against a customer because of certain characteristics of who they are (race, orientation, etc). You can however kick someone out of your restaurant for what they say, how they act, or what they do, similar to being banned or fact checked on private social media platforms.

There is no free speech on private social media platforms

Disagree here, myself and many many peers considered ourselves "experienced" programmers before college (starting at 7 years old etc), and we were barely intern material in reality. Push yourself every day and learn tools (there are always new tools to learn) to be relevant--this goes for students, new grads, seniors, etc.

No trouble, it is a system that can do many things and has many optional pieces. It is fundamentally a cloud native orchestration system.

You are completely wrong. It is trivial to have your k8s control plane and your workload cluster in something like an ASG, and basically know nothing about the nodes in either group. I'm not even using GKS or EKS, just ASGs on AWS. My servers and applications are cattle, not pets.

I knew literally nothing about k8s in September and now I have multiple clusters humming along, treating the worker cluster nodes as a generic pool of compute, autoscaling the cluster as well as the pods inside it. Upgrading is a breeze, I have great observability, I can deploy experiments and new applications with a single CI step or click, in fact I have nodes that are killed and get replaced for cost savings by SpotInst in the middle of the business day and I don't even need to know about it. My load balancers and even DNS are all provisioned for me and I can use the same Helm charts to create an identical staging and production environment.

Kubernetes IS the spirit of the Cloud and 12 factor apps. It's not that scary, and with tools like Rancher and k3s you can make it even simpler.

It's probably more of an investment than other replies to your comment, but having a receiver with at least a center channel and left/right speakers does wonders to level the volume between dialogue and other sounds. My receiver even has a dialogue setting which emphasizes the human vocal frequencies on the center channel.