r/dataanalysis • • 20h ago

A practical learning order for beginners, with a realistic timeline

1 Upvotes

I get asked fairly often how to start in data analysis with no experience, so here is the order I would follow if I had to begin again, plus a timeline that is honest about how long this takes.

Start with spreadsheets, not Python. Excel or Google Sheets will still be part of the job even if you later use other tools. Learn how to clean a messy export, write formulas, build a PivotTable, and make a simple chart that answers one question. If you cannot turn a raw file into a clear summary, the rest of the stack will not help much. This is a few weeks of work if you practice on real files, not just tidy tutorial datasets.

Add a little statistics next, but keep it practical. You want medians as well as averages, a basic sense of distributions, and a habit of asking whether two things that move together are actually causing each other. This is not about becoming a statistician. It is about not presenting a clean number that is quietly wrong.

Then learn SQL. In a lot of companies, this is how data actually gets pulled. I would learn it in this order: SELECT and FROM, WHERE, ORDER BY, aggregates with GROUP BY, then INNER and LEFT JOINs. Practice until you can explain what a join keeps and what it drops. Also watch for joins that duplicate rows and inflate totals. That mistake is easy to miss.

After SQL, pick one visualization tool and stay with it long enough to get decent. Power BI, Tableau, or even well-built Excel dashboards are all fine. The skill is not the software brand. It is showing a finding so a non-technical person can use it.

Python can come after that. I would focus on pandas and basic plots first. Machine learning can wait. Plenty of junior work is Excel, SQL, and a clear explanation, not a model.

The part that matters for applications is a small portfolio. Three to five projects is enough if they are finished. Use public data, pick a question a real team might ask, write down your steps, and be honest about the limits of the data. A short write-up of one good project beats a list of unfinished notebooks.

On timing: if you can give this 8 to 10 hours a week, six to twelve months is a realistic window for junior or internship-level work. Less time per week stretches that out. A two-month crash plan usually produces shallow projects. The better test is not "how many tools have I opened," but "can I take a messy question and come back with a clear, careful answer?"


r/dataanalysis • • 22h ago

FAERS is a masterclass in why you model the data-generating process before the data

11 Upvotes

If you want a dataset that punishes naive counting, the FDA's adverse-event database (FAERS, public via OpenFDA) is perfect. Twenty-plus million reports, and almost every property a data scientist relies on is absent or adversarial:

No denominator. Reports are suspicions filed voluntarily. There is no exposed-population count, so no incidence rate can ever be computed — any "rate" derived from it is fabricated.

Duplicates by design. The same case can be submitted by the patient, a pharmacist, and the manufacturer, plus follow-up versions of each. Deduplication and restricting to primary-suspect reports is the first pipeline step, not an optional cleaning nicety.

The collection process reacts to publicity. For semaglutide, reports by year received run: 40 through 2017, 1,142 in 2018, 3,515 in 2020, 6,302 in 2022, 9,483 in 2023, 14,287 in 2024, 19,977 in 2025. That curve tracks adoption and media attention. Treating it as a risk curve is the classic error.

Coding artifacts dominate naive rankings. MedDRA Preferred Terms include administrative entries — "Off Label Use" alone accounts for 7,316 semaglutide reports. Rank raw terms and your top "adverse events" are paperwork.

Missingness is informative and huge. Outcome and age fields are blank in a large share of reports; blank means unknown, not none.

The standard tool that survives all this is disproportionality analysis — ROR/PRR against the full database, with the Evans criteria (PRR ≥ 2, chi-square ≥ 4, ≥ 3 cases) as a screening rule. In an October 2026 snapshot, semaglutide's impaired gastric emptying posts ROR 117.2 (95% CI 112.7–121.9), and 96.9 when restricted to 2023–2026 — a signal that persists after you control for the publicity era. That persistence check is the whole game: a statistic that survives interrogating the generating process.

What other public datasets do people here use to teach "the count is not the phenomenon"?