Fair. So in a sense, the lidar vs camera argument ultimately can be publicly assess/proven through human babysitter (regulation permit) and accident rates. or maybe user adoptions.
It's still possible in the case of Digital Ocean vs AWS: 5-10x price reduction, focus on a subset of core service. You still need to deliver friction-less service in the beginning, reliability and customer service eventually.
Not all will move from AWS, but the price saving is significant for small players who doesn't need the full suite of AWS.
- I don't think "stuck in my room for 6 months keep trying to find "the right one"" is a good idea. Please change your plan/approach.
- Since money is not an issue, we can cross out the need to get a job to make ends meet and start thinking about fun things to do.
- I believe Idea is not a light-bulb moment after meditation for 6 months in your room; it sort of require you try doing different things in order to bump into the light-bulb moment.
More random advices:
- Do u like Hardware or Software? Assuming you are into tech ideas.
- Unless you have partners and funding, the scope of your project need to be within your own capabilities in order to reach mediocre success in terms of user adoptions.
- You don't need the best idea, just good enuf idea which interest you. Why passion/interest in important? So that you will work on it even though there is no money and users for 6 months, and you use/like your own product.
- Discipline. Build/Ship something every month is an interesting idea.
It's funny to ask for advice from others who barely know your passions and capability, but it will give it a few random shots:
- follow your passion, not the money. when you work on your startup, do you truly enjoy at least some part of it, or just following the hype or hoping to become millionaires?
- are you well off where money is not an issue? if money is an issue, get a job; you can choose to work with well-off Malaysian startup like GrabTaxi.
Then we would have United Earth Federation followed by United Galaxy Federation :)
I guess a healthy amount of options are good, since everyone have their own preferences. Each framework might seems to be solving the same problem, but each have their own philosophy and unique approach. Without diversity, we won't have rice, sushi and burgers.
I know it's pain in the ass to evaluate a framework or language, thus I build StackBus (http://www.stackbus.com/), a place where people share what stack they use, why they use it and to build what kind of product, providing more useful insights when making choices.
I guess remote work is an option, but not quite a total solution at the moment.
1) not all work could be remote
2) self-discipline/communication is tough
Woofoo (about 7 people) did remote, but the founder admit it's tough and challenging even for such a small and motivated company (imagine your workforce > 1000 people), though there are some obvious benefits.
It's not just about tools (slack, skype, etc.) and finding a procedure that works, but more about company culture, motivation, discipline, adaptation to remote environment, family at home, etc. Not every employee could survive a remote environment and continue to be productive :(
Before everyone could work from home, maybe the idea of multiple office location/work-space (rather than centralized) could be explored, yet it will have many pros and cons.
Nice insights on the actual usage of React, hopefully I have the time and opportunity to work on it :)
I would like to encourage more people to share on StackBus (FYI, I built it) on why they use React and what they use it for, to provide more insights to those who are evaluating React
http://www.stackbus.com/
I would like to encourage more people to share on StackBus (FYI, I built it) on why they use IPython and what they use it for, to provide more insights to those who are evaluating IPython
http://www.stackbus.com/