◆ JavaScript

Compare two dates

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCompare 'startDate' and 'endDate' to ensure 'startDate' is not after 'endDate' before saving…+
Compare 'startDate' and 'endDate' to ensure 'startDate' is not after 'endDate' before saving the event, so we prevent invalid date ranges.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I compare 'startDate' and 'endDate' to validate the event range, ensure the comparison…+
Before I compare 'startDate' and 'endDate' to validate the event range, ensure the comparison handles different date formats and timezones correctly, and also considers edge cases where dates might be identical, so the validation is robust across all user inputs.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA user just created an event where the end date, '2024-03-01', is before the start date,…+
The system allowed a user to create an event where the end date was before the start date.
A user just created an event where the end date, '2024-03-01', is before the start date, '2024-03-05'. I'm afraid our date comparison logic isn't handling the specific date objects or formats correctly, maybe comparing them as strings instead of actual dates. The product owner is furious about this data corruption. What's the most common mistake when comparing dates, and what's the most reliable way to ensure 'startDate' is always before or equal to 'endDate'?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly debugging date comparison problems, particularly when dates come from user forms…+
I keep encountering issues with date comparisons, especially when dealing with user input or different data sources.
I'm constantly debugging date comparison problems, particularly when dates come from user forms or external APIs with varying formats and timezones. It feels like a never-ending battle to get 'dateA is before dateB' right. What habit should I change to ensure my date comparisons are consistently accurate and robust, preventing invalid date ranges and the resulting data integrity issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.