My first tip would be to take the time to *really* understand how publications and subscriptions work. Most new developers don't understand why you can't just do "Posts.find()" on the client and expect to get a list of all your database's posts.Vasyl Samusiev - former developer at Apiko
My second tip would be to use as few Meteor packages as you can. Now that Meteor supports NPM out of the box, there's no reason for using a Meteor package if an NPM package will do the same job. For example, I would recommend using React Router over FlowRouter.
And my third tip would be to not get too attached to Meteor. Even though Meteor is awesome, as a developer you don't want to pigeon-hole yourself. So that's why it's important to also get familiar with things like React, Redux, Apollo, and so on. Plus, that's just the direction the ecosystem as a whole is moving in.
The most complete information about any technology is stored in its documentation. That’s why to get started with Meteor I would suggest the officcial tutorial + 1 or 2 video courses on Meteor (not more) + guide.meteor.com + docs.meteor.com. It’s necessary to apply the knowledge you get practically!Dean Witcraft - software engineer
I’d recommend you first to create the projects from the official tutorial and from the video course(s).
After that you should create your own simple project. You can take the ideas from your everyday life (e.g. a notepad, a cookbook, a player for your cell phone, etc.). If you struggle with finding your own idea for the project, take a look at your favourite websites or apps and try to create something similar to them (not their copy, just a model).
Start with the default implementation (Blaze/Mongo) and the Discover Meteor book, although it's starting to be somewhat dated it's still very useful.Michael Mazurczak - founder of situation.io
Use the Meteor Guide. It will help you to stay close to the current state of Meteor. There's a lot of out-of-date information online.
Get involved with the Meteor Forums and The Meteor Chef and their Slack channel. There's almost always someone online who can answer beginner's questions assuming you've done your homework first.
Don’t invest too much in Blaze, Meteor is clearly putting it in maintenance mode. Go with Angular or React asap, so you don’t feel abandoned in a year or so.
Read the Mongodb docs, lots of performance issues are due to lack of indexes or inefficient queries.
Go for React as the view layer, as this seems to be the future of Meteor. If you’re in a hurry and need a quick MVP, you may choose Blaze instead.Tomas Hayes - web developer, Feriaferio
Select your community packages carefully. Not all of them are maintained well, and it may happen that their support will be dropped in future Meteor versions (as it happened with CollectionFS). Have a look at the number of open issues and PRs.
Read the tutorials and then the excellent Meteor Guide.
It’s better to begin with Blaze as it’s so much easier to comprehend compared to React and Angular. Try to stick with the technologies you know and learn new ones at one step at a time.Scott Tolinski - creator of Level Up Tutorials
Experiment a lot with some small project to get your head around mongoDB.
Don’t be afraid to ask for help on forums! Later your question may also help someone else.
Have fun, make something interesting to you, don’t be afraid to write bad code.
Good luck with your projects! Feel free to add your own Meteor tips and share your development experience in the comments. We would love to hear from you!Opinion shapers