惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
Recent Announcements
Recent Announcements
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Stack Overflow Blog
Stack Overflow Blog
J
Java Code Geeks
Microsoft Azure Blog
Microsoft Azure Blog
罗磊的独立博客
博客园 - 【当耐特】
H
Help Net Security
腾讯CDC
大猫的无限游戏
大猫的无限游戏
GbyAI
GbyAI
Last Week in AI
Last Week in AI
Jina AI
Jina AI
博客园 - 聂微东
Blog — PlanetScale
Blog — PlanetScale
A
About on SuperTechFans
Apple Machine Learning Research
Apple Machine Learning Research
P
Proofpoint News Feed
Y
Y Combinator Blog
C
Check Point Blog
博客园 - 司徒正美
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Thought My One Sentence Is Creating a Perfect GPT Image...
Cathy Lai · 2026-05-26 · via DEV Community

When I first started experimenting with GPT image generation for my Garden Visualizer project, I honestly thought the workflow would be simple:

  1. Upload image
  2. Write one good prompt
  3. Receive perfect result

A prompt like:

“Add low-maintenance shrubs to this Auckland backyard.”

And it works?

Not exactly!…

After weeks of experimenting with ChatGPT app with staging photos, gardens, landscaping concepts, and “future visualizations”, I slowly realized something surprising:

The impressive results I was getting were not coming from a single prompt at all. They were coming from hidden context that ChatGPT had been accumulating throughout the conversation.

The Strange Thing I Noticed

At some point, I could type something incredibly vague like:

“Show after 3 years.”

…and GPT somehow knew:

  • Which shrubs I meant
  • Where the lemon tree it was
  • That I disliked overcrowded gardens
  • That I preferred realistic suburban styling
  • That I wanted sparse planting
  • That I preferred low-maintenance layouts

That was the moment I realized: The “prompt” was not the whole product. The conversation itself had become part of the generation engine.

My Wrong Assumption About the Image Edit API

Initially, I assumed the Image Edit API worked similarly to ChatGPT conversations.

I thought:

  • the model would somehow “remember”
  • the AI would learn over time
  • previous generations would influence future ones automatically

But API calls are usually stateless - which means every request is effectively isolated unless you manually resend the context.

So this:

{
  "users_image": "messy_backyard.jpg",
  "prompt": "plz generate a nicely layout idea for this garden"
}

…actually contains almost no useful information.

The model has no idea:

  • How dense should be the plants
  • What realism level
  • What maintenance standard
  • What climate
  • What style direction
  • Budget constraints

The API is not “remembering”. MY app has to carry the memory.

How About Using Reference Images?

Then I got curious. Instead sending the original image and a pure text prompt, what if I also include example images I liked?

Suddenly the AI had a visual target. Not exact copying — but guidance. The reference image could influence:

  • density
  • lighting mood
  • realism
  • staging style
  • color palette
  • suburban vs luxury feel

And honestly, this may become one of the most important patterns in AI apps going forward.

Not:

“Here is my magic prompt.”

But:

“Here is the style, taste, realism, and emotional direction I want you to follow.”

Final Thought

I started this project thinking:

“The better the prompt, the better the image.”

Now I think a more accurate statement is:

“The better the accumulated context, the better the direction.”

And that subtle difference completely changed how I think about building AI products.