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

Written by anti microsoft guy. Doesn't mention C# and typescript. Including Java currently. He is nuts

???

Only if Google / facebook stops inventing. Yahoo made a mistake of stagnation. Microsoft made a mistake of stagnation from 2000 to 2009 (Balmer period). Motorola made a mistake of stagnation. Apple is again making a mistake of stagnation. As long as companies not sitting on their arses and let the competition overtake them they will be fine.

Also you can live without FB but cannot live without google. You can remain days not visiting FB but everyday you will search atleast one time.

I think you are getting confused between learning programming and learning technology and language. I will say start with one language and learn programming first. Once you learn programming than you should be able to code in any other language once you master the concepts. using javascript you mainly deal with web client side programming, where as when you say java app it deals with so many (desktop, server side etc). You can download microsoft visual express developer edition and start learning C#. Which will give you all aspects of development. leaning any open source is much harder even though you have tons of documentation available all over the web

I will say good start but not useful though. Except entering numbers I couldn't do any thing. One good thing is it is very light. The reason people use excel because you can do lot more than just entering numbers.

If you look around professional websites, it looks professional for only reason they publish after it looks professional. Every thing iterative. Once you design some thing you just need to constantly iterate your own design. Trust me your end product will look professional. The main constituents of aesthetic is a combinations of colors, placements and font. Typical design colors should be in the range of blue to green. Which are pleasant to your eyes. Once you finish your design you can get feedback upon which you can improve your design.

Actually it is very easy to debug any javascript error. In IE there is a setting where you can uncheck the Disable Script debugging (Internet Explorer) and in the status bar you will see any javascript error. If you check the checkbox IE will not report any errors. In general during your development you should always uncheck the box.If you double click the javascript status this will exactly report the line number where the javscript error is. I exactly don't know if you see these kind of errors in Chrome and firefox. I know people blame IE but there are quite few nice handy features which are very helpful during development

I am not saying that you have to build the site in .NET Framework. You can pick any technology which you like. I specified it just as an example. Before you hire a developer and pay him, you should write down couple of points such as 1) What does the web application do 2) What are the core min features that you need to satisfy first few users (don't get into the habbit of feature creep) 3) What is your intended audience 4) What is the core problem you are trying to solve.

Also as a prototype do you really need the Database and other stuff. It should not matter what database or language or framework you use but you should be able to answer the above questions.

Don't listen to the people who say one language is greater than other language. It shouldn't matter. You should pick one which is easier for you and others who join you later.

Typicall tech co-founder in a early startup person is the one who can code your whole application without any outside help. He/she should be able to go through the code and fix any bugs if it is needed. This person should have good knowledge in all aspects of technologies. For ex: if you are using a website built on .NET Framework with SQL Server backend, generally then this person should be familiar with databases, writing store procs, building web services, writing C# code and lot of other stuff.

When evaluating a tech co-founder you should ask with 2 of your guys can you complete your application end to end and go public without any outside help. If the answer is yes then he/she can be your tech cofounder.

Since in the early days without any funding, money is tight you should be able to complete the prototype/product with almost no resources.

I started programming in 1991. Initially I didn't understand any thing. Then after couple of months every thing made sense. The only thing in programming is practice. If you don't get 100th time you should try 101st. If you don't get it in 1000 times try 1001 time. The only way you can get any thing in programming is practice practice and practice. This is not rocket science eventually you are going to get it. The only thing you require is patience. Always start simple. Then slowly try to learn harder things. These days you have lot of resources available online which makes it very easy for one to learn programming

I think you might already know this but it is worth while repeating. Idea is not important, execution is the most important thing

Just one suggestion, just because other people are already started doing what you thought was a good idea does't mean you give up on it. if this is the case then none of the following companies existed : Microsoft, Google, Apple, Yahoo, Cisco etc etc.

Just pick what you are mostly interested and start finding a niche which is useful to the users. The most important thing is to develop some thing users want. If you can figure out that then your already won your 50% battle.

just my 2c

The courses you lined up are pretty good. You should stick with one scripting language for now. Once you are comfortable with one, you can pick up the other one later. You will always find people who will say php is better than ROR, ROR better than python. Don't listen to them. I will say pick one stick with one. Once you mastered its not a big deal to go on to other languages.

Before you start, understand the basic architecture of web based technology. Try to understand how http works in basic.

Just because you watched some videos and went through tutorials you won't be able to program. What you need to do is practice practice and practice. If you can't get in 100th time you should try 101st time. Another thing you need is passion. You should like what you are doing. If you are coding for the heck of it, you will not be able to code.

I think Match.com itself needs a tech cofounder. Login and Join us takes lot of time. I gave up after some time.

This should work. If they pay for whole year, give them discount. If they are charging monthly then don't give them discount. You should calculate your profitability when figuring out the discount