I built DSConcepts to help people understand data science concepts through simple examples and hands-on practice. The goal was to build an app that explains concepts in an easy-to-follow way, with diagrams you can play with and questions to check your understanding.

It is for people learning these topics for the first time, as well as data scientists looking for a refresher. I wanted a place where you could connect a statistical idea to a familiar business question and practise the skills alongside it.

It currently has two parts:

  • ๐Ÿง  Concepts: learning journeys for forecasting and experimentation.
  • ๐Ÿ’ป Code lab: SQL practice with a dataset, an editor, and exercises for interview prep.
The DSConcepts homepage showing forecasting and experimentation journeys, SQL Practice, and clearly labelled work-in-progress or planned topics.
๐Ÿงญ Pick a concept journey or head to SQL Practice. Future topics are marked as planned or work in progress.

๐Ÿง  Concepts: learn with examples

There are two learning streams, both using Northstar, a fictional online retailer, as the running example:

  • ๐Ÿ“ˆ Forecasting โ€” 31 stops. How much might Northstar sell next week? Start with trends, seasonality, and uncertainty, then work through baselines, backtesting, and forecasting methods.
  • ๐Ÿงช Experimentation โ€” 24 stops. Northstar is testing a faster product page. Does it help customers buy more, and is checkout still reliable? Follow the example through randomization, metrics, confidence intervals, power, and rollout decisions.

We use fictional examples based on real-world business situations to help you understand how each concept applies in a practical setting.

Here are two examples of the kinds of questions we explore:

  • ๐Ÿ“ˆ Forecasting growth: Northstarโ€™s sales increase before the holidays. Should the team expect that growth to continue into January?
    • ๐Ÿ“… Looking at previous years helps explain the difference between a lasting trend and a seasonal pattern.
    • ๐Ÿšš That distinction matters when deciding how much stock to order.
  • ๐Ÿ›’ Experimenting with a new feature (A/B test): More customers buy after a new page launches. Was it the new page, or did a promotion bring in different customers?
    • ๐Ÿงช This gives random assignment a practical purpose: creating a fair comparison.
    • โš–๏ธ We also consider whether a change improves purchases while making another part of the experience worse.

The examples give you something concrete to think about as the ideas become more detailed. Terms such as seasonality, uncertainty, or guardrail metrics are easier to discuss when you can relate them to a decision a team needs to make.

๐Ÿ’ป Code lab: SQL interview prep

The second part is a SQL code lab for practising interview-style questions and sharpening your SQL skills. The problems cover:

  • ๐Ÿงฎ Core topics: aggregations, joins, ranking, ROW_NUMBER, and other window functions.
  • ๐Ÿข Business data: deciding what should be counted and how tables relate is part of the practice. Joining orders to payments, for example, can repeat an order when it has multiple payment attempts โ€” which is why a total can come out too high even when the SQL runs without an error.
  • ๐ŸชŸ Window functions: rank customers, compare a purchase with the previous one, or calculate spending over time. These skills come up in both interviews and day-to-day analysis.
  • ๐Ÿ’พ No setup: everything runs on provided data, so you can practise without building your own database.

๐Ÿค Open source: help improve it

The learning journey is open source on GitHub. Weโ€™d love fellow data scientists to contribute more learning materials, share feedback, or send a pull request to improve the existing content.

If you have a useful way of explaining a topic to colleagues, this could be a place to share it. A practical example, a clearer explanation, or a question you often see people struggle with can help improve the material for everyone. Contributions do not need to be large to be useful.

No sign-up is needed to try it. Notes, progress, and SQL drafts stay in your browser, so they do not sync across devices.

๐Ÿš€ Try DSConcepts or explore the source on GitHub. Pick a concept, try an example, or work through a SQL problemโ€”and let me know what would make it more useful.