◆ Apache Airflow

Install packages in Airflow (docker-compose)

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskInstall `scikit-learn==1.0.2` in our Docker environment for orchestrating data pipelines so the…+
Install `scikit-learn==1.0.2` in our Docker environment for orchestrating data pipelines so the new `predictive_analytics_dag` can run its machine learning models tonight.
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 add `pandas` to our core image for orchestrating data pipelines, let's make sure we're…+
Before I add `pandas` to our core image for orchestrating data pipelines, let's make sure we're managing dependencies intelligently. Can you verify if other DAGs also need it, and if there's a way to isolate this dependency to only the DAGs that require it, so we don't bloat the image or create version conflicts for other teams?
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 new library, `fastparquet`, is needed for the `data_lake_ingestion_dag`, but installing it in…+
A new library, `fastparquet`, is needed for the `data_lake_ingestion_dag`, but installing it breaks `pyarrow` for another critical DAG.
A new library, `fastparquet`, is needed for the `data_lake_ingestion_dag`, but installing it in our Docker image for orchestrating data pipelines breaks `pyarrow` for the `financial_reconciliation_dag`. I'm afraid of introducing instability into our core data platform, and I can't delay the data lake ingestion. What's the most likely way to resolve this dependency conflict without affecting the financial DAG?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently waste time resolving dependency conflicts or versioning issues when installing…+
I frequently encounter dependency conflicts or versioning issues when trying to install new Python packages for Airflow DAGs.
I consistently waste time resolving dependency conflicts or versioning issues when installing new Python packages into our Docker images for orchestrating data pipelines. This often leads to breaking existing DAGs and delaying new features. What habit should I change to proactively manage and isolate package dependencies more effectively across our data pipeline orchestration environment?
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 Apache Airflow'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.