(This is Marc, author of the linked post.)

I think people attribute success to a name because that fits the mental model people have for success: You just choose the right name! And then you win!

That's nonsense. Winning is a long series of decisions that have to go right far more often than not. I pulled out the decisions I thought really were critical and irreparable turning points -- hard decisions that required a lot of analysis and a lot of work to fulfill, both for us and for Mint.

You'd like to believe the name is all that matters because then the path to success is so short and so clear. It just isn't so. (And there are counterexamples galore that you're emphatically ignoring -- companies with fantastic names that never got anywhere.)

To be clear: they did have a better name. I say so in the article. But that's not enough to win.

1. Be good. Be very good. Don't be the "front-end guy" or the "back-end guy", or some other "guy". Once you know what you want to build, building software is about five things: algorithms that solve your problem, programming languages that express your algorithms, computer architecture that makes your algorithms run efficiently on real hardware, the practical toolchain, and the management of complexity of real software. So study algorithms, and then graduate algorithms, and then advanced graduate algorithms. Do every challenge problem online. Study programming languages to express those algorithms. You can get away with three: C, Lisp, Haskell. Everything else is crud. Study computer architecture and compilers to see how your programs run efficiently. Learn great tools (Emacs/Vim/Visual Studio/bash/Linux/OS X/Windows whatever - just great ones that you're damn good at). Learn how complexity is managed. Look at lare open source projects, study how they're organized, and contribute patches to understand how small changes can effect a large system.

2. Learn what to build. Once you get really good, your time starts to be more valuable than gold. There will be very few people in the world who are as good (the internet will bias you to think that the world is full of great people - this ain't so, there isn't enough of 'em). You owe it to people and to yourself not to bother with improving something by 1% or 10% because you're wasting time in opportunity cost and could be improving something by 1000%. Make sure what you're building is worth building, and make sure every line of code you write is worth writing, otherwise you will fail. Break the NIH syndrome in yourselves now (all good people have it, phenomenal people that build successful companies broke it in themselves). Learn to infer what people want.

3. If you're that good, you will easily get a $100k job after graduation (probably more by then), and grow to $180k in a few years. That's very, very comfortable. It's not worth busting your ass 16 hours a day to build another CRM tool when you can have a $180k job. So don't start a business to start a business. Start a business to bring a meaningful change in the world. A huge change. A 1000% change. There are lots of hugely successful companies out there that do what's not meaningful to you - ignore them. But do make sure that what's meaningful to you is also meaningful to millions (hopefully billions) of others. You won't get rich writing Lisp compilers.

This is what matters. Most everything else is fluff.

Have you considered a career as a James Bond antagonist?

The essential point seems to be that Mint was easier for users. This is something we constantly emphasize at YC. You care a lot about your startup. You have no idea how little a potential user cares. So you can't let the activation energy be high.

Plus users are mostly not programmers. They're terrified by software. Most software they've tried in their lives has caused them pain, either by not working right or by being incomprehensible (which are indistinguishable to the victim).

So imagine you're designing your app for someone who's both apathetic and cringing with fear at the same time. You cannot make it too easy. If there's something you can do that will take a week and make your app 1% easier to start using, it's worth doing.