Skip to content

Instantly share code, notes, and snippets.

@khajahussainecomm
Last active July 10, 2026 06:02
Show Gist options
  • Select an option

  • Save khajahussainecomm/d4f7a36a77141815d879e30fe432bb22 to your computer and use it in GitHub Desktop.

Select an option

Save khajahussainecomm/d4f7a36a77141815d879e30fe432bb22 to your computer and use it in GitHub Desktop.
10 ChatGPT Tips That Actually Made Me More Productive

10 ChatGPT Tips That Actually Made Me More Productive

ChatGPT has become one of the tools I use almost every day. Whether I'm debugging code, writing documentation, learning a new framework, or brainstorming ideas, it's usually my first stop.

Like many people, I initially asked simple questions and accepted the first answer. Over time, I realized that the quality of ChatGPT's responses depends far more on how you ask than what you ask.

Here are ten techniques that have consistently helped me get better results.

1. Give ChatGPT a Role

Instead of asking:

Explain SQL indexing.

Try:

Act as a senior SQL Server database administrator and explain SQL indexing to a beginner.

Giving ChatGPT a role helps it tailor the explanation to a specific audience. This simple change often produces clearer and more useful answers.

2. Explain Your Goal

Don't just describe the task---explain why you're asking.

For example:

Explain dependency injection because I'm preparing for a .NET interview. Include one practical example.

Knowing your objective helps ChatGPT adjust the depth and style of its response.

3. Break Large Tasks into Smaller Ones

Rather than asking ChatGPT to build an entire application, split the work into smaller steps such as database design, API development, authentication, frontend, and testing.

The responses become much more focused and easier to review.

4. Always Ask for Examples

A definition explains an idea. An example shows you how to apply it.

Whenever you're learning something new, ask for a practical example in the programming language or framework you're using.

5. Compare Different Prompts

Changing just a few words in a prompt can produce a very different answer.

Before deciding which response is better, compare them side by side instead of switching between browser tabs. Tools like Compare text make it much easier to spot small differences in prompts and AI responses, especially when you're fine-tuning instructions.

6. Tell ChatGPT What to Avoid

Negative instructions are surprisingly effective.

Examples:

• Keep the answer under 300 words. • Don't use technical jargon. • Avoid bullet points. • Don't assume prior knowledge.

These small constraints often improve the final result.

7. Ask ChatGPT to Critique Its Own Answer

After receiving an answer, ask:

Review your answer and identify anything that could be improved.

This often uncovers missing details, assumptions, or better alternatives.

8. Continue the Conversation

If you're working on one project, keep asking follow-up questions in the same chat.

The previous context helps ChatGPT provide more consistent and relevant answers.

9. Use ChatGPT for Repetitive Work

ChatGPT is excellent for repetitive tasks like generating test cases, explaining compiler errors, improving documentation, or creating sample JSON.

If you're working with APIs, large JSON responses can be difficult to read. Converting them into a table makes debugging much easier, and Json to table is a quick way to visualize complex JSON structures.

10. Think of It as a Conversation

The best results usually come after a few follow-up questions.

Ask things like:

Can you simplify this? Show another example. What are the trade-offs? Is there a better approach?

Each follow-up gives ChatGPT more context and usually leads to a stronger answer.

Final Thoughts

Getting better answers from ChatGPT doesn't require complicated prompt engineering. Simple habits like providing context, asking for examples, refining prompts, and continuing the conversation can dramatically improve the quality of the responses you receive. Start with one or two of these techniques, and you'll likely notice the difference immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment