Find the business question before writing code.
Pick one dataset or receipt table and write the plain-English decision it should support. Then list three fields needed to answer it cleanly.
A small interactive practice tool for turning daily study into visible evidence: SQL questions, Python cleaning reps, dashboard thinking, and clear analyst storytelling.
Pick one dataset or receipt table and write the plain-English decision it should support. Then list three fields needed to answer it cleanly.
Fill in what you actually did, then copy a concise summary for a portfolio log, GitHub README update, or interview practice note. The fields save in this browser only.
The goal is not random studying. Each sprint should produce a small artifact Daniel can mention in a portfolio update, GitHub note, or interview answer.
Junior data analyst applications need visible evidence: clean questions, reproducible analysis, understandable charts, and concise recommendations. This board nudges every practice session toward that evidence.
Open the board, run a 25-minute sprint, check off the evidence habits, and save the result as a short project note or dashboard improvement.
Each finished sprint gives Daniel language for interviews: how he framed the problem, cleaned the data, chose the visual, and communicated the result.
The best practice reps can become improvements to the grocery inflation project, Dataset Gym, or a short written case-study update.
After a sprint, Hermes can check the SQL, review the explanation, or turn the result into a polished portfolio entry while keeping the analysis honest.