More functionality based stuff, but both form and function. I don't want to be a photoshop expert (yet)
Well in that case I'd ask you the following questions:
"Are you lazy?"
"Do you have common sense?"
If your answer is "YES!" then you don't need a course. The design of the program you'll write will be that of simplicity and ease of use because you're lazy and have common sense to not make it too complicated
I've seen a guy write something as simple as a webserver "pinger" to check if his servers are online (he administrated several hundred)
Now instead of just having the program load from a CSV and then checking and saving the results. He had this elaborate system where you have to create a list of servers (you just imported anyway) you'd like to check and give it a name and description for this "subset" and then get the program to check this subset and report back to you (which is just a printout of the grid he had on there)
And I'm like... "File...Import...Start Checking"
3 or 4 clicks and you're checking several hundred servers... he takes half an hour to an hour setting up all his subsets before he can commence checking...
ANYWAY... you learn a lot if you're directly involved with customers as well. Especially hearing their idiotic ideas of how they think the system can function better in terms of UI, and then hearing their "oh" when I tell them why it's been done like it has and how much faster it is anyway because of it
