logoalt Hacker News

michaelttoday at 1:37 PM2 repliesview on HN

The most important thing to keep in mind, when considering AI images for helping to illustrate or explain the actual content, is that AI-generated images have a big trust problem.

Take a look at the Google Image Search results for 'Engine Diagram' https://www.google.com/search?q=Engine+Diagram&tbm=isch

In the first row I get two correct-looking diagrams, then a load of AI-generated ones. Three cylinder heads for four cylinders? Two crankshafts? Oil pan labelled Crankshaft? Oil pan labelled Connect in rod? A four-cylinder engine with seven valve springs? Parts labelled up to 39 but a 9-item key? Spark plug wires that loop back on themselves? A crank shaft where the pistons aren't offset in phase? Four-cylinder engines whose exhaust manifolds have three or five openings? Then in the second row, I get "Parts of a V6 engine" showing a four-cylinder engine - with an 'Exhaust malvol', an 'extaust manivol', an 'exsoust manivol' an 'oilolaivt manivol'

Savvy technical audiences have noticed this - and so when a diagram has a whiff of AI about it, they become extremely skeptical and distracted.

Personally I only use AI-generated diagrams very sparingly, and very carefully.


Replies

voakbasdatoday at 1:40 PM

To be fair, the problems you describe existed before AI, though I concede it has gotten worse.

What baffles me is why anyone would think it a good idea to post and host these images? What’s that upside?

show 3 replies
PunchyHamstertoday at 1:55 PM

Diagram-wise I had better luck in telling it to make a text version for diagram generator, not only AI edits tend to be more correct, it's easier to fix any errors too.

As a bonus you can then prompt AI to validate whether the diagram matches article and vice versa, I've caught some small bugs like that when we migrated our docs

show 1 reply