Avoid building something that involves skills that you don't have, and always overestimate how difficult a given feature will be to implement.

“The simple things are also the most extraordinary things, and only the wise can see them.” ― Paulo Coelho, The Alchemist

There are two types of struggle, productive and unproductive. Struggling through a problem is an amazing way to learn, but there is a point when you might need a little help.

We would recommend spending at least 20-30 minutes on a problem before you ask the community or a code mentor for help.

"Don't be afraid to ask questions. Don't be afraid to ask for help when you need it. I do that every day. Asking for help isn't a sign of weakness, it's a sign of strength. It shows you have the courage to admit when you don't know something, and to learn something new." -Barrack Obama

You must deploy your submission in order to be considered for scoring. You also never know when you're going to hit a snag, so you should try to deploy as often as possible (i.e. multiple times daily). That way, you will never be taken off-guard by a nasty bug and be forced to deploy older code.

Now that you have all the tools you need, you can start building a simple project of your own design.

Over the next few days, you want to make your project more complex, bit by bit. Keep things simple to start with, then iterate incrementally. Don't rush it, you have plenty of time! Make sure you deploy on the web!