quick poll:
- who is meteor newbie?
- who is experienced JS dev?

please give me feedback on where you want to dig deeper

Please provide feedback if you stumble upon something wired or especially like something!

use package or not:
production or development
functionality not anymore, implement it myself like search source or pagination
lost much time for that

- discussion/resource about Sessions: https://forums.meteor.com/t/patterns-and-practices-for-passing-data-between...
- what's your opinion? what is bad about using sessions? what should you be aware of when using them?

disclaimer: I'm not an expert, Please share if you have different opinions or correct me if I'm wrong.

- use Nicholas Zakas' helpful little function

Meteor is moving fast!
you can easily get distracted simply by the amount of stuff that's going on. So you have to focus on the important stuff (important to Meteor in general) and important to your specific project/use case. Knowing key members of the community helps a lot with that. Because you can trust their opinions. As you newbie you just don't know what's important and what is just interesting to read but doesn't have a long lasting impact.

- identify MDG memers
- identify the top contributors/ most active people in the community: Arunoda, Josh Owens, Chet Corcos, rclai, David Weldon (highly active on SO, cool blog!) usw. -> know whose opinion to trust
- subscribe to every Meteor news-channel that you can: thisweekinmeteor, crater.io, forums, david weldons blog, meteor interviews

- but: don't get distracted by all the activity! set aside some fixed amount of time to consume the news, decide what's relevant to your current project or possible future projects and then get back to work

schema
- David Weldon article, Llama article, Astronomy package

Immutable
- it's worth the effort
- I had lots of bugs that were difficult to trace because of mutable state
- for example when you use schema it mutates the object

- pattern to namespace Sessions: https://medium.com/@sirchill3/meteor-managing-the-global-namespace-5a50080a...

- David Weldon, Abigail Watson, rclai
watch their blogs

- Sanjo:Jasmine package, well maintained
- Jasmine features: simple syntax, Spies!
- TDD workflow: red, green, refactor
-> small steps, quick feedback
-> detect bugs easily (must be in last added code)
-> safe against regression

-> confidence!
developing software is about "managing complexity" (McConnell?)
- I used TDD for scraper code which grew quite complex and where failure could have severly bad consequences (getting blocked)
- why complex? -> lots of small functions build larger structures


-> confidence of TDD helped me a lot

-> less time (and nerves) spent on debugging

who knows about "meteor debug"?
-> easily debug server side code