◆ Apache Cassandra

Insert hard-coded UUID via CQLsh

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 taskInsert a new record into the 'user_sessions' table with a session ID of…+
Insert a new record into the 'user_sessions' table with a session ID of 'a1b2c3d4-e5f6-7890-1234-567890abcdef' for user 'john_doe', starting at '2023-10-27 10:00:00+0000', using CQLsh.
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 inserting these new hard-coded UUIDs into the 'sensor_readings' table, check if any…+
Before inserting these new hard-coded UUIDs into the 'sensor_readings' table, check if any existing entries use the same UUIDs. If so, flag them for review and suggest new UUIDs to avoid collisions, ensuring all inserts are unique and don't overwrite critical data.
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 insert a UUID into the 'transaction_log' table, but it keeps failing with a type…+
I just tried to insert a UUID into a new table, and it's throwing a 'type mismatch' error.
I'm trying to insert a UUID into the 'transaction_log' table, but it keeps failing with a type mismatch. The column is defined as 'text', but our documentation says UUIDs should work. I'm afraid of corrupting the log or missing critical transactions if I force it. Is the schema wrong, or am I missing a casting step? What's the safest way to get this UUID in there?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly generating and inserting hard-coded UUIDs for test data or one-off fixes, which…+
I keep having to manually generate and insert UUIDs for test data, which is slow and error-prone.
I'm constantly generating and inserting hard-coded UUIDs for test data or one-off fixes, which is slow and often leads to copy-paste errors. This eats into my time before Friday's deployment. How can I change my habit to streamline this process, perhaps by automating generation or using a more robust method, without sacrificing data integrity for the QA team?
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.