$ ls -la drwxr-xr-x docs/ $ run script
◆ Bash

Manage background jobs

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 Bash tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskStart the 'data_ingestion_job.py' script in the background and redirect its output to…+
Start the 'data_ingestion_job.py' script in the background and redirect its output to 'ingestion_log.txt'.
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 start the 'report_generation_task', ensure it runs with low priority and that its…+
Before I start the 'report_generation_task', ensure it runs with low priority and that its output is logged to 'reports_output_2024_07_23.log' so it doesn't impact other critical services and I can review its progress later.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'process_large_dataset.sh' job, which has been running for 3 hours, just exited. There's no…+
A long-running data processing job just stopped without warning, and I don't know why.
The 'process_large_dataset.sh' job, which has been running for 3 hours, just exited. There's no error message in its log file, and I can't find it in the process list. I know David was doing some network configuration earlier. I'm afraid this means I'll have to restart the entire process, wasting hours of compute time. What's the best way to determine why the job stopped and how to resume it efficiently, if possible?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often start long-running scripts in the background and then get sidetracked, forgetting to…+
I keep forgetting to check the status of my background jobs, leading to missed failures.
I often start long-running scripts in the background and then get sidetracked, forgetting to check their status until much later, only to find they failed hours ago. This delays data availability and causes frustration for the data science team. What habit can I change to ensure I'm always aware of the real-time status of my background jobs without constantly checking manually?
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 Bash'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.