Sept. 5, 2023, 11:04 a.m. | /u/takenorinvalid

Data Science www.reddit.com

Every time I've tested a SQL query and realized that some null somewhere broke my CONCAT statement, or run an R script and realized that I forgot to add "na.rm = TRUE" to a function somewhere, I wonder what was going through the development team's minds when they decided to build these tools these ways.

Why isn't ignoring nulls the default behavior?

Genuinely curious if there's a logic to this that I haven't considered.

build datascience development function null query sql sql query team through true

Data Architect

@ University of Texas at Austin | Austin, TX

Data ETL Engineer

@ University of Texas at Austin | Austin, TX

Lead GNSS Data Scientist

@ Lurra Systems | Melbourne

Senior Machine Learning Engineer (MLOps)

@ Promaton | Remote, Europe

Research Scientist, Demography and Survey Science, University Grad

@ Meta | Menlo Park, CA | New York City

Computer Vision Engineer, XR

@ Meta | Burlingame, CA