DEV Community: zhouhua xiao

Before You Rewrite the Prompt, Check the Photo

zhouhua xiao — Tue, 08 Sep 2026 12:07:04 +0000

Picture this: you want AI to give your bathroom a new look. Your prompt reads like a dissertation, but the result seems to come from a parallel universe.
Before adding an eighteenth “premium, elegant, realistic,” look at the input photo. Towels hide the vanity, only a corner of the floor is visible, and the mirror is trying to reflect the entire world.
It’s a little like filing a bug report that says “it’s broken.” Even a capable assistant needs enough context to work with.

AI-generated conceptual illustration of an input problem.
Give the model a photo that explains the room
AI Bathroom Designs uses bathroom photos to generate visual concepts in different styles, helping you compare tile, vanity finishes, and color palettes. With tools like this, the photo is part of the brief.
Before taking it, try four small adjustments:

Show the space. Shoot from a suitable position, such as the doorway, and try to include the floor, vanity, shower, and wall boundaries.
Make the light useful. Avoid a bright window turning the rest of the room into a silhouette. Keep the main areas visible.
Reduce obstructions. Move towels and clutter that cover fixtures. Check the mirror for people or personal items, too.
Watch the perspective. Keep the camera reasonably level and avoid obvious distortion just to fit everything into the shot. You don’t need a real-estate advertisement. You need a picture that helps someone understand the room. Treat redesigning as a small experiment Once you have a suitable photo, keep it fixed and ask one clear design question at a time. For example: “Do I prefer warm walls or cooler tones?” Focus on color in that round and materials in the next. Generated concepts may still alter several details, so keep the original alongside each result and check whether the changes match your intention. If you change the camera angle, style, floor, and lighting all at once, it becomes hard to explain which change you actually liked. It’s like adjusting ten variables while debugging: you have an outcome, but you’ve lost the explanation.

AI-generated conceptual illustration of a photo-taking approach.
A small UX idea for AI product developers
A specific sentence beside the upload field may be worth testing before you write a long prompting tutorial.
Consider a clear preview, a reminder to include major fixtures and the floor, and a way to state what should change and what should stay. These are interaction ideas to evaluate, not claims that the website implements every suggestion.
A successful upload tells you the transfer worked. Whether the input provides enough information is a separate question.
Next time, start with another photo
For a practical starting point, read the bathroom photography guide, then use your own photo to compare design directions.
A clearer photo still doesn’t guarantee accurate dimensions or a perfectly preserved layout. It gives the process a clearer input; the output still needs checking.
If you build image-based AI features, what one reminder would you put beside the upload button?

Your Tool Collection Is Growing. Your Project Folder Is Still Empty

zhouhua xiao — Tue, 08 Sep 2026 04:43:30 +0000

Picture this: you need one handy AI tool to save some time on your weekend project.
Soon, your browser is throwing a party. One tool promises to write your code. Another will build your website. A third sounds ready to take your job on Monday. Your coffee is cold, your bookmarks are full, and your project folder is still empty.
When did choosing tools become another job?

Start with the job you need done
You don’t need a dragon-slaying sword to chop an onion. Software shopping works the same way.
Are you fixing an error, sorting through a few documents, or building a landing page that actually opens? A specific task makes it easier to separate useful features from landing-page confetti.
MakerJury is a software and AI tool discovery site with evidence-led reviews. It brings together product information, test procedures, and limitations so you can judge whether a tool fits your work.
It also distinguishes listings from tested products: being listed doesn’t mean a tool has been reviewed, and scores appear only after a documented test.
Give your shortlist a tiny audition
You don’t have to start with “build me a billion-dollar company.” Ask three smaller questions:

What can it finish? Give it a concrete task, such as fixing a reproducible bug.
How can I check the result? Does the code run? Can I find the cited source? Does the exported file open?
How much cleanup is left for me? What needs manual editing? Is there a paywall? Does it disrupt my existing workflow? The demo gets you excited. The audition tells you whether you can work together.

