◆ C#

Improve INSERT performance of SQLite

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 C# tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskInsert these 100,000 records into the 'sensor_data' table in the 'telemetry.db' SQLite…+
Insert these 100,000 records into the 'sensor_data' table in the 'telemetry.db' SQLite database. Each record has a timestamp, device_id, and value. Do it as quickly as possible.
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 run this batch insert of 50,000 new user profiles into the 'users' table, help me make…+
Before I run this batch insert of 50,000 new user profiles into the 'users' table, help me make it faster. Suggest the optimal transaction strategy and any index recommendations for 'username' and 'email' that would speed up this specific bulk operation without slowing down reads too much.
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 nightly import of 1 million telemetry readings into the 'readings' table is killing our…+
Our nightly data sync is taking hours, and the operations team is on my back.
The nightly import of 1 million telemetry readings into the 'readings' table is killing our database performance. I've tried wrapping it in a transaction, but it's still too slow. The table has indexes on 'device_id' and 'timestamp'. What's the most likely bottleneck for this kind of large SQLite insert, and what's the best next move to dramatically cut down the import time without rebuilding the entire database schema?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI always seem to get burned by slow SQLite inserts when dealing with large datasets, leading to…+
I constantly struggle with slow data imports into SQLite, leading to missed deadlines.
I always seem to get burned by slow SQLite inserts when dealing with large datasets, leading to delays and frustrated stakeholders. What habit should I change to proactively identify and implement the right performance optimizations, like batching, proper indexing, or WAL mode, before I even start writing the import script, instead of scrambling to fix it when it's already too late?
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 C#'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.