The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need a function that converts the CSV export from our analytics into the structure our API…
Execute — do the immediate task
+I need a function that converts the CSV export from our analytics into the structure our API expects. Write a function named parseAnalyticsCsv that takes a CSV string and returns an array of objects with keys date (ISO), userId (string), and events (number). Include input validation and a thrown Error if required columns are missing. Keep it compatible with Node 18 and browsers.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I merge this into the repo, make the function easy to review and maintain: surface the…
Improve — make it easier to accept
+Before I merge this into the repo, make the function easy to review and maintain: surface the assumptions about date formats and header names up front, make error messages actionable, and add a short example showing input CSV and resulting output. Flag any lines that would make a reviewer hesitate about edge cases like empty rows or quoted fields.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I wrote parseAnalyticsCsv and most tests pass but CI fails when the CSV contains "01/02/2024"…
Decide — diagnose the stuck moment
+I wrote parseAnalyticsCsv but tests fail on one case
I wrote parseAnalyticsCsv and most tests pass but CI fails when the CSV contains "01/02/2024" dates. I am not sure whether those are month/day or day/month in production. The code currently uses Date.parse. Who should I ask to decide the format, what questions do I ask them, and what is the safest interim code change so CI stops failing without changing production data interpretation?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over several projects I keep writing similar CSV parsing utilities that diverge on tiny assumptions…
Become — change the pattern
+I keep rewriting parsing functions for slightly different CSVs
Over several projects I keep writing similar CSV parsing utilities that diverge on tiny assumptions — date formats, optional columns, trimming rules. Where am I losing time and introducing bugs, and what single pattern or library and three conventions should I adopt to avoid doing this again?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other programming language work people do in JavaScript.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.