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

Software Engineer for AI Training Data (School Specific)

@ G2i Inc | Remote

Software Engineer for AI Training Data (Python)

@ G2i Inc | Remote

Software Engineer for AI Training Data (Tier 2)

@ G2i Inc | Remote

Data Engineer

@ Lemon.io | Remote: Europe, LATAM, Canada, UK, Asia, Oceania

Artificial Intelligence – Bioinformatic Expert

@ University of Texas Medical Branch | Galveston, TX

Lead Developer (AI)

@ Cere Network | San Francisco, US