◆ Apache Cassandra

Define how data will be stored

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 Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet the data definition language for the user profile table ready. We need to store user ID as…+
Get the data definition language for the user profile table ready. We need to store user ID as a UUID, username as text, and last login as a timestamp. Make sure user ID is the primary key.
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 finalize this user profile table definition, make sure it's resilient to high write…+
Before I finalize this user profile table definition, make sure it's resilient to high write loads. Think about how we'll query it later for user activity and what might cause hotspots.
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 analytics team just asked to query user activity by region, and our current user activity…+
The new analytics team wants to query user activity by region, but our current data model only uses user ID as the primary key.
The analytics team just asked to query user activity by region, and our current user activity table only has user ID as the primary key. I'm worried about creating massive partitions if we add region directly, but I also can't tell them no. What's the likely impact on read performance and what's the best way to support this without blowing up our cluster?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and credibility because new teams come in with query patterns we didn't…+
I keep having to refactor data models because new query patterns emerge that we didn't anticipate.
I keep losing time and credibility because new teams come in with query patterns we didn't design for, forcing me to refactor data models. What habit should I change to better anticipate future access patterns and avoid these costly redesigns, especially when the initial requirements are vague?
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.