Answers to this question are constantly posted on this forum and on Reddit by people who are not software engineers/developers, nor product managers. Either that or they are truly terrible at their jobs. Reddit in particular has really turned into a garbage dump, but that's something for another discussion.
Anyway, in a business context you want to build software that meets your customer's expectations, so understanding how a user makes use of your software solution is really important for smooth communication and shared understanding between management, marketing and engineering. Normally you want to write out really detailed user stories/journeys, maybe even draw diagrams or create mock-ups that demonstrate the exact problem you're trying to solve and how your thing will solve it.
Here's a teaser:
Alice is at a farmer's market and wants to buy broccoli from a vendor. How does she pay?
Here are just a few important details that we need to know first:
- What country is Alice in, and what are the economic conditions?
- How much money does she make every year/how well off is she?
- How technologically sophisticated is she/how old is she?
- What tastes and preferences does Alice have/what prejudices her in certain ways?
We need a lot more information before we start talking about what BIP we can code up in a day. If you think about these questions only from your own perspective and experience, you're discounting the majority of people on this planet that want to use the same technology. Bitcoin's value depends mainly on how many people can safely use it, and if it's not in use by the largest number of people possible, it will not achieve it's full potential/value.
The correct answer to the question in this poll is "it depends". Bitcoin is for humans, and humans have different needs. Most likely every redditor and bitcoin.org poster's favorite potential use case, "in-person payments at high volume merchants", will not be satisfied by Bitcoin directly. Use something else for that one narrow use case if Bitcoin isn't doing it for you, and support the engineers who are working to make Bitcoin more secure and stable, goddamnit
Both of them, I think because we can use Bitcoin for both of purposes of Gold and cash. Bitcoin is really usefull for my life. Anyway, in a business context you want to build software that meets your customer's expectations, so understanding how a user makes use of your software solution is really important for smooth communication and shared understanding between management, marketing and engineering. Normally you want to write out really detailed user stories/journeys, maybe even draw diagrams or create mock-ups that demonstrate the exact problem you're trying to solve and how your thing will solve it.
Here's a teaser:
Alice is at a farmer's market and wants to buy broccoli from a vendor. How does she pay?
Here are just a few important details that we need to know first:
- What country is Alice in, and what are the economic conditions?
- How much money does she make every year/how well off is she?
- How technologically sophisticated is she/how old is she?
- What tastes and preferences does Alice have/what prejudices her in certain ways?
We need a lot more information before we start talking about what BIP we can code up in a day. If you think about these questions only from your own perspective and experience, you're discounting the majority of people on this planet that want to use the same technology. Bitcoin's value depends mainly on how many people can safely use it, and if it's not in use by the largest number of people possible, it will not achieve it's full potential/value.
The correct answer to the question in this poll is "it depends". Bitcoin is for humans, and humans have different needs. Most likely every redditor and bitcoin.org poster's favorite potential use case, "in-person payments at high volume merchants", will not be satisfied by Bitcoin directly. Use something else for that one narrow use case if Bitcoin isn't doing it for you, and support the engineers who are working to make Bitcoin more secure and stable, goddamnit
