reading “After Steve” (I know, I know…)
The book is painting Tim Cook in a poor light, but also, damn Jony Ive stop being so whiny. Like I get that this is a fictionalized account but the idea of a designer bristling when an engineer has concerns over some wild idea is just… it hits a little close to home 😅
reading “After Steve” (I know, I know…)
I’ve always said this but Apple getting rid of Scott Forestall was a huge mistake. Both a computer nerd and a theatre nerd, what a powerful high school energy.
reading “After Steve” (I know, I know…)
@ashfurrow Perpetual problem at one job, designer would propose not-plausible things, I'd push back with a few realistic options, designer was OK with this, but then the overprotective manager's assistant (not actually my manager) would freak out, try to make me only do what the designer drew. It was like a cult but less welcoming.
reading “After Steve” (I know, I know…)
@mdhughes that sucks!
reading “After Steve” (I know, I know…)
@ashfurrow Speaking as someone who has worn both hats, a design conceived in vacuum is never a good idea, and no matter how many engineers you throw at it afterwards, it will show. Design needs to be secondary to requirements and physical reality, always, with no exceptions, and fuck postmodernists.
reading “After Steve” (I know, I know…)
@ashfurrow he must have a huge ego to have refused to die in shame after the esc key fiasco
reading “After Steve” (I know, I know…)
Designers I’ve worked with sometimes conceive of ideas totally in a vacuum, unconcerned with the practicalities of making their design into a working product. When I voiced concerns, some designers get really defensive.
Good designers will work with me to understand the constraints. Their designs are a North Star, a platonic ideal that we aim for together – even though we know we will fall short.
But what do I know! I’m just a lowly software engineer 🤷♂️