Jupyter Notebook Basics

Jupyter is the data scientist's notebook. Code, output, and narrative in one document. Learning Jupyter well pays dividends for every future project.

30 min · Reviewed 2026

A Living Document

A Jupyter notebook is a browser-based editor where you mix code cells, markdown cells, and their outputs in one file. Run a cell, see the result right below, write an explanation, continue. It is the default tool for data science because it fits how exploration actually works.

The two main cell types

Code cells: run Python (or R, Julia, etc.) and show output
Markdown cells: formatted text with headings, links, LaTeX math

Getting started

# Install pip install jupyterlab pandas matplotlib # Launch jupyter lab # Or use cloud versions # - Google Colab (colab.research.google.com) # - Kaggle Notebooks # - Hugging Face Spaces with Jupyter # - GitHub CodespacesFour ways to get a Jupyter environment

The kernel is the key concept

A kernel is the running Python (or other) process that executes your cells. Variables persist across cells because they live in the kernel. This is why the order you run cells matters more than the order they appear in the notebook.

Must-know shortcuts

Shift+Enter: run cell, go to next
Ctrl+Enter (Cmd+Enter Mac): run cell, stay here
A: insert cell above, B: insert below (command mode)
M: convert to markdown, Y: convert to code
00: restart the kernel

Magic commands

# Time a cell %%time expensive_function() # Inline plots %matplotlib inline # Run shell commands !pip install seaborn !ls -lh data/ # Inspect a variable ?pd.read_csv # shows docstringJupyter magic commands

Common anti-patterns to avoid

Giant cells with 200 lines of code (break them up)
No markdown explaining the flow (readers drown)
Leaving unused code in the middle of the notebook
Hardcoding file paths that only work on your machine
Not pinning library versions for reproducibility

The big idea: Jupyter is exploration married to narration. Treat your notebook as a story, not just a scratch pad, and your future self (and collaborators) will thank you.

End-of-lesson check

10 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-data-jupyter-basics

What is the main idea of "Jupyter Notebook Basics"?
1. Jupyter is the data scientist's notebook. Code, output, and narrative in one document. Learning Jupyter well pays dividends for every future project.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Jupyter Notebook Basics"?
1. notebook
2. Jupyter
3. kernel
4. markdown
Which use of AI fits this topic best?
1. Giant cells with 200 lines of code (break them up)
2. Let the AI decide what matters without your review
3. Code cells: run Python (or R, Julia, etc.) and show output
4. Use the answer before checking whether it fits the situation
Which limitation should you watch for in this topic?
1. Code cells: run Python (or R, Julia, etc.) and show output
2. Explain the topic in plain language
3. Organize a draft for human review
4. Giant cells with 200 lines of code (break them up)
What should a careful learner remember about "The out-of-order bug"?
1. Use "The out-of-order bug" as a reminder to verify the AI output before anyone relies on it.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about Jupyter be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about Jupyter.
Which action would help you apply "Jupyter Notebook Basics" responsibly?
1. No markdown explaining the flow (readers drown)
2. Use the tool to avoid thinking through the tradeoff
3. Keep going even if the output conflicts with a trusted source
4. Markdown cells: formatted text with headings, links, LaTeX math
Which choice is a bad use of AI for this lesson?
1. No markdown explaining the flow (readers drown)
2. Code cells: run Python (or R, Julia, etc.) and show output
3. Ask for a plain-language explanation of notebook
4. Compare the answer with a trusted source

← Back to interactive lesson

Tendril · Creators · AI Foundations