rajeshamara

When you say failure what exactly you mean 1) Did not scale 2) Performance issues 3) Ran over budget 4) Ran over time 5) Lots of bugs 6) Feature creep

In your message you said unsolved usability issues. Typically usability issues should be solvable. My advice is accept the failure, learn from your mistakes for the next project. These things happen. Just move on.

Also 4 months is too short of a time to declare it as a failure. You can always pivot to make it successful

AT&T give 7% dividend. VZ give 4.5% dividend. There should be good quality stocks which easily pay 3% dividend. If you do drip in 4 to 5 years it might become 4%-5%. But always there is a risk though

Congrats. Just curious, what are your revenue sources- ads or paid subscriptions?

I think zoom is already getting into similar. Also feel pricing is a bit on expensive side for what you are providing

1) Ask the other team members can they function without the lead engineer 2) Ask the other team members to do all the work for 2 weeks without the lead engineer 3) Ask the lead engineer to start documenting 4) You always need to have a backup plan (what if a member gets killed by a bus or quits after winning lottery) 5) I doubt that other engineers would be lost without the lead engineer. In general no one is valuable 6) Put a plan in place thinking that lead engineer will quit and he has given 2 weeks notice

Before I answer what would I get in your search engine, that I won't get in Google (assuming I don't care if Google tracks everything i do). All I look in a search engine is am I getting the results for the things I am looking for. I don't see any difference in results between Bing and Google. But I still use Google. I felt some how I like the results on Google (the way they present). Not sure why I don't like the way Bing presents.

How long does your robot take to do the hair cut. I never wait more than 10 min for a haircut. Currently if you do the appt. online, you can go around that time and they will take you right away. Your concept is good but may be you need to pivot.

1)Have stored procedures with parameters for all you backend transactions 2)Make sure you have foreign key constraints between tables 3)Log everything so that you can track 4)Daily backup your db so that you can restore in case something happens 5)Create primary keys for each table 6)For all you order make sure if is between transaction and roll back in case of failures 7)After successful, payment transaction, send out email notification to the end customer. You can cc yourself too. Again this if for auditing purpose. What I came up is a very quick list. Again you need to thoroughly analyze your req. and come up appropriate solutions

I wish a valuation column was added. Much easier to read. Now we have to intepret from the text. Not a big deal, but prefer it as a separate column

Yes very useful. Thanks for your effort.

Jeremy, I live in PA. Do you have online streaming for this course or do we need to be physically in CA

The only way is to have confidence in you. No one is perfect everyone learns by trial and errors. You become perfect via practice

Right now your focus should be get a MVP out. Don't worry about the technology. You can change the underlying tech later once you have a viable business. Pick something which you are comfortable and get the product out

No Framework is perfect. There are always tradeoffs. Just because some things didn't work for you doesn't mean you can generalize and say Angular2 is bad. The way the Author wrote, he is generalizing things and making assumptions based on baseless facts

2 flaws with this article. 1) Using a Beta product and complaining on Angular2. You could have waited till the product is matured 2) Blaming for the developers inefficiency on Typescript. If your developers coding speed is reduced blame on your developers. Your title and article appears that something is wrong with Angular2 and moved to Vue.js. Before you post such articles make sure what your write makes sense