◆ Apache Cassandra

Document network processes

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 taskUpdate the network diagram for the database replication factor changes in the disaster recovery…+
Update the network diagram for the database replication factor changes in the disaster recovery region, reflecting the new 3x replication on all critical tables 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 finalize the network documentation for the new data center, make it easier for our…+
Before I finalize the network documentation for the new data center, make it easier for our on-call engineers to troubleshoot connection issues. Highlight the critical firewall rules for inter-node communication and the specific port ranges used by the database, and flag any known network latency choke points between regions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe just lost a production Cassandra node, and the new data isn't replicating to its peers as…+
We just lost a Cassandra node in the production cluster, and replication isn't happening as expected.
We just lost a production Cassandra node, and the new data isn't replicating to its peers as quickly as it should be, causing some read inconsistencies. The network monitoring shows no obvious packet loss, but I'm afraid there's a subtle misconfiguration in the gossip protocol or a firewall rule I missed during the last security audit. What's the most likely network-related issue preventing proper replication, and what's the best immediate step to verify the network health between the remaining nodes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur network-related incident response times for database issues are consistently too high. It…+
Network-related incidents often take too long to resolve due to incomplete or outdated documentation.
Our network-related incident response times for database issues are consistently too high. It often comes down to engineers hunting for accurate diagrams or current port configurations. We're losing valuable minutes with every outage. What habit should I change in how I maintain our network process documentation to ensure it's always up-to-date and immediately actionable during a critical incident?
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.