◆ Apache Cassandra

Create data models and schemas

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 taskCreate the data model for the product catalog. We need product ID, name, description, and…+
Create the data model for the product catalog. We need product ID, name, description, and price. Product ID should be the primary key, and we'll query mostly by product ID.
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 product catalog data model, make sure it's optimized for both quick…+
Before I commit this product catalog data model, make sure it's optimized for both quick lookups by product ID and efficient searches by category. Consider how adding new attributes later might impact performance.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMarketing just asked to search products by keyword across the description and name fields. Our…+
The marketing team wants to search products by keyword across description and name, but our current product model only allows queries by product ID or category.
Marketing just asked to search products by keyword across the description and name fields. Our current product data model only supports queries by product ID or category, and I'm afraid adding a full-text search index will crush our write performance. I can't tell them it's impossible. What's the likely performance hit and what's the best next move to support this without overhauling everything?
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 accuracy because I struggle to design data models that can gracefully…+
I consistently struggle with designing data models that can gracefully handle evolving search requirements without major re-writes.
I keep losing time and accuracy because I struggle to design data models that can gracefully handle evolving search requirements without major re-writes. What habit should I change to better incorporate future search flexibility into initial data model designs, especially when the exact search criteria aren't fully known upfront?
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.