I didn't read the article because I'm not interested in crypto, but I love "Move deliberately and Fix things."
I love that it implies that you know where you are going and making steady progress towards that. It also subtly acknowledges that you are building on the work of others, and that bugs happen. It's OK, but fix 'em when you find 'em.
There's a lot of reasonable reasons to dislike cryptocurrencies, and I say that as someone who's all-in on them. It's kind of like atheism in 1750's Europe -- it makes perfect sense on its own terms, but it threatens to upend a seemingly critical social governance mechanism.
There are also serious technical flaws, but I think there's a good chance those can be addressed.
A thousand times this. I don't mind if they mine crypto in Iceland or Quebec where they have 100% renewables but a lot of crypto mining is done using coal. In my opinion, fixing our planet should have a higher priority than inventing a new currency. If they'd at least use the money from BTC to fish plastic from the oceans I'd be fine, but currently it's just benefiting some large mining operations and hardware manufacturers.
IDK, we've had "money over IP" with cryptographic signatures for decades already in various financial exchange protocols, with the main difference from Bitcoin being the requirement of pre-existing trust relationships.
However, since the vast majority of people and institutions do have some pre-existing trust relationships, Bitcoin doesn't bring that much to the table, we already had the technology to wire money worldwide.
Writing your own transaction messages and injecting them for execution to whatever banks hold your money is a standard, widely used product of classical banking, not some novelty. Ages old cash management services and accounting system integrations run off of that ability. It's not P2P, but it remains to be seen if P2P by itself is a worthwhile benefit.
You still need an agent in classical banking for that transaction, even if the agent is just the bank's server.
I'm my own agent and an international network is the bank. Classical banking can't compete with that in the long run though I'm sure they'll still be of use.
Can you elaborate why exactly can't that compete in the long run?
I'm sure that there are multiple niche use cases where being your own agent has some benefits and it will certainly be of some use, but it seems that for the mainstream usage it does not, and there are certainly all kinds of practical advantages for some centralization and delegation of tasks to another agent, so it seems quite plausible to me that the classical banking might dominate the majority of transactions forever.
> I doubt anyone would ever launch a war funded on Bitcoin.
Why do you think that? You can store a lot of bitcoins on a single sheet of paper (private keys for wallets) so stealing it is a lot easier than precious metals. If any large nation ever really starts disliking BTC they'll just launch targeted operations to get hold of a large share of Bitcoins and destabilise the system. Similar to earlier times where enemy states printed fake money to destabilise monetary systems, bitcoin makes it easier because you don't need to move physical assets.
The dollar's value derives, in great part, from the existence of the US military. It uses far more energy per year than Bitcoin does.
And...
Genuine economic activity in crypto-currencies represents roughly %0.00000000000000000000001 of the economic activity transacted in dollars. How much energy would be required for crypto-currencies in a one to one comparison?
Let's not forget the US military may in fact serve some other functions as well.
I have seen plenty of people ignore articles on HN and make it to the top. The comments are complaining about how conservatives are censored on HN, never with a sense of irony.
Isnt it hilarious to see this being touted as some new and insightful way of developing a product? CS undergrads should be forced to learn about how bridges, skyscrapers, and airliners get built.
I actually think the curriculum works directly against this. I know my homework assignments tended to be much more unmaintainable than even a one-off python script that I would hack together. It might be interesting to design a class where, instead of weekly homework, students are required to continually maintain/modify the same source over a semester. Weekly projects that will never be touched again actively discourage writing maintainable code, and I don't think that is a good lesson to be teaching.
I recall reading about a teaching system where homework involved taking submissions of previous year's students and adding features on top of that, providing students with all kinds of practical insights on what makes code easy or hard to maintain.
It depends on the context. Facebook's cavalier, exploratory attitude mostly worked because they were building an entertainment. Software development tends to be a lot more cautious in domains like finance, where errors can cause serious, actionable damage.
I love that it implies that you know where you are going and making steady progress towards that. It also subtly acknowledges that you are building on the work of others, and that bugs happen. It's OK, but fix 'em when you find 'em.