◆ Apache Cassandra

Perform month-end closing activities

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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a report of all 'financial_transactions' for the month of November 2023 from the…+
Generate a report of all 'financial_transactions' for the month of November 2023 from the 'accounting_data' keyspace, grouped by customer ID, and export it as a CSV. This is due for the finance team by end-of-day.
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 send this month-end report to the auditors, make it robust and verifiable. Add…+
Before I send this month-end report to the auditors, make it robust and verifiable. Add checksums for data integrity, include a summary of any data anomalies found, and ensure all time zones are explicitly handled for accurate date ranges.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to run the final aggregation query for the month-end close on the 'sales_metrics'…+
I'm trying to aggregate data for the month-end close, but the query is timing out and impacting other production queries.
I'm trying to run the final aggregation query for the month-end close on the 'sales_metrics' table, but it's consistently timing out and I'm seeing increased latency on other production queries. I'm afraid this indicates a full table scan or an inefficient query pattern for the volume of data. I can't just kill the query without potentially corrupting the close. What's the most likely diagnosis for this performance hit, and what's the best next move to get the data without disrupting the live 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.