Comment by robbies
I know enough people at Apple who are at the mercy of the overlord design teams, and it sounds exactly like what you described
I know enough people at Apple who are at the mercy of the overlord design teams, and it sounds exactly like what you described
Apple designers used to build interactive demos in Macromedia Director, so I'm assuming they knew a bit about scripting. That probably helped them think in a way that really clicks with software development.
I've worked with some younger designers who couldn't even put together a consistent click-dummy once the client wanted to see flows outside the happy path. To be fair, all they really had to go on was their education and Figma's panels.
This is a pretty discriminatory comment that I’ve honestly seen zero hint of in reality. And this is coming from someone who didn't go to a particularly prestigious school. I honestly rarely even find out what school my colleagues went to school. But the ones I know who did go to those prestigious schools are beyond humble.
Not really. That's bad faith. I've worked at lots of places, probably hired about 200 engineers over my career so far and have noticed this pattern.
I stopped looking at the educational background years ago in a fear that it would influence my bias either way. We shouldn't base someone's suitability at 40 upon what opportunities they were afforded at 17.
I do have a somewhat prestigious pedigree btw. I removed it from my resume around 2010 and never looked back
I've met some great designers as well. They usually come from more modest backgrounds.
It's kinda the rule for programmes too.
The ones that went to a small liberal arts school you've never heard of programming as their second career are usually more effective to work with then the Stanford/MIT crowd.
The problems start I think, when you have an expectation that your collaborators are somehow either superhuman or subhuman and not peers.
Humility and mutual respect gets things done.