[josh2600]

I hate this language of “so and so isn’t a technologist”. You don’t need to understand how a compiler works or grok segfaults to see the future.

It’s obvious if you’re running a big data center yourself that you’d rather pay someone else to do that, it’s just that no one wanted to take on that operational burden because it’s a pain. It doesn’t take a technologist to realize that arbitraging pain is where you make money. Everything after that is execution.

There are plenty of people who see the future who aren’t coders, they just usually can’t execute.

[whoisjuan]

I disagree with this. The vision wasn't a simple economic statement on why "we should rent out our unused server capacity". It was vastly more complex than that. It included technical details on how it should be approached and how to leverage and scale their existing infrastructure. It also laid down the ground for EC2 and S3 as foundational services.

Perhaps my error was saying that Jassy isn't a technologist. He is 100% a technologist and has an incredible ability to absorb and understand very complex technical topics. He just isn't a technologist by training or by trade. He simply has an innate technical ability to such extent that his first job at Amazon was being a technical liaison to Jeff Bezos.

[StreamBright]

Also VPC networking + patents show how advanced these guys are.

[bobl]

I think the confusion is largely between computer science, information systems, system sciences and management. Which are overlapping fields, but not necessarily practiced as such.

[scottlocklin]

Yeah, but it's hard to identify those people until their useful business lifespan is half over. Technologists are at least assumed to have some idea of the possibilities; plenty of "visionaries" come up with unworkable visions that we conveniently forget about in hindsight, because they were bad visions of the future.