I think that some of the biggest issues with omitted variables could have been address by using the "new" Stata interaction syntax ("new" in the sense that has been available in Stata since 10 releases ago) instead of rolling their own products and forgetting to include the main effect.

Emailing them privately in advance of the meeting will give them the opportunity to think about your input and, in some cases, reply and engage with you about the policy. It might not change their mind, but it will definitely help them see others' perspectives on their upcoming decision.

By using an LLM to fabricate citations, authors are moving away from this noble pursuit of knowledge built on the "shoulders of giants" and show that behind the curtain output volume is what really matters in modern US research communities.

[Data Preparation] --> [Data Analysis] --> [Result Preparation]

Neither Python or R does a good job at all of these.

The original article seems to focus on challenges in using Python for data preparation/processing, mostly pointing out challenges with Pandas and "raw" Python code for data processing.

This could be solved by switching to something like duckdb and SQL to process data.

As far as data analysis, both Python and R have their own niches, depending on field. Similarly, there are other specialized languages (e.g., SAS, Matlab) that are still used for domain-specific applications.

I personally find result preparation somewhat difficult in both Python and R. Stargazer is ok for exporting regression tables but it's not really that great. Graphing is probably better in R within the ggplot universe (I'm aware of the python port).

We didn't find the frozen DuckLake setup useful for our use case. Mostly because the frozen catalog kind of doesn't make sense with the DuckLake philosophy and the cost-benefit wasn't there over a regular duckdb catalog. It also made making updates cumbersome because you need to pull the DuckLake catalog, commit the changes, and re-upload the catalog (instead of just directly updating the Parquet files). I get that we are missing the time travel part of the DuckLake, but that's not critical for us and if it becomes important, we would just roll out a PostgreSQL database to manage the catalog.

ESTA/ETIAS gets automatically approved within a few minutes of paying for the fee (I guess this is true for 99.999% of applicants).

Very few countries allow people to just show up and cross the border. US citizens had that privilege in a lot of places, but it looks like it’s changing now.

My understanding of the Italian political climate of the 60s, 70s, and 80s is that there were political groups/cells (on both the far right and far left) that organized around violent acts to further their political goals (which involved the eventual authoritarian takeover of the Italian government by either the far right or far left). For example, you can think of the Red Brigades to be akin to the Black Panthers, but with actual terrorism.

In contrast, most political violence in America has been less organized and more individual-driven (e.g., see the Oklahoma City Bombing). For better or worse, the police state in the US has been quite successful in addressing and dispersing political groups that advocate for violence as a viable means for societal change.

While the methods alone cannot fix it all ("You can’t fix by analysis what you bungled by design" [1] after all), it gets somewhat closer to unbiased results.

[1]: https://www.degruyterbrill.com/document/doi/10.4159/97806740...

There are interesting null results that get published and are well known. For example, Card & Kruger (1994) was a null result paper showing that increasing the minimum wage has a null effect on employment rates. This result went against the common assumption that increasing wages will decrease employment at the time.

Other null results are either dirty (e.g., big standard errors) or due to process problems (e.g., experimental failure). These are more difficult to publish because it's difficult to learn anything new from these results.

The challenge is that researchers do not know if they are going to get a "good" null or a "bad" one. Most of the time, you have to invest significant effort and time into a project, only to get a null result at the end. These results are difficult to publish in most cases and can lead to the end of careers if someone is pre-tenure or lead to funding problems for anyone.

At the end of the day, a 3-course sequence in a CTE pathway (which is the CA requirements for a high school CTE certificate in California) doesn't prepare you for a career in the same way as being in journalism class prepares you to be a journalist or being in theater prepares you to be an actor. Students will most likely need to pursue some form of post-secondary training (either through a community college or on-the-job) to become somewhat competent in their field.

Looking at the statistics[1], the US went from a 23.2% college completion rate in 1990 to 39.2% completion rate in 2022, or a 67% increase in college degree completions. If you assume that X in the population is constant over time, mechanically you will need to enroll and graduate students from lower percentiles of X in order to increase the overall college completion rate in the whole population.

This process might be particularly acute at "lower tier" institutions that cannot compete with "top tier" institutions for top students.

[1]: https://nces.ed.gov/programs/digest/d20/tables/dt20_104.20.a...

A Parquet file is a static file that has the whole data associated with a table. You can't insert, update, delete, etc. It's just it. It works ok if you have small tables, but it becomes unwieldy if you need to do whole-table replacements each time your data changes.

Apache Iceberg fixes this problem by adding a metadata layer on top of smaller Parquet files (at a 300,000 ft overview).

This could become a two pronged problem where you have fewer people to provide care while they are trying to implement a new EHR which results in a decrease in productivity because of the need of learning a new system.

It seems to me that going from "F1 and F2 generations of mice respond differently to the smell of acetophenone if their parents were exposed to it" to "well, human trauma is inherited and there isn't anything we can do about violent behavior" is somewhat far-fetched and smells like neo-eugenics.

If you have individual ELOs, you could pre-seed the ranking using averages and then let the algorithm take over.

An interesting consequence about the wearable ban is that they also banned medical electronic devices (e.g., heart monitors or blood sugar monitors) and parents are required to meet with administration to approve their use [1].

[1]: https://greenwichfreepress.com/schools/greenwich-schools-ann...

By the way, not even government agencies have good geo data, even when they should. I needed up to date address information for work, so I bought a map from my local county assessor's office. In my mind, the assessor should have the most recent data on properties, as their main mission is to collect taxes annually. I was wrong. Their data is about 4 to 5 years wrong, with whole "new" subdivisions missing from their inventory. Google Maps kind of has them on the map; I believe that their geolocation data comes from real estate platforms when new houses are on the market. OSM is about 10 years behind in my area. I am submitting edits as I find them.

If someone has a better idea on where to find address data, please let me know.

This is different from qualitative analysis because the data reduction is done “by hand” by the researcher.

The difference between the “automatic”, model-based data reduction in quantitative research and the “subjective” reduction in qualitative research is then amplified when people say that quant is more objective than qual analysis. The discussion, instead, should be about the quality of the work and whether the final conclusions are warranted by the methods instead of the method itself.

The blog post list this as the original Stata code:

> replace event`i’ = 1 if delta_mct`i’ != 0 | spouse_delta_mct`i’ != 0

and this as the correct one:

> replace event`i’ = 1 if (delta_mct`i’ != 0 | spouse_delta_mct`i’ != 0) & delta_mct`i’ != . & spouse_delta_mct`i’ != .

It looks like the authors didn't properly handle missing values in Stata, leading to marking people with missing health information being marked as being "severely ill" instead of being excluded from the analysis.

It's an unfortunate mistake, but it happens.