Day 36 of improving my Data Science skills

Source: Dev.to

If you work with data long enough, you stop wishing for fancier models and start wishing for something simpler – confidence.

• Confidence that what you’re seeing is real.
• Confidence that what you’re reporting won’t fall apart under questions.

That was the thread running through my learning today.

Data Visualization

In data visualization, I wasn’t just drawing charts; I was learning how easily visuals can mislead if we’re careless.

Histograms

Histograms taught me how distributions can hide or exaggerate patterns depending on bin size.

Box Plots

Box plots forced me to confront variability, outliers, and spread—not just averages.

Error Bars

Error bars forced me to admit uncertainty instead of hiding it. Instead of pretending a value is exact, I show how much it can realistically vary. That small visual choice makes a big difference, because decisions aren’t made on perfect numbers; they’re made within ranges.

Importing Data

Then came importing data, where many data problems are quietly born. I worked with SAS and Stata files using pandas, and it reinforced something uncomfortable: reliable analysis doesn’t start with models or plots. It starts with respecting how data was originally structured.

Knowing how to read SAS and Stata files means:

• You can preserve meaning instead of guessing it.
• You can catch assumptions early.
• You’re less likely to build insights on silently altered data.

That’s the kind of quiet skill that separates using data from understanding data.

Twitter APIs

Finally, I stepped into the world of Twitter APIs and authentication. Not scraping, not downloading files, but asking a live system for data, with permissions, rate limits, and constraints.

It made one thing clear: real‑world data doesn’t wait for us. We negotiate access to it.

Key Insight

Most data failures don’t happen at the “advanced” stage. They happen when we underestimate the basics:

• A misleading histogram.
• An ignored error bar.
• An imported dataset we never questioned.
• An API response we assumed was complete.

If you’re building products, making decisions, or hiring people who work with data, this is the real differentiator. Not who knows the most tools, but who knows where trust can break.

That’s the skill I’m deliberately building.

And tomorrow, I’m pushing deeper: more practice, more questioning, more discomfort. Because trustworthy insights are never accidental.

—SP