That's true, but I think that's what a lot of people think it is.

I'm also a software dev. I wouldn't say, when designing code, that "I make the code look nice" though, I'd hope that's at least part of it.

However... when someone is looking for a "designer," while it does include UI/UX (again, whatever that is ;) ) I've found they strictly only want someone who is good at making pretty things in Photoshop.

I think your post could do with some bullet points about what design is.

You're right.

The process of making form follow function, maybe?

Definition of design: a plan or drawing produced to show the look and function or workings of a building, garment, or other object before it is built or made.

So, I guess "web designer" is very similar to "make it in Photoshop" and I should stop complaining ;)

I'd say that definition defines the outcome of design, not design itself. I focused on the "process" deliberately, because most design work happens outside whatever tool you use to externalize your plan/vision.

It's reductive to conceive design as the design outcome, IMHO. If you have a guy doing all the UX work (alignment with business needs, research, gather data, analysis, IA, brand identity integration, etc.) and other guy which takes all this work and produces UI mock-ups in Photoshop, who did most design work?