avishetar2242 / September 2026 — January 2027

Start with PostgreSQL.
Think like a data analyst.

A complete, beginner-first path: 104 guided lessons, realistic scenarios, runnable code, measurable checkpoints, and a portfolio you can explain.

12 Sep 2026 → 11 Jan 2027Monday–Saturday · 3:00 pm IST60–90 minutes / lessonSundays off
0 / 104Lessons completed
0Benchmarks passed · score ≥80
Average recorded score / 100
0Hours you have logged
Your 18-module roadmap and benchmark targets
Start here · setup, study method, and the four-month roadmap

Before lesson 1

  1. Install PostgreSQL from the official download page. Use PostgreSQL 16 or newer; pgAdmin is a graphical query editor.
  2. In pgAdmin, connect to your own server with your chosen password. Create a practice database named analyst_practice, select it, then open Tools → Query Tool.
  3. Paste SELECT 'Hello, analyst!' AS greeting; and press Execute. Read the one-row result in Data Output.
  4. For every lesson, copy or download the complete SQL example. Run the whole example in your practice database. All data is synthetic and included; no company database is needed.
-- Your first SQL statement
SELECT 'Hello, analyst!' AS greeting;

-- Optional terminal workflow after creating your practice database:
-- psql -d analyst_practice -f lesson_001.sql

This HTML teaches SQL; it is not a database engine. Run SQL in pgAdmin or psql. Phone users can read and track here; executing SQL requires access to a PostgreSQL query editor. Examples use inline data or scratch objects within transactions. Run each complete example; if a failed transaction leaves your editor blocked, execute ROLLBACK; before trying again.

Your daily routine

  1. 10 min: recall the last lesson without looking.
  2. 20 min: read the lecture; explain each new term.
  3. 20 min: predict and run the worked example.
  4. 25 min: complete the scenario task independently.
  5. 10 min: test edge cases, score yourself, and save notes.

Every sixth lesson in a module is a checkpoint. A score below 80 means revisit the weak skill; keep studying on the scheduled dates and use the next session's recall block for review. Sundays remain free.

Phases: 1–24 SQL foundations and aggregation; 25–54 relational querying and data quality; 55–84 analytical SQL and performance; 85–104 semi-structured data, portfolio and interviews. These phases span four calendar months.

Target role: junior data analyst. You will define metrics, clean and reconcile data, explain query results, and build a reproducible analytical portfolio.

Manage delivery, preserve progress, and export backups

Daily lesson delivery

Automation setup is being verified.

The HTML opens any lesson immediately. Codex delivers the scheduled lesson in the original task. This page cannot run a background scheduler while closed.

Optional direct controls: in Chrome or Edge, choose the outputs folder containing this HTML with “Connect dashboard folder.” Controls then save postgres-learning-control.json beside this file for the daily automation to read. Reconnect after reopening if needed. Browser progress alone is not visible to Codex.

No shared folder connected. Scheduled delivery uses its existing saved state.

Pausing through this page tells scheduled runs to stay quiet; it does not disable the underlying schedule. To change the 3:00 pm time or disable the schedule itself, use Codex scheduled-task controls or ask in the original task.

Backups and storage

Completion, scores and notes are stored in this browser. Clearing browser data, changing browser or moving the HTML may make that storage unavailable. Export progress regularly. Imports merge records and never erase unrelated lessons.

Calendar export contains all 104 sessions with a 3:00 pm start and a reminder. Import it once to avoid duplicates. A calendar event does not generate a lesson by itself.

Preservation instruction
Never delete this file or change its format unless you explicitly request it. Routine progress goes into browser storage or a separate control file. No delete/reset button is included. Keep an exported HTML copy as your own backup.

No analytics, remote scripts, tracking pixels or external accounts are used by this dashboard. Links to reference websites open only when you choose them. Your email, account details and device identifiers are not embedded in this file. Hosting providers may process ordinary access logs. Progress stays in your browser until you export or sync it.

Concept lecture

Worked scenario · runnable PostgreSQL

Predict the output first. Download or copy the example, run it, then change one input and explain the effect.

Expected result and explanation check

SQL walkthrough

    Trace inputs → transformations → output. Explain the purpose of every line and identify which lines would change for a different business rule.

    Your independent scenario task

    Module benchmark

    Check your understanding

      Reveal concept-check answers
        Score rubric · 100 points, pass at 80

        Self-assessment is not automatic code grading. Keep evidence in your notes. For each category use 0 = not attempted, 10 = substantial help or errors, 20 = mostly independent with a minor gap, 25 = independent and correct.

        • Correctness (25): exercise meets the stated business requirement and expected checks.
        • Edge cases (25): tests at least two relevant cases, such as missing input, zero, duplicates, an empty collection, or boundary values.
        • Explanation (25): explains the concept, each important line and a limitation.
        • Reproducibility (25): saves runnable work and enough instructions/evidence to reproduce the result. For written tasks, saves a complete, evidence-based artifact.

        Do not award a checkpoint pass for copied code or an unrun project. If a required artifact is missing, record the gap and revisit it.