2 ms·
> Honestly, I think being "tech savvy" is a liability. Someone who doesn't think they're tech savvy knows they don't know. It takes a certain level of expertise
by notahacker 7y ago
> Honestly, I think being "tech savvy" is a liability. Someone who doesn't think they're tech savvy knows they don't know. It takes a certain level of expertise to talk yourself into something extremely dumb. They might not fall for this particular pitch deck (or the one I overheard), but there are scams for every skill level. And the more confident you are in your understanding, the larger the "investment" you will being willing to make.
Blockchain's probably the prime example of that. Understand a potential real world use case and you can probably identify the extent to which mutability of records loses value, and pay someone to audit the code if the real problem is that centralisation is impractical and stakeholders can benefit from manipulating the records without having any incentive to modify the physical product. If your fundamental understanding of a business model convinces you the real business problem is mutability of records, you can hire someone skilled to evaluate whether the codebase is likely to fix that. More difficult if your starting point is that the code and team certainly deliver on promises and the only problem that needs due diligence is everything else about why people would ever use it.
On the other hand, outside the VC world there are a lot of people in corporates who broadly understand use cases but don't have an in-depth knowledge of the tech whose job depends on saying yes to enough innovation initiatives
- Bartweiss 7y ago> outside the VC world there are a lot of people in corporates who broadly understand use cases but don't have an in-depth knowledge of the tech whose job depends on saying yes to enough innovation initiatives Both inside and outside the VC world, I think. You make an extremely good point about use cases: you don't have to be an expert on the tech to avoid scams as long as you're an expert on the problem it's being used for. If you can say "but we have a trusted source and we want to fix mistakes in old records, wouldn't a database be better?", you're past 90% of blockchain puffery. But if you have to say "what if there's a trusted source?", you can still get snowed by talk about all the hypothetical ways that could fail to apply. If you're picking tech someone else will use, or investing in products you think the market will value, you can't rely on knowing the problem in detail. It's like the difference between a beta tester saying "can I buy this?" and saying "I'll bet tons of people will buy this". The first tells you what they think about the product, the second other just tells you what they think about other people.