Read the test, not just the score
For example, MakerJury’s three-task Cursor review separates bug fixing, feature work, and refactoring. It identifies the small public codebase used for testing and explains why those results cannot establish performance on production projects.
That gives you more to work with than “Amazing. Must buy.” You can ask: does this resemble my problem, and what do I still need to verify?
Give yourself a stopping rule, too. If the tool completes the task, the result is checkable, and the cost works for you, start using it. Don’t hand your entire weekend to a comparison spreadsheet while searching for the perfect option.
Before your next software shopping spree, browse MakerJury’s reviews, then try a candidate on your own task.
Your bookmark collection can keep growing. Your project deserves a turn.
What’s one tool you bookmarked thinking “I’ll use this immediately” and then never opened again?

How to Remove GPS Metadata from Photos and Verify the Result

zhouhua xiao — Tue, 08 Sep 2026 03:24:59 +0000

A photo can reveal more than what appears in the frame.
Depending on the device, camera settings, and export process, the file may contain GPS coordinates, a capture timestamp, camera details, or editing information. None of those fields need to be visible when you open the image.
Before publishing a photo in a blog post, attaching it to a public issue, or adding it to a marketplace listing, it is worth checking the actual file you are about to share.
Disclosure: I run MetadataRemover.ai. This article explains the workflow and includes an independent way to inspect the result.
What should you check?
GPS coordinates are commonly stored inside EXIF metadata, alongside fields such as camera make, model, and capture time.
However, EXIF is only one part of the picture. Depending on the format and the applications that touched the file, other information may appear in XMP, IPTC, or image text chunks.
Useful fields to review include:

GPS coordinates and altitude.
Original capture date and time.
Camera model and device identifiers, where present.
Author, description, and editing-software fields. Not every image contains these fields. Inspect the file instead of assuming they are present—or already gone. A browser workflow: inspect, remove, verify For a local browser workflow, you can use the EXIF remover. The current image tool supports JPG, PNG, and WebP files up to 25 MB each. Inspection, cleaning, and output verification happen locally in the browser; the image file does not need to be uploaded to the service. The steps are:
Keep an untouched original for your own archive.
Select the final exported image you intend to share.
Review the detected metadata groups.
Choose Privacy Safe, or use Custom to select supported groups for removal.
Download the cleaned copy and inspect it before publishing. Check the final export, not just the original photo. An editor or conversion step can preserve existing metadata or add new fields. Also, make sure you share the downloaded copy rather than accidentally selecting the original again. Verify the downloaded file with ExifTool The tool checks its generated output, but a second metadata reader provides an additional check. If you have ExifTool installed, run these read-only commands with your own filenames: exiftool -a -G1 -s original.jpg exiftool -a -G1 -s cleaned.jpg The options show duplicate tags, include group names, and use short tag names, making the output easier to compare. Review the fields you intended to remove. Pay attention to GPS entries and any relevant EXIF, XMP, or IPTC fields. Do not expect the cleaned file to produce empty output. ExifTool can still report file-system information, image dimensions, compression details, and other properties. A file modification timestamp is different from an embedded original capture timestamp. The useful question is whether the targeted embedded fields remain within the reader’s supported coverage. Open the image as well. Metadata inspection does not tell you whether its appearance still meets your needs. Two details developers should watch EXIF Orientation affects how an image displays. Some photos store pixels in one orientation and rely on an EXIF value to display them correctly. Removing that value without handling the pixel orientation can produce a sideways image. Normalizing the orientation may require re-encoding, so “remove metadata” should not automatically be described as “always lossless.” ICC profiles affect color rendering. They have a different purpose from GPS coordinates or author fields. Preserving a color profile does not mean privacy cleanup failed. These are reasons to use a deliberate cleanup policy and check rotation, color, and dimensions afterward. Know the limits Metadata removal does not hide an address visible on a package, a reflection, or a recognizable landmark. It also does not remove pixel-level invisible watermarks or erase copies previously uploaded elsewhere. Some platforms strip metadata during processing, but behavior can differ between upload methods and downloaded versions. Checking before upload gives you control over the file that leaves your device. For an image-sharing workflow, a useful sequence is: Export → inspect → remove selected metadata → verify → publish. If you work on an upload or publishing pipeline, where do you handle metadata checks: in the browser, on the server, or both?