◆ Apache Cassandra

Write code and scripts

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 taskWrite a Python script that connects to the Cassandra cluster, queries the 'user_sessions' table…+
Write a Python script that connects to the Cassandra cluster, queries the 'user_sessions' table for all sessions older than 30 days, and deletes them. Ensure it includes proper error handling for connection failures.
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 commit this new data ingestion script, make it robust for production. Add logging for…+
Before I commit this new data ingestion script, make it robust for production. Add logging for failed inserts, implement retries with exponential backoff for transient database errors, and ensure it can be easily configured for different environments without code changes.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy data migration script just failed halfway, leaving some records in a corrupted state in the…+
The new data migration script failed halfway through, corrupting some records in the target Cassandra table, and I'm not sure if the rollback mechanism worked correctly.
My data migration script just failed halfway, leaving some records in a corrupted state in the new Cassandra table. I thought my rollback logic was solid, but now I'm not sure if it fully reverted the changes or if I've made things worse. The client expects this data live by tomorrow morning. I'm afraid to try running it again without understanding the current state. What's the immediate issue here, and what's the safest first step to assess the damage and recover without losing more data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy code and scripts frequently hit unexpected edge cases in production or fail completely,…+
My scripts often encounter unexpected edge cases or fail in production due to insufficient error handling or testing.
My code and scripts frequently hit unexpected edge cases in production or fail completely, requiring urgent fixes and causing downtime. It feels like I'm always reacting. What habit should I change in my development and testing process to build more resilient and fault-tolerant code, so it handles the real-world chaos of a distributed system?
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 Cassandra'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.