2 ms·

This seems to just re-enforce that he was an ideas man. I've yet to hear a story where Jobs was the one who discovered the fix, only stories that he pointed ou

This seems to just re-enforce that he was an ideas man. I've yet to hear a story where Jobs was the one who discovered the fix, only stories that he pointed out the things that needed to be fixed. He's lauded as a visionary, not as an engineer. And all the stories about him are about him pushing others to realize his vision. Edit: Lots of people seem to disagree with me, but then pointing out how he was an extremely skilled ideas man. Perhaps that term has too much negative connotation for Jobs' visions (ideas) to be associated with?

kevinmchugh 3y ago
Nobody's claiming that he was a programmer. From what I've read, though, he had a very keen sense of design and product. Here's an anecdote: https://www.folklore.org/Calculator_Construction_Set.html https://www.folklore.org/Calculator_Construction_Set.html I think "ideas guy" doesn't capture this. He had big ideas but also was super particular about details. (Which doesn't justify being a prick, to be certain)
jdgoesmarching 3y ago
Maybe the lines are more blurry, but design, marketing, and product are not just “ideas.” I’m not going to weigh in on what Steve contributed, but it’s perfectly plausible that he did so without writing code or holding a soldering iron. Not to say ideas guys aren’t prevalent, but for all his faults I would argue that Jobs wasn’t one of them.
bdw5204 3y ago
Being able to point out the right things that need to be fixed is an important skill. Most people can tell when something is off about a product but can't tell you exactly what it is. You can easily identify the wrong thing as the problem then end up trying to hide a symptom instead of fixing the problem. Medicine is notorious for treating symptoms when the underlying problem is usually related to something else like diet or (lack of) exercise. You can also completely fail to identify an obvious problem such as the games where you end up stuck and having to Google how to progress because the game is poorly designed. This poor design isn't going to be obvious to anybody working on the game every day because they designed and already know the solution but it would come up if somebody else played the game and got stuck.
- Workaccount2 3y ago
  I'm not saying that it's not an important skill. I am saying it's not a technical skill. Realizing that the iPod had to be thinner was a visionary idea. Making the iPod thinner was a technical feat. One had the idea, the other had the technical ability (even if they had given up before Jobs pushed them harder).
ecshafer 3y ago
I used to think very similar to you, I mean Woz was the engineer! Jobs didn't build or design the ipod. But I have since worked with product managers, both good and bad. I have worked in companies and on products with a good vision and a poor vision. Being able to get a good idea for a product, envision that product, and guide people through the whole process of building that product and keeping that vision through everything is very difficult and is a useful skill.

kevinmchugh 3y ago

Nobody's claiming that he was a programmer. From what I've read, though, he had a very keen sense of design and product. Here's an anecdote: https://www.folklore.org/Calculator_Construction_Set.html https://www.folklore.org/Calculator_Construction_Set.html I think "ideas guy" doesn't capture this. He had big ideas but also was super particular about details. (Which doesn't justify being a prick, to be certain)

jdgoesmarching 3y ago

Maybe the lines are more blurry, but design, marketing, and product are not just “ideas.” I’m not going to weigh in on what Steve contributed, but it’s perfectly plausible that he did so without writing code or holding a soldering iron. Not to say ideas guys aren’t prevalent, but for all his faults I would argue that Jobs wasn’t one of them.

bdw5204 3y ago

Being able to point out the right things that need to be fixed is an important skill. Most people can tell when something is off about a product but can't tell you exactly what it is. You can easily identify the wrong thing as the problem then end up trying to hide a symptom instead of fixing the problem. Medicine is notorious for treating symptoms when the underlying problem is usually related to something else like diet or (lack of) exercise. You can also completely fail to identify an obvious problem such as the games where you end up stuck and having to Google how to progress because the game is poorly designed. This poor design isn't going to be obvious to anybody working on the game every day because they designed and already know the solution but it would come up if somebody else played the game and got stuck.

Workaccount2 3y ago
I'm not saying that it's not an important skill. I am saying it's not a technical skill. Realizing that the iPod had to be thinner was a visionary idea. Making the iPod thinner was a technical feat. One had the idea, the other had the technical ability (even if they had given up before Jobs pushed them harder).

ecshafer 3y ago

I used to think very similar to you, I mean Woz was the engineer! Jobs didn't build or design the ipod. But I have since worked with product managers, both good and bad. I have worked in companies and on products with a good vision and a poor vision. Being able to get a good idea for a product, envision that product, and guide people through the whole process of building that product and keeping that vision through everything is very difficult and is a useful skill.