The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The dashboard shows timestamps as raw ISO strings. Convert the createdAt and updatedAt fields to…
Execute — do the immediate task
+The dashboard shows timestamps as raw ISO strings. Convert the createdAt and updatedAt fields to user-local format: show date as MMM DD, YYYY and time as HH:mm in the user's locale, updating when the timezone changes. Make sure this runs on page load and when the user switches accounts, ready for Monday's demo.
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 ship this to the UX lead, make the date formatting easy to review: put the format function…
Improve — make it easier to accept
+Before I ship this to the UX lead, make the date formatting easy to review: put the format function next to the display component, show an example input and output at the top, and flag any places that still call toString on the Date object or assume UTC.
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
+Users in CET see times shifted by several hours after daylight saving; I used fixed timezone…
Decide — diagnose the stuck moment
+times show wrong timezone for some users
Users in CET see times shifted by several hours after daylight saving; I used fixed timezone offsets when formatting timestamps for the activity feed. I can't reproduce locally because my machine is in PST. What's likely causing the DST shift and the safest fix to ensure dates render correctly across timezones without requiring server changes?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep wasting cycles because each component formats dates differently, introducing layout shifts…
Become — change the pattern
+formatting logic duplicated and brittle
We keep wasting cycles because each component formats dates differently, introducing layout shifts and timezone bugs. Which habit should we change to reduce bugs: where to centralize formatting, a small API for relative vs absolute time, and one test to prevent regressions?
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.