Category: AI

  • How I Turned ChatGPT into My SQL Study Partner

    How I Turned ChatGPT into My SQL Study Partner

    After learning the basics of SQL syntax, I knew the fastest way to improve for me personally is simple: practice through problem-solving.

    LeetCode is one of the best places for that. Many of its SQL questions are based on real interview problems from top tech companies.

    If you’re short on time, start with this: SQL 50 Study Plan. It covers roughly 80% of the SQL question types you’ll see in interviews.


    Why I Needed a Better System

    At first, I used Notion to track my mistakes — but I ran into two problems:

    1. Entering and organizing everything took too long.
    2. I couldn’t easily see which topics I struggled with most or revisit similar problems.

    The Breakthrough: Using ChatGPT as My SQL Partner

    Then I moved my learning into a ChatGPT Project — and it’s so much better.

    With memory and automatic summarization, ChatGPT could help me spot patterns, save notes, and generate personalized review plans.

    (Heads up: these features are only available to paid users.)

    Here’s the setup that worked best 👇


    Step 1. Create a “Learning SQL” Project

    Create a new Project called “Learning SQL.”

    In the Edit Instructions, paste the following prompt (you can tailor it to your career goals and target industry):

    Instructions Prompt (click to see)

    🎯 Goal

    Help Ellen systematically master SQL and understand its real-world business applications, to be fully prepared for a data analyst position (especially in AI or Gaming) by March 2025.

    🧠 Learning & Collaboration Method

    All SQL learning, mistakes, and reviews will take place within this project.

    Ellen will provide questions (from LeetCode or custom business scenarios).

    My tasks:

    Break down the problem-solving approach and key syntax

    Identify common mistakes and show optimized solutions

    Extract a generalized SQL template

    Automatically record each question into the Error Log (with priority level and topic tag)

    💡 Business Extension (Real-Life Case)

    After each SQL explanation, I will add a short “Real-Life Case” example to show how this query applies to real-world data tasks — focusing on at least one of these areas:

    AI industry: model log analysis, data labeling tracking, conversion monitoring, A/B testing

    Gaming industry: player retention, engagement, in-game purchases, mission completion rate

    Market Growth / Go-To-Market: user growth funnel, channel conversion, marketing campaign analysis

    Example Output:

    🏢 Real-Life Case: This type of SQL is often used in gaming companies to calculate Day-2 retention rate, helping the team identify player churn points and optimize reward mechanics.

    📊 Learning Records & Summaries

    I will automatically track Ellen’s questions and mistakes within this project.

    After each question, I will generate a mini summary automatically (no need for Ellen to ask):

    Problem meaning

    Key syntax

    Common mistakes & improvements

    Real-world business application

    When Ellen says:

    “Summarize today” → I’ll create a daily summary

    “Review this week” → I’ll output a structured weekly report, in this format:

    🗓️ Weekly Review 📘 Total questions: ❌ Mistakes: 🧠 New SQL concepts learned: 💡 Real-life business use cases: 📈 Areas for improvement:

    🔁 Review & Reinforcement

    I can automatically generate review questions or similar follow-ups based on Ellen’s record.

    Each week, I’ll provide a SQL skills diagnosis and next week’s practice recommendations.

    If Ellen says “mock interview”, I’ll create industry-specific SQL interview questions (AI / Gaming / Market Growth) and give scoring + feedback.

    🪄 Output Style

    Clear logic and step-by-step explanations

    Focus on reasoning rather than memorization

    Use simple examples and business logic to explain why

    When queries are complex, include tables or diagrams to visualize the process

    📦 Learning Structure (Automatically Maintained)

    SQL Learning

    ├─ Basic Queries ├─ Aggregation & Grouping ├─ Subqueries ├─ Window Functions ├─ Interview-Focused Questions ├─ Error Log ├─ Real-Life Business Cases (AI / Gaming / Market Growth) └─ Learning Logs

    ✅ Summary

    This project helps Ellen not just write correct SQL, but also understand the business impact behind each query.

    By the end, Ellen will be able to confidently explain why a SQL query matters, what insights it provides, and how it drives value in real-world analytics.


    Step 2. Create a “📌 Quick Commands” Chat

    To make communication faster, I created a chat in the project and renamed the chat to “📌 Quick Commands.”

    It’s my personal shortcut panel for high-frequency prompts like:

    Shortcut panel

    The below is for myself, you don’t need to reply anything.

    🎯 3 Universal Commands

    👉 “Remember this is an SQL mistake…”

    👉 “Summarize today / Review this week”

    👉 “How is this used in real life?”


    🧠 Learning & Practice

    💬 To generate a question:

    “Give me an SQL question (window function / aggregation / interview style).”

    🧩 If stuck on a problem:

    “I’m working on LeetCode 176, and I don’t understand it.”

    📌 To mark a mistake:

    “Remember this is an SQL mistake, high priority, window function.”

    🔍 To explain syntax:

    “Explain how DENSE_RANK() works.”


    📊 Summaries & Reviews

    🗓️ Daily summary:

    “Summarize today.”

    📆 Weekly review:

    “Review this week.” / “Summarize this week’s SQL learning.”

    🔁 Error review:

    “Help me review my mistakes.”

    🧱 Practice similar questions:

    “Give me a few similar questions to practice.”

    🧠 Extract templates:

    “Help me extract today’s SQL templates.”


    💼 Real-World Applications & Industry Scenarios

    🏢 General business use:

    “How would this SQL be used in a real company?”

    🎮 Gaming analytics:

    “Give me a gaming industry SQL analysis question.”

    🤖 AI analytics:

    “Give me an AI company SQL analysis question.”

    📈 Market growth:

    “Give me a Market Growth–related question.”

    💬 Further explanation:

    “How is this type of SQL typically used in AI / Gaming / Market Growth?”


    🔁 Reinforcement & Diagnosis

    🧩 Skill diagnosis:

    “Assess my understanding of window functions.”

    🎯 Targeted practice:

    “Give me 3 questions on the topics I’ve been struggling with.”

    🧭 Learning plan:

    “Help me plan exercises to improve my aggregation function skills.”

    Set reminders:

    “Remind me every Friday to review SQL mistakes.”


    📈 Progress Tracking & Exports

    📊 Check progress:

    “How’s my current SQL learning progress?”

    🧾 Export highlights:

    “Help me compile an SQL summary suitable for my portfolio.”

    🗂️ View mistakes:

    “List my current high-priority SQL mistakes.”

    Delete content:

    “Delete the SQL mistakes I saved about window functions.”


    Step 3. Example in Action

    After solving a few LeetCode problems, I send my results to ChatGPT like this (remember to use the Study mode):

    My learning input

    These are the questions I worked on today:

    1378. Replace Employee ID With The Unique Identifier

    Here’s my answer:

    # Write your MySQL query statement below
    SELECT unique_id, name
    FROM Employees AS id
    JOIN EmployeeUNI AS uni
    ON id.id = uni.id
    

    I didn’t know how to make names without a unique_id show up with NULL.

    It didn’t occur to me that I should use a LEFT JOIN for that.

    1068. Product Sales Analysis I

    This one wasn’t difficult — I solved it quickly by myself.

    1581. Customer Who Visited but Did Not Make Any Transactions

    I managed to solve it, but not very quickly, and I needed to look up some references.

    This one can be considered a mistake question for my review list.

    ChatGPT then:

    • Analyzes my reasoning and explains what went wrong
    • Provides an optimized solution
    • Adds a real-world business use case (AI / Gaming / Market Growth)
    • Saves and summarizes the mistake for future review

    The Results

    This setup helps me:

    1. Instantly see all my mistakes and weak spots
    2. Understand how each SQL query applies to real business contexts
    3. Get personalized practice and review plans without extra effort

    Try It Yourself

    Here’s your starter pack:

    1. Begin with LeetCode SQL 50
    2. Create your own “Learning SQL” Project
    3. Copy the prompts above
    4. Let ChatGPT track, summarize, quiz, and review for you

    If you try this method, I’d love to hear your experience or share if you’ve found an even better way to learn SQL!

  • GEO Explained: Optimizing Your Content for AI Platforms

    GEO Explained: Optimizing Your Content for AI Platforms

    What is GEO?

    Generative Engine Optimization (GEO) focuses on optimizing content specifically for AI-driven search engines and generative models like ChatGPT, Google’s AI Overviews (SGE), Gemini, and Perplexity.

    GEO ensures your content is found, interpreted, and cited in AI-generated answers—not just listed in search results.


    GEO: To-Dos and Don’ts in Content Strategy

    At its core, GEO is about creating structured, authoritative content that AI can trust.

    1. Shift in Content Focus and Keywords

    Do:

    • Use a natural variety of related terms, concepts, and entities to create a semantic web around your topic.
    • Anticipate user queries and provide thorough solutions.
    • Use conversational language that mimics human speech.
    • Target long-tail queries like “how to improve organic traffic using AI.”
    • Offer direct answers, lists, and actionable advice.

    Don’t: Stuff your content with repetitive keywords. AI prioritizes context and meaning.


    💡 Example: Instead of “SEO tips,” write “how to improve organic traffic using AI” to match natural search queries.


    2. Emphasize Authority and Trust (E-E-A-T)

    AI looks for credible, authoritative content. Focus on:

    Do:

    • Experience: Include case studies or firsthand examples.
    • Expertise: Publish accurate, well-researched content with visible author credentials.
    • Cite sources: Use statistics, expert quotes, or reputable links.
    • Digital PR & backlinks: Get mentions in industry publications or “best-of” lists.
    • Topical authority: Cover your niche thoroughly so AI cites your content multiple times.

    Don’t:

    • Focus only on short-form content that lacks depth.

    3. Optimize Content Structure for AI

    Do:

    • Use clear headings and hierarchy (H1, H2, H3) to organize content.
    • Incorporate bullet points, numbered lists, and tables for easy AI parsing.
    • Include FAQs for succinct, AI-friendly information.
    • Keep content concise and non-redundant across the page.

    Don’t:

    • Duplicate answers within the same page or across multiple pages.
    • Use long, unstructured paragraphs that are hard for AI to scan.
    • Ignore logical content flow or headings.

    4. Technical & Distribution Strategies

    Do:

    • Implement schema markup to define your content type (Article, Organization, etc.).
    • Ensure crawlability and fast page speed; do not block AI bots in robots.txt.
    • Keep important content in HTML text rather than JavaScript or images.
    • Optimize multimedia with alt text, captions, and transcripts.
    • Distribute content on forums, directories, and industry sites to increase AI visibility.

    Don’t:

    • Hide content behind complex scripts or images.
    • Rely solely on one distribution channel for exposure.

    5. Using AI Tools Wisely

    Do:

    • Use AI to brainstorm ideas and create outlines.
    • Always add human touch, including tone, experience, and insights.
    • Edit AI-generated content to align with E-E-A-T principles.

    Don’t: Publish mass, unedited AI content. AI rewards clarity, context, and human insight.


    Sources

    What Is Generative Engine Optimization (GEO) [Tips & Workflows To Do It] by Charlie Marchant

    What Is Generative Engine Optimization (GEO)? by Neil Patel

  • How to Vibe Code?

    How to Vibe Code?

    TL;DR

    “Vibe coding” is rapidly becoming the new standard for software development, with dev productivity jumping 10x in recent months.

    Key Stats:

    • 1 in 4 experienced founders say 95%+ of their code is AI-generated
    • Tools like Cursor and Windsurf are everywhere in startup accelerators

    The Workflow:

    1. Planning First – Spend extensive time creating detailed project plans, architecture docs, and step-by-step instructions for AI
    2. Modular Implementation – Build section by section, not all at once
    3. Test-Driven – Write integration tests first to guide AI and catch mistakes
    4. Version Control Everything – Commit constantly to enable quick rollbacks when AI goes off-track

    Top Tools:

    • Cursor – Fast, great for frontend
    • Windsurf – Slower but thoughtful, can run alongside Cursor
    • Claude Code – Best for experienced developers
    • Replit/Lovable – Beginner-friendly with visual interfaces

    Vibe Coding Is Taking Off Fast

    It’s looking less like a trend and more like the new normal. If you’re not on board, you risk getting left behind.

    Adoption

    • Explosive growth: Dev speed jumped from 10× six months ago to 100× just last month.
    • Recent wave: By summer 2024, tools like Cursor were everywhere in YC batches, fueling a rapid shift.

    AI-Generated Code

    • 1 in 4 founders: Say 95%+ of their code is AI-written.
    • Not newbies: These are experienced builders who could code it all themselves—but now let AI handle most of it.

    What Is Vibe Coding?

    Vibe coding focuses on coding through prompts, not direct code.

    Key aspects:

    • Tools: Windsurf, Cursor, Claude Code, Replit, Lovable, ChatGPT, Gemini.
    • Language as Code: Developers write prompts and detailed instructions.
    • Planning: Start with a written plan (scope, architecture, features).
    • Modular Build: Implement step by step, not all at once.
    • Version Control: Commit often with Git to avoid AI mistakes.
    • Testing: Use integration tests to guide AI and catch regressions.
    • Bug Handling: Easier to regenerate code than debug manually.
    • Security/Refactor: Use rules, keep files small, refactor often.
    • Engineer’s Role: More product-focused, judge quality, think systems.
    • Learning Tool: LLMs can explain code and speed up learning.

    The Vibe Coding Workflow and Development Process

    1. Planning and Preparation (Spending “Unreasonable Amount of Time”)

    Before writing any code, spend significant time planning and setting boundaries for the AI:

    • Select Tools: Pick an AI coding assistant. Tools like Windsurf and Cursor (often forks of VS Code) can be loaded simultaneously on the same project, allowing developers to generate slightly different iterations of code and pick the one they prefer.
    • Define Scope and Architecture: The first step is not to dive in and write code. Instead, work with a pure LLM (separate from the coding tool initially) to set project boundaries and structure.
    • Create a Comprehensive Plan (PRD): Work with the LLM to write a detailed, comprehensive plan and put it in a markdown file inside the project folder. This plan should define features, potential edge cases, and architecture.
    • Trim Scope: Go through the draft plan, deleting unwanted features, marking certain features as explicitly “won’t do” (too complicated), and keeping a section for ideas for later (out of scope for now).
    • Write Detailed Instructions/Rules: Write a step-by-step to-do list (to-do.md) from the comprehensive plan for the AI coding agent.
    • Documentation Access: Download relevant API docs into a local folder so the LLM can reference them, instructing it to “go and read the docs” before coding.
    • Version Control: Install and use Git religiously. The AI can help initialize the Git repository (e.g., git init) and set up secure code storage on platforms like GitHub.

    2. Implementation and Iteration

    The implementation phase is iterative and modular, focusing on small, manageable chunks:

    • Section-by-Section Implementation: Do not try to “oneshot the whole thing”. Work with the LLM to implement the plan section by section. Explicitly tell the LLM which section to implement next.
    • Provide Detailed Context: Because you are “programming with language,” you must provide the necessary context and information in a very detailed way to get good results.
    • Use Multiple Tools: Load tools like Cursor and Windsurf on the same project simultaneously. Give the same context to both, and they will both give you slightly different iterations of the code, allowing you to pick the one you like better.

    3. Verification, Testing, and Version Control

    After implementing a feature, thorough testing and saving are essential to maintain code stability:

    • Start with Tests (Guard Rails): Begin by handcrafting test cases yourself, without LLMs. These tests act as strong guard rails that the AI must follow when generating code.
    • High-Level Integration Tests: Keep tests super high level (integration tests) to simulate a user clicking through the site. These are crucial because LLMs have a bad habit of making unnecessary changes to unrelated logic. This helps catch issues early.
    • Commit Religiously: Use Git religiously and make sure you are starting with a clean Git slate before starting a new feature. Once your tests pass and you see those green flags, commit immediately.
    • Revert Capability: Committing frequently ensures you can revert to a known working version if the AI “goes off on a vision quest” or if things go wrong on the next step.

    4. Handling Bugs and Code Quality

    The approach to debugging leverages the low cost of code regeneration:

    • Simple Bug Fixes: For minor issues, copy-pasting the error message (from server logs or browser console) into the LLM is often enough for the AI to fix the problem..
    • Complex Bugs (The Reroll Strategy): If the LLM falls into a rabbit hole, keeps regenerating code, or produces “funky” code. The preferred strategy is to ignore the bug and tell it to try again from scratch.
    • Avoid Accumulating Crust: Don’t keep prompting the AI to fix a bug on top of bad code—it creates “layers and layers of bad code.” For complex bugs, reset all changes and feed the LLM specific instructions on a clean codebase.
    • Rollback: If the code becomes unfixable, use the Git history to roll back to a previous stable commit and start the implementation attempt over.
    • Refactor Frequently: Once the code works and tests pass, refactor often. Ask the LLM to spot repetitive code, and keep files small and modular.
    • Complex Features: For tricky features, build a small reference implementation in a clean project first. Then point the LLM at it and have it reimplement the feature inside your larger codebase.

    Which coding language is recommended?

    • JavaScript – most popular language worldwide
    • Python – the go-to for AI development
    • Suggested stackPython backend, HTML + JavaScript frontend

    Primary AI Coding Agents

    • Cursor
      • Faster than Windsurf.
      • Good for front-end and light full-stack tasks.
      • Can run alongside Windsurf on the same project.
      • Needs detailed instructions (“cursor rules”).
    • Windsurf
      • Slower, “thinks longer” than Cursor.
      • Can run alongside Cursor.
      • Devs often wait while it processes tasks.
      • Needs detailed instructions (“windsurf rules”).
    • Claude Code
      • Best for devs with prior coding experience.
      • Claude Sonet 3.7 excels at implementing code changes.
      • Also used for DevOps (DNS setup, Heroku hosting).

    General Purpose LLMs & UI Tools

    • Replit
      • For beginners, no coding experience needed.
      • Easy visual interface.
      • Great for testing new UIs in code.
    • Lovable
      • Also beginner-friendly with visual interface.
      • Good for UI generation.
      • Weaker on backend logic modifications.
    • Pure LLMs (Claude, ChatGPT, Gemini)
      • Used first for scope and architecture planning.
      • Can solve issues when coding tools get stuck.
      • Gemini: best for indexing codebases and plans.
      • Claude Sonet 3.7: best for implementing code.
      • ChatGPT: helpful for non-coding (e.g., favicon images).
    • GPT-4.1
      • Less effective.
      • Asks too many questions, often mis-implements.

    Sources